SKILLEMALL.ai

BA feature-flag-strategy

Plan a flag-gated rollout: classify the flag, pick a rollout shape, set kill-switch thresholds and retire the flag. Use when planning a phased rollout, a kill switch, a holdout or a cleanup of old flags.

borghei/Claude-Skills Agent Skills author: borghei 10 files body ≈ 2 335 tokens Open the sourcegithub.com↗ analyzed 8 h ago

Plan a flag-gated rollout: classify the flag, pick a rollout shape, set kill-switch thresholds and retire the flag.

As a process A 80/100 · Runs to the end — weak spots: result and completion, running it twice

ProcedureData and analyticsSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
A
80/100
Runs to the end
Running it twice w 4
30
Result and completion w 14
40
When it triggers w 12
50
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: 10. 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 80/100

    • 30Running it twice. 7 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 22 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2335 tokens
    • 100Progress reporting. Reports progress
    • low 10 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)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +2Single-language instructions
    • +3Description length 203: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 22 items
    • +4Reference files are cited in the instructions (4 of 4)
    • +1License stated

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