CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex/patent-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

The body is a well-sequenced orchestrator skill with outstanding workflow clarity — explicit checkpoints, resume logic, and review feedback loops — and largely concrete, executable sub-skill invocations. Its weaknesses are moderate padding (patent-law fact tables and three overlapping pipeline diagrams) and a vague, jargon-heavy reviewer-routing preamble that lacks concrete commands, plus a dangling reference to a shared file absent from the bundle.

Suggestions

Move the invention-vs-utility-model specification tables into a reference file (e.g., references/patent-types.md) and keep only the decision-relevant constraints (CN-only, apparatus claims only for utility models) inline, cutting the restated patent-law facts Claude already knows.

Replace the three overlapping pipeline diagrams (linear chain, branch tree, and 'Composing with Other Workflows') with a single compact diagram, or fold the entry-points list into a few bullet lines.

Make the reviewer-routing preamble concrete: give the actual reviewer_route.py invocation and an example .aris/reviewer.json, or move the routing details into the referenced reviewer-backends.md file (which should be included in the bundle so the link resolves).

DimensionReasoningScore

Conciseness

The body is mostly operational, but the patent-type tables restate well-known patent law facts Claude already knows ("20 years from filing date", "formal examination only", "6-8 months to grant"), and the pipeline structure is diagrammed three times (the linear chain, the branch tree, and again in "Composing with Other Workflows"). This fits anchor 3 (mostly efficient but includes some unnecessary explanation or could be tightened) rather than anchor 2, since no section is purely concept-teaching and most guidance is skill-specific.

3 / 5

Actionability

Phases 0-5 provide copy-paste-ready sub-skill invocations (e.g., `/prior-art-search "patent/INVENTION_BRIEF.md"`), a complete PATENT_STATE.json schema, exact checkpoint message templates, and concrete override syntax. It falls short of anchor 5 because the reviewer-routing preamble ("resolve invocation → `.aris/reviewer.json` → Codex default ... with `reviewer_route.py`") gives no executable command or example, leaving a gap in a core review phase — anchor 4 (mostly executable with minor gaps).

4 / 5

Workflow Clarity

The workflow is a clearly sequenced six-phase pipeline with explicit STOP-and-wait checkpoints, enumerated user options ("go" / adjustments / "stop"), state persistence after every phase, 24-hour resume logic, and a two-round examiner review-revision feedback loop. This matches anchor 5 (clear sequence, explicit validation, feedback loops); anchor 4 would require missing or implicit checkpoints, which is not the case.

5 / 5

Progressive Disclosure

The document is well-sectioned with clear headers and its one detailed reference ("../shared-references/reviewer-backends.md") is clearly signaled at the top and one level deep. It stops short of anchor 5 because the referenced shared file is not present in the bundle, the bundle contains no references/ files at all, and inline content such as the patent-type specification tables and the deliverables table could appropriately live in separate reference files.

4 / 5

Total

16

/

20

Passed

Description

82%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 with an explicit, concrete 'Use when...' trigger clause and clear bilingual trigger terms that give it excellent completeness and distinctiveness. Its main weakness is specificity: it describes the pipeline at a macro level rather than enumerating the concrete drafting actions it performs.

DimensionReasoningScore

Specificity

The description names the domain and one macro action ("Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents") with scope qualifiers ("Supports CN (CNIPA), US (USPTO), EP (EPO)", "invention patents and utility models"), but does not list several concrete actions such as prior art search, claims drafting, or specification writing. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than anchor 4, which requires a list of several specific actions.

3 / 5

Completeness

It clearly answers both questions: "what" via "Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents" and "when" via the explicit "Use when user says..." clause with concrete trigger phrases. This matches anchor 5 exactly; anchor 4 would require a less explicit or less specific 'when' clause, which is not the case here.

5 / 5

Trigger Term Quality

The trigger clause includes natural phrases users would actually say — "写专利", "patent pipeline", "专利申请", "draft patent", "写权利要求书" — with good bilingual synonym coverage. It falls short of anchor 5 because common English variants like "file a patent" or "patent an invention" are missing, matching anchor 4 (good coverage, a few natural terms missing).

4 / 5

Distinctiveness Conflict Risk

Patent drafting is a clear niche with distinct triggers ("写专利", "patent pipeline", "写权利要求书") that would not plausibly fire for generic writing, coding, or document skills, matching anchor 5 (clear niche, distinct triggers, minimal conflict risk). It is clearly above anchor 4, which still admits overlap with closely related skills.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/patent-pipeline/SKILL.md

Reviewed

Table of Contents

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.