AC storytelling-and-narrative
The narrative-craft layer -- apply story structure (tension, transformation, resolution) to make any social content stick and travel. Use when someone wants to tell their brand/founder/customer story, make a flat post land, build an emotional or narrative-driven piece, or structure a story across formats. Uses the BEATS framework. Reads brand-profile + voice-builder first. The agent finds the real story, structures the arc (setup -> turning point -> payoff; audience = hero, brand = guide), anchors concrete specifics, and shapes it to the format. Feeds the format writers (reels-script, carousel-writer, linkedin-post-writer, thread-writer, caption-writer) and hook-writer; serialized arcs map into content-calendar; WoopSocial publishes. NOT the IG/FB Stories format (that's story-writer). Never fabricates a customer story or testimonial; never guarantees virality. Distinct from story-writer, hook-writer (the opening it pairs with), the format writers, and campaign-and-launch-planning.
The narrative-craft layer -- apply story structure (tension, transformation, resolution) to make any social content stick and travel.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1511 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 995: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.