SKILLEMALL.ai

BA roadmap

Plan and execute entire application builds. Generates phased delivery roadmaps, then executes them autonomously — phase by phase, committing at milestones, deploying, testing, and continuing until done or stuck. Modes: plan (generate roadmap), start (begin executing), resume (continue from where you left off), status (show progress). Triggers: 'roadmap', 'start building', 'resume the build', 'keep going', 'build the whole thing', 'execute the roadmap', 'what phase are we on'.

jezweb/claude-skills Agent Skills author: jezweb 1 file body ≈ 3 259 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Plan and execute entire application builds.

As a process A 81/100 · Runs to the end — weak spots: running it twice

GeneratorCloudflareOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
95
Quality 40%
87
Run on models
none yet
Process rating
A
81/100
Runs to the end
Running it twice w 4
30
When it triggers w 12
50
Failures and branches w 10
55
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: roadmap (Lord1Egypt/RA-Skills)

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Read Write Edit Glob Grep Bash

    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 81/100

    • 30Running it twice. 26 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 75 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3259 tokens
    • 100Progress reporting. Reports progress

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

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