prior-art-search
Search patent databases and academic literature for prior art relevant to an invention. Use when user says "现有技术检索", "prior art search", "专利检索", "check patents", or wants to find relevant prior art.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 'what' and 'when' clauses, and a distinctive niche. The main weakness is that the capability description could be more specific about the concrete actions performed beyond just 'search' — e.g., analyzing patent claims, generating prior art reports, or comparing inventions against existing patents.
Suggestions
Expand the capability description with more specific actions, e.g., 'Search patent databases and academic literature for prior art, analyze patent claims for overlap, and generate prior art reports summarizing relevant findings.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (patent databases, academic literature) and one core action (search for prior art), but doesn't list multiple specific concrete actions like analyzing claims, comparing patent families, generating novelty reports, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (search patent databases and academic literature for prior art relevant to an invention) and 'when' (explicit 'Use when' clause with specific trigger phrases and a general condition). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms in both Chinese and English: '现有技术检索', 'prior art search', '专利检索', 'check patents', and 'find relevant prior art'. These cover common variations users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of patent-specific terminology, prior art focus, and bilingual Chinese/English trigger terms creates a very distinct niche that is 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, actionable skill for prior art searching with clear workflow steps and concrete search commands. Its main strengths are the specific WebSearch/WebFetch query patterns and the detailed output template. Weaknesses include moderate verbosity in the output template section and references to bundle files that don't exist, slightly undermining progressive disclosure.
Suggestions
Consider moving the detailed output markdown template to a separate template file (e.g., PRIOR_ART_TEMPLATE.md) to reduce the main skill's length and improve progressive disclosure.
Provide the referenced `../shared-references/prior-art-databases.md` bundle file or remove the reference if it doesn't exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary structure like the 'Inputs' section and 'Constants' that could be tighter. The output template is lengthy but arguably necessary for a complex report. Some sections like the FTO disclaimer add modest bloat. | 2 / 3 |
Actionability | Provides concrete, executable search commands (WebSearch and WebFetch with specific query patterns), specific assessment criteria with clear HIGH/MEDIUM/LOW categories, and a detailed output template with exact markdown table structures. Claude can follow these instructions directly. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with logical progression from concept extraction through search, analysis, and output. Each step has explicit sub-tasks. The classification/analysis step serves as a validation checkpoint, and the FTO assessment adds a review layer before final output. | 3 / 3 |
Progressive Disclosure | References a shared file `../shared-references/prior-art-databases.md` and mentions other skills like `/arxiv` and `/semantic-scholar`, but no bundle files are provided to verify these exist. The output template is quite long and could potentially be split into a separate reference file. The skill is somewhat monolithic at ~120 lines. | 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.