SKILLEMALL.ai
GitHub ↗ RU Sign in

BC patent-pipeline

Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents. Supports CN (CNIPA), US (USPTO), EP (EPO). Supports invention patents and utility models. Use when user says "写专利", "patent pipeline", "专利申请", "draft patent", "写权利要求书", or wants to draft a complete patent application.

wanshuiyin/Auto-claude-code-research-in-sleep Claude Code author: wanshuiyin MIT 1 file body ≈ 3 628 tokens Open the sourcegithub.com↗ analyzed 5 h ago

Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents.

As a process C 54/100 · Has gaps — References files that are not bundled: ../shared-references/reviewer-backends.md

ProcedureInfrastructuretype 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
91/100
safety, quality, tests
Safety 60%
95
Quality 40%
86
Run on models
none yet
Process rating
C
54/100
Has gaps
References files that are not bundled: ../shared-references/reviewer-backends.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: Auto-claude-code-research-in-sleep

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash(*)
    allowed-tools: Bash(*) Read Write Edit Grep Glob WebSearch WebFetch Skill

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../shared-references/reviewer-backends.md

Process rating: all ten parameters 54/100

Will not run. References files that are not bundled: ../shared-references/reviewer-backends.md
  • 0Tools and files. 1 referenced file(s) missing: ../shared-references/reviewer-backends.md
  • 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. 1 mutating operations with no state check
  • 85Steps. 44 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3628 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)
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 318: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 44 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)

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