BC interactive-fiction
This skill should be used when the user asks to "write a branching story", "interactive fiction", "choose your own adventure", "plan the branches", "choice graph", "add a choice", "gamebook", "Twine", "Ink", "draft a branch", "where the branches rejoin", "add an ending", "unreachable chapter", "path continuity", "state-differs-by-path", or wants to plan, draft, or revise a story project whose chapters carry `choices`. NOT for turning a finished linear book into an interactive edition in Ink or Twine (use adaptation).
This skill should be used when the user asks to "write a branching story", "interactive fiction", "choose your own adventure", "plan the branches", "choice…
As a process C 55/100 · Has gaps — References files that are not bundled: ../../examples/the-gull-rock-light/, ../story-maintenance/references/continuity-checks.md, ../story-maintenance/references/conventions.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../examples/the-gull-rock-light/ - warning
missing-refreference to a missing file: ../story-maintenance/references/continuity-checks.md - warning
missing-refreference to a missing file: ../story-maintenance/references/conventions.md - warning
missing-refreference to a missing file: examples/the-gull-rock-light - warning
missing-refreference to a missing file: references/interactive-fiction.md
Process rating: all ten parameters 55/100
- 0Tools and files. 5 referenced file(s) missing: ../../examples/the-gull-rock-light/, ../story-maintenance/references/continuity-checks.md, ../story-maintenance/references/conventions.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 9 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 39 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3153 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 13 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 522: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.