SKILLEMALL.ai
GitHub ↗ RU Sign in

AC Code Patent Validator

Turn your code scan findings into search queries — research existing implementations before consulting an attorney. NOT legal advice.

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

Turn your code scan findings into search queries — research existing implementations before consulting an attorney.

As a process C 64/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

AnalyzerGitHubSoftware 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
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
64/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
    • note frontmatter-key unknown frontmatter key "homepage"
    • note frontmatter-key unknown frontmatter key "emoji"

    Process rating: all ten parameters 64/100

    • 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
    • 40Consistency. Frontmatter name (Code Patent Validator) differs from the folder (code-patent-validator)
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 40 steps
    • 100When it triggers. States when to use and when not to
    • 100Execution cost. Instruction body is 2265 tokens
    • low 13 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 133: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 40 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)

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