SKILLEMALL.ai
GitHub ↗ RU Sign in

AB genre-craft

This skill should be used when the user asks to "mystery", "fair play", "clue", "red herring", "romance beats", "HEA", "thriller", "ticking clock", "horror", "dread", "MG", "YA", "middle grade", "young adult", "science fiction", "sci-fi", "serial", "episodic", "web serial", "genre conventions", or wants genre-specific structural craft for a story project.

danjdewhurst/story-skills Agent Skills author: danjdewhurst MIT 8 files body ≈ 1 614 tokens Open the sourcegithub.com↗ analyzed 7 d ago

This skill should be used when the user asks to "mystery", "fair play", "clue", "red herring", "romance beats", "HEA", "thriller", "ticking clock", "horror"…

As a process B 68/100 · Nearly there — weak spots: result and completion, running it twice

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
99/100
safety, quality, tests
Safety 60%
100
Quality 40%
97
Run on models
none yet
Process rating
B
68/100
Nearly there
Result and completion w 14
0
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 8. 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 68/100

    • 0Result and completion. Does not say what the result is
    • 30Running it twice. 3 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 34 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 1614 tokens
    • 100Progress reporting. Reports progress

    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 15 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 357: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 34 items
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (7 of 7)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 97.