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.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger term coverage in both Chinese and English, clear 'when' guidance, and a distinctive niche. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'compile into filing format' — listing specific sub-tasks like formatting claims, generating cover sheets, or structuring specifications would strengthen it.
Suggestions
Expand the capability description with more specific actions, e.g., 'Compile patent application into jurisdiction-specific filing format, including structuring claims, formatting specifications, and generating required cover sheets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (patent application) and a core action (compile into jurisdiction-specific filing format), but it doesn't list multiple specific concrete actions like 'extract claims, format drawings, generate abstracts, structure specifications'. | 2 / 3 |
Completeness | Clearly answers both 'what' (compile patent application into jurisdiction-specific filing format) and 'when' (explicit 'Use when' clause with specific trigger phrases and use cases like wanting formatted patent documents for CN/US/EP filing). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms in both Chinese and English: '格式转换', 'jurisdiction format', '国家格式', 'compile patent', and specific jurisdiction codes CN/US/EP. Good coverage of bilingual user queries and common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining patent applications with jurisdiction-specific formatting. The specific trigger terms (格式转换, CN/US/EP filing, compile patent) are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill for patent format compilation across three jurisdictions. Its main strengths are the clear multi-step workflow with validation checkpoints and the concrete, jurisdiction-specific formatting rules. Its main weakness is potential redundancy between the inlined formatting details and the referenced shared format files, which inflates the token cost without clear justification.
Suggestions
Reduce inlined jurisdiction-specific formatting details that should already be covered in the referenced shared format files (patent-format-cn.md, patent-format-us.md, patent-format-ep.md), keeping only key rules and deferring details to those files.
Provide the referenced bundle files (shared-references/patent-format-*.md) or note their expected contents so the progressive disclosure structure is complete and verifiable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-structured, but includes some content that could be tightened—e.g., the full output summary template with tables is verbose, and some formatting conventions (like font names, margin sizes) could be referenced from the shared format files rather than inlined. However, most content is domain-specific knowledge Claude wouldn't inherently know. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific file paths, exact formatting conventions per jurisdiction (e.g., '其特征在于', 'characterised in that', 'FIG. 1'), exact section ordering for each jurisdiction, specific word/character limits, font specifications, and margin measurements. The instructions are copy-paste ready for implementation. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 6 steps with logical progression from jurisdiction determination through format generation to consistency checking and output summary. Step 5 provides an explicit validation checklist, and the docx fallback to markdown is a good error recovery pattern. The consistency check serves as a proper verification checkpoint before final output. | 3 / 3 |
Progressive Disclosure | The skill references shared format files (patent-format-cn.md, patent-format-us.md, patent-format-ep.md) which is good progressive disclosure design, but then proceeds to inline substantial jurisdiction-specific formatting details that presumably overlap with those referenced files. No bundle files are provided to verify the references exist. The inline content could potentially be shorter if it properly deferred to those shared references. | 2 / 3 |
Total | 10 / 12 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 — 9 / 11 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 | 9 / 11 Passed | |
- Commit
2028ac4
- 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.