CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patent-novelty-check

Assess patent novelty and non-obviousness against prior art. Use when user says "专利查新", "patent novelty", "可专利性评估", "patentability check", or wants to evaluate if an invention is patentable.

Quality

85%

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

82%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.

A well-structured, highly actionable instruction skill: concrete templates, decision matrices, verdict criteria, and an explicit independent-verification step with a fallback path. Weaknesses are minor — reviewer-routing boilerplate padding, no handling for a missing prior-art input, and unverifiable out-of-bundle shared references.

DimensionReasoningScore

Conciseness

The body is dense and task-focused with no explanation of concepts Claude already knows (no patent-law primer, no library overviews); tables, templates, and rules are all load-bearing. The main trimmable content is the reviewer-routing boilerplate block and the "Adapted from /novelty-check" lineage note, which are minor instances of over-explanation — matching the 'efficient; minor instances that could be trimmed' anchor rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact anticipation matrix layout with verdict rules ("ANTICIPATED: One reference discloses every element"), a complete spawn_agent template with model and reasoning_effort specified, defined motivation-to-combine criteria, per-jurisdiction pass/fail formats, and a copy-paste-ready output file template. It is not level 4's 'minor gaps' — the common cases (novel, obvious, needs amendment) each have concrete templates covering them.

5 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit independent-examiner verification checkpoint (Step 4) and a rejected-claim feedback path (recommended amendments), plus an explicit fallback when reviewer delegation is unavailable. It falls short of level 5 because some checkpoints are missing or implicit: there is no instruction for what to do when the required input patent/PRIOR_ART_REPORT.md does not exist, and no confirmation that the output file was written correctly. It is clearly above level 3, which lacks checkpoints entirely.

4 / 5

Progressive Disclosure

The single-file body is well-sectioned (Constants, Inputs, Shared References, Workflow, Key Rules) and shared references are clearly signaled in a dedicated section pointing one level deep (patent-writing-principles.md, patent-format-us.md, reviewer-backends.md). It sits at the 'good structure, references mostly clear' level rather than 5 because the shared references live outside the skill bundle and cannot be verified as navigable from it, and some framework detail (jurisdiction standards) is inlined that could arguably live in those references.

4 / 5

Total

17

/

20

Passed

Description

86%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.

A strong description: explicit what-and-when structure with comprehensive bilingual trigger terms that clearly match how users would request this task. The main weakness is that the capability list is narrow relative to what the skill actually does, and there is minor overlap risk with a prior-art-search sibling skill.

DimensionReasoningScore

Specificity

"Assess patent novelty and non-obviousness against prior art" names the domain with 1-2 concrete actions (novelty assessment, non-obviousness assessment) but stops there — no mention of claim drafting, jurisdiction-specific analysis, or amendment recommendations that the body actually covers. It is not vague (ruling out 1-2), but coverage of capabilities is not comprehensive (ruling out 4-5).

3 / 5

Completeness

The description explicitly answers 'what' ("Assess patent novelty and non-obviousness against prior art") and 'when' with an explicit "Use when..." clause listing concrete trigger phrases. This is a direct match for the anchor where both what and when are clearly and explicitly stated with concrete trigger phrases; level 4's 'when could be more explicit' does not apply since four explicit triggers are given.

5 / 5

Trigger Term Quality

"专利查新", "patent novelty", "可专利性评估", "patentability check", "wants to evaluate if an invention is patentable" covers natural trigger phrases comprehensively in both English and Chinese, including synonyms and both noun/verb phrasings a user would naturally say. This matches the comprehensive-synonyms anchor, exceeding the 'good coverage, a few missing' level of 4.

5 / 5

Distinctiveness Conflict Risk

The patent-novelty/patentability niche is fairly distinct with dedicated bilingual triggers, giving minimal conflict risk with unrelated skills. However, "against prior art" and "patentability" leave minor overlap risk with a closely related prior-art-search skill, matching the 'mostly distinct; minor overlap risk with closely related skills' anchor rather than the fully-distinct level 5.

4 / 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/skills-codex/patent-novelty-check/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.