CtrlK
BlogDocsLog inGet started
Tessl Logo

uspto-database

Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.

59

Quality

70%

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 ./backend/cli/skills/databases/uspto-database/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.

The content is well-structured with excellent progressive disclosure and largely executable examples, but it includes some verbosity and lacks validation checkpoints for its batch/destructive workflows. Tightening the API enumeration and adding verify-and-retry steps would improve it.

Suggestions

Add explicit validation/error-handling checkpoints to the portfolio monitoring and comprehensive-analysis workflows (e.g., check API responses for errors before processing, retry on rate-limit).

Trim or tabulate the twelve 'Additional APIs' one-liners, or move them entirely into references/additional_apis.md to reduce inline padding.

Consolidate the repeated 'Reference Documentation' sections into a single clearly-labeled reference index to avoid redundant navigation blocks.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code, but includes padded ecosystem enumeration (twelve one-line additional-API entries) and minor over-explanation that could be tightened.

3 / 5

Actionability

It provides multiple copy-paste-ready executable Python examples across searching, PEDS, trademarks, and assignments, with only minor gaps such as placeholder API keys.

4 / 5

Workflow Clarity

Tasks are numbered and sequenced (Task 1-5), but batch operations like portfolio monitoring and comprehensive analysis lack explicit validation checkpoints and error-recovery feedback loops, capping this at 3 per the destructive/batch guideline.

3 / 5

Progressive Disclosure

The SKILL.md serves as a clear overview with well-signaled, one-level-deep references to real references/*.md and scripts/*.py files, with bulk detail appropriately split into separate files.

5 / 5

Total

15

/

20

Passed

Description

75%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 is specific and well-niched with strong trigger terms, but it omits an explicit 'Use when...' trigger clause, which limits its completeness score. Adding explicit usage triggers would lift it toward the top anchors.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when performing patent or trademark searches, prior art analysis, or examining USPTO prosecution history').

Include natural user phrasings and synonyms such as 'patent search', 'trademark lookup', and 'patent prosecution' to broaden trigger coverage.

Consider mentioning '.xml' or docket/application-number style triggers if users commonly phrase requests around those.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete API capabilities — 'patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

It clearly answers 'what' by listing capabilities, but there is no explicit 'Use when...' trigger clause, so the 'when' is only weakly implied — capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural terms like 'patent', 'trademark', 'prior art searches', and 'IP analysis' are present, but common variations and synonyms (e.g., 'patent search', 'trademark lookup', file extensions) are partly missing.

4 / 5

Distinctiveness Conflict Risk

It is niched specifically to USPTO/IP data with distinct triggers, making it unlikely to fire for unrelated skills.

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (607 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
synthetic-sciences/openscience
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.