SKILLEMALL.ai

AC narrative-building

Drafts or audits a scientific paper’s introduction and framing. Covers the motivating real-world "why", evidence audit, theory-to-falsifiable-if-then funnel with a named estimand, bridges across experiments, and a contribution list matched to the design. Use when the user asks to write, restructure, or critique an introduction, motivate or frame a paper, repair a gap-in-the-literature opening, sharpen or calibrate a contribution claim, or connect experiments into one argument. Sentence-level flow and wording go to prose-revision.

scdenney/open-science-skills Claude Code author: scdenney NOASSERTION 2 files body ≈ 3 925 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Drafts or audits a scientific paper’s introduction and framing.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

AnalyzerMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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: 2. 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 57/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
    • 30Running it twice. 5 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 42 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3925 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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 535: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 42 items
    • +4Has examples (0 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

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