SKILLEMALL.ai
GitHub ↗ RU Sign in

BF story-long-write

长篇网文写作。从大纲到正文，辅助长篇网络小说的创作，包括世界观、人物、情节线管理。触发方式：/story-long-write、/写长篇、「帮我开书」「写大纲」「日更」「续写」「继续写」「修改第X章」「回炉」「重写第X章」。

ClawHub Agent Skills author: pitechen v1.1.23 MIT-0 80 files body ≈ 1 768 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process F 38/100 · Will not run — References files that are not bundled: references/writing-craft.md, scripts/tracking_commit.py

GeneratorSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: references/writing-craft.md, scripts/tracking_commit.py
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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: 80. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/writing-craft.md
  • warning missing-ref reference to a missing file: scripts/tracking_commit.py

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: references/writing-craft.md, scripts/tracking_commit.py
  • 0Tools and files. 2 referenced file(s) missing: references/writing-craft.md, scripts/tracking_commit.py
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 15 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1768 tokens

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 112: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 15 items
  • +4Reference files are cited in the instructions (19 of 47)

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

External checks

ClawHub: suspicious
This writing skill is coherent overall, but it needs Review because a bundled tracking script can delete Markdown files outside the project through a symlink and author-memory files are written with permissive local permissions.
LLM: suspicious (high) · 9 Sept 2026