jurisdiction-format

Compile patent application into jurisdiction-specific filing format. Use when user says "格式转换", "jurisdiction format", "国家格式", "compile patent", or wants formatted patent documents for CN/US/EP filing.

Quality

95%

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

100%

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

A well-structured, token-efficient skill body that delivers specific patent-filing formatting rules across three jurisdictions with a clear sequenced workflow and explicit validation checkpoint. Progressive disclosure is handled cleanly through signaled one-level references.

Dimension	Reasoning	Score
Conciseness	The body is dense with domain-specific formatting knowledge Claude would not reliably know (CNIPA/EPO/USPTO section ordering, two-part claim form, fonts, margins, word limits) and avoids explaining generic concepts; every section earns its tokens.	3 / 3
Actionability	Provides concrete, copy-paste-ready guidance: exact claim phrasing templates, per-jurisdiction section ordering, file output paths, abstract word limits, and specific docx font/margin settings, satisfying the instruction-skill actionable standard.	3 / 3
Workflow Clarity	Six clearly sequenced steps with an explicit Step 5 consistency-check checklist (validation across all formats) and a python-docx availability fallback, giving a feedback loop for this batch operation.	3 / 3
Progressive Disclosure	SKILL.md acts as an overview with one-level-deep, clearly signaled references to ../shared-references/patent-format-{cn,us,ep}.md; no nested reference chains and content is appropriately split.	3 / 3
	Total	12 / 12 Passed

Description

90%

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 that clearly communicates its patent-filing niche and provides explicit bilingual trigger guidance. It is held back only on specificity, where a single core action is named rather than a fuller enumeration of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the patent-filing domain and a concrete action ("Compile patent application into jurisdiction-specific filing format") but lists a single core action rather than multiple distinct concrete actions.	2 / 3
Completeness	Explicitly states both what the skill does ("Compile patent application into jurisdiction-specific filing format") and when to use it via an explicit "Use when" clause with concrete triggers.	3 / 3
Trigger Term Quality	Provides good bilingual coverage of natural user phrases ("格式转换", "jurisdiction format", "国家格式", "compile patent", "formatted patent documents for CN/US/EP filing") that a user would plausibly say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (jurisdiction-specific patent filing compilation for CN/US/EP) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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/jurisdiction-format/SKILL.md
Commit: c5f3d5b

Reviewed: about 1 hour 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.