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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable with a clear validated workflow and jurisdiction-specific conventions, scoring well on actionability and workflow clarity. Weaker on conciseness (duplicate checklists, verbose summary template) and progressive disclosure (inline detail and missing bundled reference files).

Suggestions

De-duplicate the consistency checklist: keep it once in Step 5 and have the OUTPUT_SUMMARY reference it rather than restating all items.

Move the detailed CN/US/EP section-order and claim-format rules into the referenced shared-references files (and ensure those files actually exist in the bundle) so SKILL.md stays a concise overview.

Trim the OUTPUT_SUMMARY markdown template to a minimal skeleton since the per-jurisdiction file lists are already implied by the workflow steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but the consistency checklist is duplicated (Step 5 and the OUTPUT_SUMMARY template) and the summary template block is verbose, so it could be tightened.	2 / 3
Actionability	Provides concrete, specific guidance: exact claim phrasing ("1. 一种[主题]的方法，...其特征在于..."), fonts (宋体/SimSun, 黑体/SimHei), margins, word limits, and output paths, making it copy-ready for an instruction skill.	3 / 3
Workflow Clarity	A clear six-step sequence with an explicit consistency-check checkpoint (Step 5), word-count verifications, and a python-docx availability check with markdown fallback for this batch operation.	3 / 3
Progressive Disclosure	The body is well-sectioned, but the detailed CN/US/EP formatting rules are inline rather than split out, and the referenced shared-references files are not present in the bundle (no references/ directory exists), so the disclosure structure is only partially realized.	2 / 3
	Total	10 / 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: it clearly defines the task, gives natural multilingual trigger phrases, and explicitly states when to invoke it. The only minor weakness is that capability specificity rests on one main action rather than an enumerated list.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("Compile patent application into jurisdiction-specific filing format") and domain (CN/US/EP), but lists a single primary action rather than the multiple distinct concrete actions the top anchor calls for.	2 / 3
Completeness	Explicitly states both what it does (compile into jurisdiction-specific filing format) and when to use it via a "Use when user says..." clause with concrete triggers.	3 / 3
Trigger Term Quality	Provides natural multilingual triggers a user would actually say ("格式转换", "jurisdiction format", "国家格式", "compile patent") plus "formatted patent documents for CN/US/EP filing", giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Patent filing compilation is a clear niche with jurisdiction-specific triggers, making it 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
Commit: 82076e5

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.