SKILLEMALL.ai
GitHub ↗ RU Sign in

BD run-parity

Compare React Doctor diagnostics for a GitHub pull request (PR) with Vercel Sandbox. Use when asked to run parity, check a PR for diagnostic regressions, compare a PR with its base, or report added and removed diagnostics.

millionco/react-doctor Agent Skills author: millionco NOASSERTION 16 files · 14 scripts body ≈ 4 078 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Compare React Doctor diagnostics for a GitHub pull request (PR) with Vercel Sandbox.

As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerGitHubData and analyticsSoftware 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
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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: 16. 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 272): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 43/100

    • 0Result and completion. Does not say what the result is
    • 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. 16 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70Execution cost. Instruction body is 4078 tokens
    • 75Steps. 3 steps
    • 100Consistency. Name and required fields are in place
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The skill ranks results itself: that belongs to the system behind the tool, not the model

    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
    • -32 of 14 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 222: enough signal without eating the budget
    • +4Structure: 5 headings
    • +3Step-by-step instructions: 3 items
    • +4Has examples (15 code blocks)

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