SKILLEMALL.ai
GitHub ↗ RU Sign in

BB test-value

Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.

The skillemall take

The skill identifies slow, flaky, and redundant tests while calculating audit costs. Operates locally on affected code, skips repository-wide scans. Five files, 2308 tokens of logic. Grade B: quality 85, process 66, safety 100. No critical errors, no lint issues. Models untested, sandbox unused.

Useful for auditing specific tests during development or before commits. Not for full repository diagnostics. Works across all platforms from Claude to DeepSeek. Install if tests already cause friction.

tt-a1i/archify Agent Skills author: tt-a1i MIT 5 files body ≈ 2 308 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes…

As a process B 66/100 · Nearly there — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerSoftware developmentData and analyticstype 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%
85
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
20
Result and completion w 14
40
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: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 12, 38): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 66/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 40Result and completion. Does not say what the result is
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 13 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2308 tokens
    • 100Running it twice. Mutating operations check current state
    • 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)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +2Single-language instructions
    • +3Description length 288: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 13 items
    • +4Reference files are cited in the instructions (2 of 2)
    • +1License stated

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