SKILLEMALL.ai
GitHub ↗ RU Sign in

BC output-style-creator

Create, validate, and diagnose Claude Code output styles — the file that sets Claude's role, tone, and response format for every turn. Use when asked to write, bundle, or force an output style for a plugin, to set keep-coding-instructions or force-for-plugin, when a style is not taking effect or the wrong one applies, or when choosing between an output style, CLAUDE.md, a skill, and an agent for a persistent behavior change.

Jamie-BitFlight/claude_skills Agent Skills author: Jamie-BitFlight MIT 14 files · 3 scripts body ≈ 2 853 tokens Open the sourcegithub.com↗ analyzed 8 d ago

Create, validate, and diagnose Claude Code output styles — the file that sets Claude's role, tone, and response format for every turn.

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

AnalyzerAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 8. 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

    • 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. 5 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, write) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 100Steps. 30 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2853 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • medium 14 test cases, all positive: not one "should refuse" or "should ask first"
    • low No test case covers injection arriving through data

    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)
    • -5TODO / placeholder text left in the skill
    • -32 of 3 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 428: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 30 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)

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