SKILLEMALL.ai
GitHub ↗ RU Sign in

AD google-patents

Search Google Patents database for patent research, infringement risk checks, and competitive IP analysis. Use when user mentions: 专利, patent, 侵权, infringement, 知识产权, IP, 外观设计, design patent, 专利检索, patent search, 专利风险, patent risk, 专利分析, patent analysis, 专利布局, patent portfolio, 有没有专利, 会不会侵权, 能不能卖, FTO, freedom to operate, 规避设计, 专利壁垒, 技术壁垒, 权利要求, claims, 专利详情, 发明人, inventor, 受让人, assignee, 专利号, patent number, 说明书, description, 技术领域, 背景技术, 发明内容, 具体实施方式, PDF

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

Search Google Patents database for patent research, infringement risk checks, and competitive IP analysis.

As a process D 36/100 · Unfinished process — weak spots: steps, result and completion, when it triggers

AnalyzerLegalCustomer supporttype 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
D
36/100
Unfinished process
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
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 36/100

    • 0Steps. Prose only: no discrete steps
    • 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
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1005 tokens
    • 100Running it twice. No mutating operations

    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)
    • +3No numbered steps or checklist
    • +1No license
    • +2Single-language instructions
    • +3Description length 459: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)
    • +3All 1 scripts are documented

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