BD novel-orchestrator
用于长篇网络小说协作生产与流程统筹。适用于写章节、续写、重写、救文、审稿、分卷规划、长线结构调整，以及任何需要在 manager、planner、writer、checker 之间进行任务路由、协作编排、返修闭环和阶段推进的小说任务。当用户要求创建小说agent、初始化小说工作流、设置小说创作环境时，使用此skill自动创建writer/checker/planner/manager四个agent。
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-agent-memory-dumpassets/agent-templates/checker/HEARTBEAT.mdAgent memory / workspace files bundled with the skill (16) — likely a workspace dump with personal data or tokensassets/agent-templates/checker/HEARTBEAT.md, assets/agent-templates/checker/IDENTITY.md, assets/agent-templates/checker/SOUL.md, assets/agent-templates/checker/USER.md, assets/agent-templates/manager/
Files scanned: 38. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 69 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 686 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 201: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 69 items
- +4Reference files are cited in the instructions (1 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.