SKILLEMALL.ai
GitHub ↗ RU Sign in

AC upstream-recon

Investigate an open-source project before interacting with it — PRs, issues, or comments. Use BEFORE: filing an issue, submitting a PR, or commenting on an existing thread. Triggers on: "upstream recon", "should I PR this", "will they merge", "check the project", "investigate the repo", "PR strategy", "file an issue", "check existing issues", "should I comment", or any time the user wants to interact with a repo they don't maintain. Also use proactively when about to file an issue or PR — checking existing threads prevents duplicates and wasted effort.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 620 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Investigate an open-source project before interacting with it — PRs, issues, or comments.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

ProcedureData and analyticsSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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: 2. 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 57/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 3 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 19 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 620 tokens

    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

    • +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
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 9 example trigger phrases
    • +3Description length 558: enough signal without eating the budget
    • +4Structure: 4 headings
    • +3Step-by-step instructions: 19 items

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