portfolio

Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.

Quality

88%

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

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable instruction skill with clear multi-mode workflows and an explicit consequential-action validation gate. Its weakness is conciseness and progressive disclosure: the ~540-line body repeats its caveat across sections and keeps reference-grade material (jurisdiction rules, register schema) inline rather than in separate files.

Suggestions

Consolidate the deadline-verification caveat into one canonical statement and reference it where needed, instead of restating it in Instructions step 8, the report close, the audit output, and the dedicated 'Important' section.

Move the jurisdiction maintenance rules and the register YAML schema into separate reference files (e.g. references/jurisdiction-rules.md and references/register-schema.yaml) and summarize them inline, so the SKILL.md body serves as a lean overview pointing one level deep.

Trim the prose 'Purpose' and 'Works better connected' sections to their essential points to cut length without losing the guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded: the deadline-verification caveat is repeated across Instructions step 8, the report close, the audit output, and a dedicated 'Important' section, and the prose 'Purpose' and 'Works better connected' sections add length that could be trimmed. It is not a 3 because it is verbose rather than lean; not a 1 because it avoids explaining basics Claude already knows and the jurisdiction rules are genuinely specialized.	2 / 3
Actionability	Highly concrete and copy-paste ready: an exact register YAML schema with field comments, full report and audit output templates with emoji buckets, specific invocations like '--report --days 180', and the verbatim consequential-action gate language — well above the 'describes rather than instructs' floor.	3 / 3
Workflow Clarity	Five modes are clearly sequenced (Mode 1 Step 1-3, sub-modes for update), with an explicit validation checkpoint — the consequential-action gate that blocks setting status to 'filed' without an explicit yes — and a refresh-before-report step, satisfying the 'explicit validation steps' anchor.	3 / 3
Progressive Disclosure	The file is well-sectioned but ~540 lines kept entirely inline with no skill-bundle reference files (no references/ or scripts/ exist); the long jurisdiction maintenance rules and the register YAML template are content that could be split into separate reference files. It is not a 1 (organization is clear and external references are one level deep to real files), and not a 3 because it is a monolithic single-file doc rather than an overview pointing to one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that states concrete capabilities and gives an explicit 'Use when' trigger covering the main usage modes. It is specific, naturally worded, and clearly scoped to the IP portfolio domain.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'registrations, renewals, maintenance fees, and use declarations', 'adding or updating an asset', 'recording a maintenance filing', 'auditing the register' — matching the 'Lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both: what ('Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations') and when (an explicit 'Use when checking what's renewing... adding or updating an asset... or auditing the register' clause).	3 / 3
Trigger Term Quality	Uses natural terms a legal/IP user would actually say — 'what's renewing', 'maintenance filing', 'auditing the register', 'gaps, lapses, and use-in-commerce questions' — giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	A clear IP-portfolio niche with distinct triggers (renewals, maintenance fees, use declarations, prosecution/clearance handoffs) that are unlikely to fire for an unrelated skill.	3 / 3
	Total	12 / 12 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 (540 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: anthropics/claude-for-legal
Path: ip-legal/skills/portfolio/SKILL.md
Commit: 4a6c651

Reviewed: 6 days 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.