CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patent-landscape

Use when analyzing biotech patent landscapes, identifying white spaces in pharmaceutical IP, tracking competitor patents, or assessing freedom to operate for drug development. Provides comprehensive patent analysis and strategic insights for life sciences innovation.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/patent-landscape/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%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 is dominated by generic template boilerplate repeated from the description, while its patent-specific content is largely fabricated: the documented Python API and CLI do not match the actual scripts/main.py, and most referenced files are missing. Genuine executable guidance is limited to two audit commands; the real script's interface (--target, --area) is never shown.

Suggestions

Document the actual script interface: replace the fabricated PatentLandscapeAnalyzer API and scripts/patent_landscape.py CLI with the real class (PatentLandscape in scripts/main.py) and its actual flags (--target, --area), including a working example invocation.

Fix or remove broken references: references/ipc-classifications.md, references/patent-search-strategies.md, and examples/landscape-reports/ do not exist — either create them or delete the citations, keeping only the real references/audit-reference.md.

Cut boilerplate: remove the verbatim description repeats in 'When to Use' and 'Key Features', the generic template sections (Dependencies, Output Requirements, Input Validation, Response Template), and the leaked internal path '20260318/scientific-skills/Evidence Insight/patent-landscape'; move the inlined API/CLI reference material into reference files to slim SKILL.md to an overview.

DimensionReasoningScore

Conciseness

The ~240-line body is noticeably padded: the frontmatter description is repeated verbatim three times ("When to Use", "Key Features", scope framing), and large boilerplate sections ("Dependencies", "Implementation Details", "Output Requirements", "Input Validation", "Response Template") repeat generic evidence-insight template language ("bounded deliverable", "evidence insight tasks") unrelated to patents.

2 / 5

Actionability

Only the audit commands ("python -m py_compile scripts/main.py", "python scripts/main.py --help") are genuinely executable. The core capability examples import a nonexistent module and class ("from scripts.patent_landscape import PatentLandscapeAnalyzer", with analyzer.search_patents/analyze_competitors/assess_fto methods absent from the actual script), and the CLI examples invoke "python scripts/patent_landscape.py --query ..." — a file that doesn't exist — while the real script's actual interface (--target/--area) is never documented. The guidance is therefore misleading rather than merely incomplete.

2 / 5

Workflow Clarity

A sequence with checkpoints exists (confirm inputs, validate scope, py_compile quick check, run, fallback path on failure), but it is generic template language duplicated across "Workflow", "Example Usage", and "Implementation Details" (including a confusing self-reference "See ## Workflow above"), and the steps never show how to actually perform a patent analysis run with the real script arguments, leaving key operational gaps.

3 / 5

Progressive Disclosure

The body cites "references/ipc-classifications.md", "references/patent-search-strategies.md", and "examples/landscape-reports/", none of which exist in the bundle (only references/audit-reference.md is real), so navigation is broken; additionally the bulk API reference (Core Capabilities, CLI usage, data-source lists) is inlined in SKILL.md where it belongs in separate reference files.

2 / 5

Total

9

/

20

Passed

Description

78%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 solid description with an explicit, well-targeted "Use when" trigger clause for the biotech/pharma patent niche. Its main weakness is a vague second sentence ("comprehensive patent analysis and strategic insights") that pads instead of stating concrete deliverables, and missing common synonyms such as "prior art" or "FTO".

Suggestions

Replace the buzzword tail 'Provides comprehensive patent analysis and strategic insights for life sciences innovation' with concrete deliverables, e.g. 'Generates landscape reports covering white spaces, competitor portfolios, and freedom-to-operate risk for drug development programs.'

Add missing natural trigger synonyms such as 'prior art', 'patentability', 'FTO', and 'patent portfolio analysis' so users phrasing the request differently still match.

State the output format explicitly (e.g. report/summary artifact) to sharpen the 'what' half of the description.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "identifying white spaces in pharmaceutical IP", "tracking competitor patents", "assessing freedom to operate for drug development" — but closes with buzzword filler ("Provides comprehensive patent analysis and strategic insights for life sciences innovation") that adds no concrete capability, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Both parts are present: an explicit "Use when analyzing biotech patent landscapes... or assessing freedom to operate" trigger clause plus a what-clause ("Provides comprehensive patent analysis"). It falls short of the 5 anchor because the what is stated generically ("comprehensive patent analysis and strategic insights") rather than naming concrete deliverables.

4 / 5

Trigger Term Quality

Natural phrases like "biotech patent landscapes", "white spaces", "competitor patents", and "freedom to operate" match what a user in this domain would actually say, but common variations like "prior art", "patentability", "patent portfolio", or "FTO" are missing.

4 / 5

Distinctiveness Conflict Risk

"Biotech patent landscapes" and "pharmaceutical IP" carve out a clear niche with distinct trigger terms; conflict risk with generic research or document skills is minimal.

5 / 5

Total

17

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/patent-landscape/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.