| name | Plot-Consistency-Checker |
| description | Checks a story's plot for inconsistencies, logical gaps, and timeline errors. |
| version | 1.0.0 |
When to use this skill
Use this skill during the drafting or editing phase of a story to identify and rectify any logical flaws, continuity errors, or discrepancies in the narrative. This ensures a cohesive and believable plot for the reader.
How this skill works (step-by-step workflow)
- User provides a story summary or key plot points, potentially including character actions, timelines, and world-building rules.
- The skill analyzes the provided information, looking for contradictions, unexplained events, or deviations from established rules.
- It identifies potential inconsistencies and provides specific feedback on where and why they might exist.
- The output is a JSON object listing identified issues, their severity, and suggestions for resolution.
Output format (JSON structure)
{
"story_title": "The Story Title",
"consistency_report": [
{
"issue_id": "PC001",
"type": "Logical Inconsistency",
"description": "Character A is in Location X at Time 1, but then appears in Location Y at Time 2, which is geographically impossible given the travel time.",
"severity": "High",
"suggested_resolution": "Adjust timeline, introduce faster travel method, or clarify character's simultaneous presence."
},
{
"issue_id": "PC002",
"type": "Character Motivation Discrepancy",
"description": "Character B, known for being extremely cautious, suddenly takes a reckless action without clear internal justification.",
"severity": "Medium",
"suggested_resolution": "Add internal monologue or preceding events to justify the change in behavior."
}
]
}
Example input and output
Example Input: "Story: A detective story. Detective Miles investigates a murder. He finds a clue on Tuesday at 9 AM in the victim's office. Later that day, at 3 PM, he interviews a suspect who claims to have been out of the city since Monday evening. However, the clue he found was a recent receipt from a local cafe, dated Tuesday 10 AM."
Example Output (truncated for brevity):
{
"story_title": "Murder at the Cafe",
"consistency_report": [
{
"issue_id": "PC001",
"type": "Timeline Inconsistency",
"description": "Detective Miles finds a clue dated Tuesday 10 AM, but he supposedly found it at 9 AM on Tuesday. This is a chronological contradiction.",
"severity": "High",
"suggested_resolution": "Adjust the time Miles finds the clue to after 10 AM, or change the receipt's timestamp."
},
{
"issue_id": "PC002",
"type": "Suspect Alibi Contradiction",
"description": "The suspect claims to be out of the city since Monday evening, but a clue dated Tuesday 10 AM from a local cafe was found. This contradicts the suspect's alibi if they were the one who made the purchase.",
"severity": "High",
"suggested_resolution": "Investigate who made the purchase at 10 AM. If it was the suspect, their alibi is false. If not, clarify the source of the receipt."
}
]
}