SKILLEMALL.ai

AB dnd-campaign-starter

Spin up a tabletop RPG one-shot or a session-zero for a new campaign — a hook, a map of the first adventure, NPCs, and encounters tuned to your party. Use when asked to start a D&D campaign, run a one-shot, help me DM, session zero, or make me an adventure for my party. Produces a premise and hook, a session-zero framework (tone, safety tools, expectations), a first-adventure outline with beats and branches, ready-to-run NPCs and encounters scaled to party level/size, and improv fallbacks for when players go off-script.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 1 file body ≈ 885 tokens Open the sourcegithub.com analyzed 2 d ago

Spin up a tabletop RPG one-shot or a session-zero for a new campaign — a hook, a map of the first adventure, NPCs, and encounters tuned to your party.

As a process B 72/100 · Nearly there — weak spots: when it triggers, progress reporting

GeneratorMarketingtype 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
B
72/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Failures and branches w 10
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: dnd-campaign-starter (mohitagw15856/pm-claude-skills)

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: 1. 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 72/100

    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 31 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 885 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 525: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 31 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)

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