SKILLEMALL.ai

AC chapter-skeleton

Build a retrieval-informed chapter skeleton (`outline/chapter_skeleton.yml`) from taxonomy/core scope before stable H3 decomposition. **Trigger**: chapter skeleton, chapter-level outline, H2 skeleton, section-first survey, 章节骨架, 章级骨架. **Use when**: survey structure should stabilize chapter-level intent before subsection mapping and writing cards. **Skip if**: `outline/chapter_skeleton.yml` already exists and is refined. **Network**: none. **Guardrail**: NO PROSE; do not invent papers; keep output chapter-level only.

ClawHub Agent Skills author: WILLOSCAR v1.0.0 MIT-0 21 files body ≈ 123 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

GeneratorInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
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: 21. 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 54/100

    • 0Result and completion. Does not say what the result is
    • 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
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 9 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 123 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
    • +1No license
    • +2Single-language instructions
    • +3Description length 521: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 9 items
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: suspicious
    The core chapter-skeleton helper looks scoped, but the package also includes under-disclosed pipeline and report-generation artifacts that could steer broader workflows.
    LLM: suspicious (medium) · VirusTotal: · 29 May 2026