SKILLEMALL.ai
GitHub ↗ RU Sign in

BC plan-pipeline-execute

Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.

FlorianBruniaux/claude-code-ultimate-guide Claude Code author: FlorianBruniaux CC-BY-SA-4.0 1 file body ≈ 1 727 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge.

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

ProcedureInfrastructureWriting and documentstype 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
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
C
58/100
Has gaps
Failures and branches w 10
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
    • 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

    • note frontmatter-key unknown frontmatter key "effort"
    • note edit-residue the text marks something as outdated (lines 65): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 58/100

    • 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
    • 30Running it twice. 13 mutating operations with no state check
    • 40Consistency. Frontmatter name (plan-pipeline-execute) differs from the folder (execute)
    • 60Tools and files. Uses tools (bash, git) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 23 steps, 1 vague phrases
    • 100Result and completion. Output format and completion criterion are stated
    • 100Execution cost. Instruction body is 1727 tokens
    • low 13 top-level sections: this looks like several domains in one skill

    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 185: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 23 items
    • +3Output format is stated explicitly
    • +4Has examples (10 code blocks)

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