CtrlK
BlogDocsLog inGet started
Tessl Logo

patent-review

Get an external patent examiner review of a patent application. Use when user says "专利审查", "patent review", "审查意见", "examiner review", or wants critical feedback on patent claims and specification.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 body is highly actionable with a clear, well-validated multi-round workflow and concrete MCP integration. Its weaknesses are token efficiency (long inline prompts and redundant rules) and progressive disclosure (everything inline with no reference files).

Suggestions

Move the long Round-1 office-action prompt and the Round-2 follow-up prompt into reference files (e.g. references/round1_prompt.md) and link to them, reducing inline tokens and improving progressive disclosure.

Trim the Key Rules section to points not already covered by the workflow steps (e.g. the xhigh-effort and persona rules are already stated in Constants/Step 2) to reduce redundancy.

Collapse the seven examination-category sub-bullets into a referenced checklist so the core SKILL.md body stays a lean overview.

DimensionReasoningScore

Conciseness

It assumes Claude's competence with no concept-padding, but the ~60-line embedded office-action prompt and the Key Rules section (which restates workflow guidance) could be tightened, matching the mostly-efficient anchor rather than fully lean.

2 / 3

Actionability

Provides copy-paste-ready MCP tool calls with exact model and config (gpt-5.6-sol, xhigh reasoning), concrete file paths (patent/CLAIMS.md, patent/PATENT_REVIEW.md), and a full report template — fully executable guidance.

3 / 3

Workflow Clarity

A clear five-step sequence with severity-based fix prioritization, an explicit round-2 re-examination feedback loop, and a final completion checklist — the strongest anchor.

3 / 3

Progressive Disclosure

Well-sectioned into headers, but as a single ~200-line file with large inline prompt templates and no bundle references to offload detail, it stops at the some-structure anchor rather than a clean overview-plus-references split.

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 that clearly states its purpose and provides explicit, natural bilingual triggers for when to invoke it. The only gap is specificity — it names one action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ("Get an external patent examiner review of a patent application"), but lists a single action rather than multiple specific concrete actions, matching the score-2 anchor.

2 / 3

Completeness

Explicitly answers what it does ("Get an external patent examiner review...") and when to use it with an explicit "Use when user says..." trigger clause, satisfying both halves.

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say across both languages — "patent review", "examiner review", "专利审查", "审查意见", and "critical feedback on patent claims" — giving good trigger coverage.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear patent-examiner niche with distinct bilingual triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.