CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patent-assistant

Assists R&D teams with patent technical disclosure drafting and patent/novelty search analysis; use when users ask to write a patent disclosure, structure an invention description, search related patents, or assess novelty.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/patent-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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-organized, mostly actionable skill with concrete CLI examples and a clear worked example, but it underuses its own bundle: one shipped script is undocumented, reference material is inlined rather than split out, and the multi-platform search workflow lacks validation/error-recovery checkpoints. The description side is stronger than the body.

Suggestions

Document scripts/generate_disclosure.py in the Example Usage and Implementation Details sections (or remove it from the bundle), so both shipped tools are actually reachable from SKILL.md.

Add validation and feedback loops to the patent search workflow: check for failed or empty platform results, retry or broaden keywords, and confirm result quality before issuing a preliminary novelty judgment.

Trim duplication to improve token efficiency: collapse 'Key Features' into 'When to Use', and either shorten the 50-line example disclosure or move the IPC table and full example into a references/ file.

DimensionReasoningScore

Conciseness

The body is efficient and assumes domain competence — it never explains what a patent or a CLI is, and the CLI examples and checklists are tight. Minor trimmable material keeps it below the lean anchor of 5: the 'Key Features' section substantially repeats 'When to Use', the ~50-line example disclosure restates the section template already listed under Implementation Details, and the 'Dependencies' section hedges about a script that actually ships in the bundle ('Exact runtime dependencies may vary depending on how scripts/patent_search.py is implemented in your repository').

4 / 5

Actionability

Mostly executable guidance: copy-paste-ready CLI invocations with flags ('python scripts/patent_search.py "..." -s all -p -a'), a concrete information-collection checklist, and a full worked output example. Not fully a 5 because the search-output example is labeled 'conceptual' rather than shown, and the disclosure-generation workflow never mentions the bundled scripts/generate_disclosure.py, leaving the main generation path without a concrete command.

4 / 5

Workflow Clarity

Both workflows are clearly sequenced (collect → synthesize → optimize; extract keywords → execute search → analyze results) with an 'ask if missing' checkpoint for information collection. However, validation is absent: the parallel multi-platform search is a batch operation with no guidance on handling failed or empty platform results, retrying, or adjusting keywords, and there is no verification step before presenting novelty conclusions. Per the batch-operations cap, this cannot score above 3.

3 / 5

Progressive Disclosure

Section organization is clear, but measured against the actual bundle, structure is weaker than it looks: the bundle contains two scripts yet only scripts/patent_search.py is referenced — scripts/generate_disclosure.py is never mentioned — and reference material (the IPC suggestions table, the full worked disclosure example) is inlined in a ~190-line SKILL.md with no references/ files. This matches the 'some structure, content that should be separate is inline' anchor better than the well-split anchor of 4.

3 / 5

Total

14

/

20

Passed

Description

87%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: concrete capabilities, an explicit 'use when' clause with four natural trigger phrases, and a clearly delineated patent niche. The only minor improvement is broader synonym coverage for search-related triggers.

DimensionReasoningScore

Specificity

The description names concrete actions across the patent domain — 'patent technical disclosure drafting and patent/novelty search analysis' — and the trigger clause enumerates four distinct tasks ('write a patent disclosure, structure an invention description, search related patents, or assess novelty'), matching the anchor for several specific actions with minor gaps. It falls short of 5 because capability synonyms users might use (e.g., prior art search, patentability analysis) are not covered, and it does not fully describe the optimization/claim-direction support the body provides.

4 / 5

Completeness

It explicitly answers both questions: the 'what' is 'Assists R&D teams with patent technical disclosure drafting and patent/novelty search analysis' and the 'when' is a concrete 'use when users ask to...' clause listing four trigger phrases. This matches the top anchor of clearly and explicitly stating both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Trigger phrases like 'write a patent disclosure', 'structure an invention description', 'search related patents', and 'assess novelty' are natural wordings an R&D user would actually say, giving good keyword coverage. A few common variations are missing ('prior art search', 'patentability', 'draft a patent application'), keeping it below the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The patent-drafting/patent-search niche is clearly distinct from general document or research skills, and the triggers ('patent disclosure', 'search related patents', 'assess novelty') are unlikely to fire for unrelated skills. Minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/patent-assistant/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.