CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

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%Weight 40%Scale 1-5

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

The body delivers a well-sequenced, near-executable two-round examiner-review workflow with severity gating, an explicit feedback loop, a score threshold, and a complete report template. The weaknesses are a dangling shared reference whose routing boilerplate is duplicated inline, and placeholder-heavy prompt templates.

Suggestions

Move the reviewer-routing contract (the opening blockquote and the repeated 'Resolve this reviewer slot' notes in Steps 2 and 4) into the referenced reviewer-backends.md and cite it once, removing the three duplicated passages.

Ship ../shared-references/reviewer-backends.md with the skill bundle, or inline the minimal routing decision — as written the link is dangling from this bundle, leaving the routing step unexecutable.

Add an explicit fallback branch for REVIEW_UNAVAILABLE (e.g., record it in patent/PATENT_REVIEW.md and stop) so the workflow has a defined path when no reviewer backend resolves.

DimensionReasoningScore

Conciseness

The body is dense operational content (Constants, Prerequisites, Inputs, full prompt templates, report template, Key Rules) with no explanation of concepts Claude already knows, but the reviewer-routing boilerplate ("Before each reviewer slot, follow [Selectable Reviewers]...") is restated at Steps 2 and 4 ("> Resolve this reviewer slot first...") and could be trimmed. Fits 'efficient; minor instances that could be trimmed' rather than the fully lean anchor, and is well above 'unnecessary explanation'.

4 / 5

Actionability

Concrete, near-copy-paste guidance: an executable `claude mcp add codex...` command and full MCP call blocks with model ("gpt-6-astra"), config ("{\"model_reasoning_effort\": \"xhigh\"}"), and complete prompt text, plus a fully specified report template. Minor gaps keep it below the top anchor: prompts rely on "[all claims]"-style placeholders, and the routing step depends on an external file not present in the bundle.

4 / 5

Workflow Clarity

Five clearly sequenced steps (Gather → Round 1 → Implement Fixes → Round 2 → Report) with explicit validation checkpoints: severity gating ("CRITICAL issues... Must be fixed before proceeding"), a built-in feedback loop (Round 2 re-examination via codex-reply asking "Are the previous rejections overcome?"), a score-threshold rule ("below 5/10 after Round 2, recommend significant rework"), and a final checklist. Matches the anchor for clear sequence with explicit validation, feedback loops, and checklists; the one below lacks these checkpoints.

5 / 5

Progressive Disclosure

Internal structure is clear (Constants/Prerequisites/Inputs/Workflow/Key Rules), but the only external reference ("../shared-references/reviewer-backends.md") is not present in the bundle, and the routing contract that belongs in that file is instead inlined and duplicated three times in the body. Fits 'some structure but could be better organized; references present but... content that should be separate is inline' — above the minimal-structure anchor because section organization is good.

3 / 5

Total

16

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly and explicitly answers both what the skill does and when to use it, with concrete bilingual trigger phrases in a well-differentiated patent-examination niche. The only mild weakness is that the capability statement is a single action rather than an enumeration of the review's concrete coverage.

DimensionReasoningScore

Specificity

"Get an external patent examiner review of a patent application" names the domain and one concrete action, but does not enumerate what the review covers (claims clarity, novelty, enablement, etc.). Matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not 4 because several distinct actions are not listed, not 2 because the named action is concrete rather than generic.

3 / 5

Completeness

Both parts are explicit: what ("Get an external patent examiner review of a patent application") and when ("Use when user says \"专利审查\", \"patent review\", \"审查意见\", \"examiner review\", or wants critical feedback on patent claims and specification.") — concrete trigger phrases attached to a clear capability statement, exactly the top anchor.

5 / 5

Trigger Term Quality

Explicit triggers "patent review", "examiner review", "专利审查", "审查意见", plus the intent clause "wants critical feedback on patent claims and specification", give good bilingual coverage of natural phrases. Not 5 because a few natural terms are missing (English "office action", "patentability", "claims review"); well above the generic-keyword anchors.

4 / 5

Distinctiveness Conflict Risk

Triggers are patent-specific ("patent review", "专利审查", "examiner review", "critical feedback on patent claims and specification"), occupying a clear niche with minimal overlap risk against generic review or document skills; no broader terms that would fire for the wrong skill.

5 / 5

Total

17

/

20

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 — 13 / 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

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/patent-review/SKILL.md

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.