uspto-database

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/uspto-database/SKILL.md

Quality

Content

68%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 skill body is highly actionable with executable code and well-organized references to bundle files, but it is verbose from redundant capability listings and lacks explicit validation checkpoints in its batch/retrieval workflows. Tightening the duplication and adding error-handling guidance would lift the weaker dimensions.

Suggestions

Collapse the triple listing of API capabilities (Overview, 'When to Use', 'API Ecosystem') into a single concise section to reduce padding.

Move the inline query-operator, endpoint, transaction-code, and status-code tables into the corresponding reference files, keeping only a minimal example in SKILL.md.

Add explicit validation/error-handling checkpoints to the portfolio and comprehensive-analysis examples (check response status, handle rate-limit/empty results, retry on failure).

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable but noticeably padded — capabilities are listed three times (Overview, 'When to Use', 'API Ecosystem') and inline query operators, endpoint lists, and transaction/status code tables duplicate content already in the reference files.	3 / 5
Actionability	Provides fully executable, copy-paste-ready Python examples using the bundled helper scripts plus direct requests-based API calls, covering the common search, retrieval, and analysis cases.	5 / 5
Workflow Clarity	Tasks are sequenced (Task 1–5) and a combined analysis example exists, but validation checkpoints are absent or implicit; the portfolio/comprehensive examples perform batch retrievals without systematic error checking or retry feedback loops.	3 / 5
Progressive Disclosure	Structure is good with clearly signaled, one-level-deep references ('See references/patentsearch_api.md for...') and listed helper scripts, though a fair amount of API detail that could live in the reference files is inlined in SKILL.md.	4 / 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 distinctive, clearly carving out a USPTO IP-data niche with concrete capabilities. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the invocation context only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs patent or trademark data, prior art searches, or USPTO prosecution history.'

Include common synonyms users say, such as 'prosecution history', 'trademark status', and 'IP portfolio analysis'.

Tighten 'IP analysis' to a more concrete action phrase like 'analyzing patent portfolios' to strengthen the 'when' guidance.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions across the domain — 'patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR' — giving comprehensive coverage rather than just naming the domain.	5 / 5
Completeness	The 'what' is explicit, but the 'when' is only weakly implied by the purpose clause 'for IP analysis and prior art searches' with no 'Use when...' trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('patent/trademark searches', 'prior art searches', 'office actions'), but misses common synonyms such as 'prosecution history', 'IP portfolio', or 'trademark status'.	4 / 5
Distinctiveness Conflict Risk	The USPTO/patent/trademark/PEDS/TSDR niche is highly specific with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (605 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/uspto-database/SKILL.md
Commit: d5ae560

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.