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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-sequenced orchestrator skill with strong workflow clarity and concrete sub-skill invocations, but it is overlong for a SKILL.md: duplicate diagrams and inlined reference material that should live in bundle files hurt conciseness and progressive disclosure.

Suggestions

Move the patent-type comparison tables, jurisdiction deliverables table, and final-report template into separate reference files under references/ (e.g. PATENT_TYPES.md, JURISDICTION_OUTPUT.md, REPORT_TEMPLATE.md) and link to them from the body to improve progressive disclosure.

Remove the duplicate ASCII pipeline diagram in 'Composing with Other Workflows' — the Overview already depicts the idea-discovery tracks — and drop the Acknowledgements section to reduce token load.

Tighten editorial prose such as 'Patents are about protecting inventions (legal scope), not publishing results (academic contribution).' to the operational minimum Claude needs.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational guidance, but includes redundant material — two ASCII pipeline diagrams depicting the same idea-discovery tracks, a verbose final-report template, and an Acknowledgements section — that could be tightened; some explanatory prose ('Patents are about protecting inventions ...') pads rather than instructs.	3 / 5
Actionability	Provides concrete, executable invocations with arguments (e.g. /prior-art-search "patent/INVENTION_BRIEF.md"), explicit file paths, a state JSON schema, and checkpoint templates — mostly copy-paste ready with only minor gaps where sub-skill internals are delegated.	4 / 5
Workflow Clarity	Phases 0–5 are clearly sequenced with explicit validation checkpoints (🚦 Checkpoint, ⛔ STOP HERE), state persistence and resume logic, and feedback loops (review rounds, novelty re-check on adjustments), matching the anchor for explicit validation steps and error-recovery loops.	5 / 5
Progressive Disclosure	Good section structure, but at ~340 lines the body is monolithic with no bundle files in references/scripts/assets; material that belongs in separate files (patent-type comparison tables, jurisdiction deliverables table, final-report template, state schema) is inlined rather than split into one-level-deep references.	3 / 5
	Total	15 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it clearly states the pipeline's purpose, enumerates supported jurisdictions and patent types, and provides explicit bilingual trigger phrases for when to use it. The only soft spot is specificity, where capabilities are stated at the pipeline/jurisdiction level rather than as a granular list of concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents') plus concrete coverage (CN/US/EP jurisdictions, invention patents and utility models), listing several specific capabilities with only minor gaps in granular action enumeration.	4 / 5
Completeness	Explicitly answers both 'what' (full patent drafting pipeline to jurisdiction-formatted filing documents) and 'when' ('Use when user says ...') with concrete trigger phrases, matching the anchor for clear and explicit what-and-when.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms across both languages ("写专利", "patent pipeline", "专利申请", "draft patent", "写权利要求书") plus the natural phrase 'wants to draft a complete patent application' — covers synonyms and bilingual variations users would actually say.	5 / 5
Distinctiveness Conflict Risk	Patent drafting is a clear niche with highly specific triggers (e.g. '写权利要求书', 'draft patent') that are unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: wanshuiyin/Auto-claude-code-research-in-sleep
Path: skills/patent-pipeline/SKILL.md
Commit: 0472e53

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.