entity-compliance

Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

The body is highly actionable and clearly workflow-sequenced with validation gates, but it is a long monolithic file with repeated paths and overlapping caveats that hurt token efficiency and leave no room for progressive disclosure to reference files.

Suggestions

Define the long path `~/.claude/plugins/config/claude-for-legal/corporate-legal/` once as a variable or short alias at the top and reuse it, instead of repeating the full path dozens of times.

Move the detailed tracker YAML schema, output-format templates, and per-state/entity-type deadline reference (e.g. the Delaware corp/LLC/LP split) into separate reference files (e.g. TRACKER_SCHEMA.md, DEADLINES.md) and link to them one level deep, keeping SKILL.md as a lean overview.

Consolidate the three overlapping risk caveats (deadline reference, jurisdiction assumption, entity-type disambiguation) into a single concise "Caveats" block to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and domain-specific rather than generic padding, but at ~450 lines it repeats the full plugin file path many times and overlaps the deadline-caveat / jurisdiction-assumption / entity-type-disambiguation warnings that could be consolidated; it is not score 3 because it is not lean, and not score 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Concrete, copy-paste-ready guidance: an exact tracker YAML schema, specific CLI flags, full output-format templates with named fields, a defined CSV column list, and ready-to-use prompt blocks — fully actionable even though it is instruction-only rather than code.	3 / 3
Workflow Clarity	Five modes are clearly sequenced with numbered steps and explicit validation checkpoints — notably the consequential-action gate before recording a filing, status-setting rules, and the bulk-sweep confirm loop — matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	Well-sectioned but monolithic: a single ~450-line SKILL.md with no bundle files and no one-level-deep references, while the tracker schema, output templates, and per-state deadline details are content that could be split out; it is not score 1 because organization is good with no nested references, and not score 3 because nothing is split or linked out.	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.

The description is specific, uses natural trigger terms with an explicit "Use when" clause, answers both what and when, and occupies a distinct niche. Voice is third person throughout ("Maintains", "calculates", "surfaces"), so no specificity penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "initialize, report upcoming deadlines, update status, run health audit, export to CSV" plus "calculates filing deadlines" and "surfaces what's due" — matching the multiple-specific-actions anchor, not the score-2 "some actions" anchor.	3 / 3
Completeness	Clearly answers both what (the enumerated actions and the compliance-tracker.yaml mechanism) and when (an explicit "Use when" trigger clause), satisfying the top anchor; it is not score 2 because the when is explicit, not implied.	3 / 3
Trigger Term Quality	Explicit "Use when user says 'entity compliance', 'filing deadlines', 'annual reports due', 'entity tracker', 'what filings are due', 'entity health', or 'good standing'" gives good coverage of natural phrasings a user would actually say.	3 / 3
Distinctiveness Conflict Risk	A clear niche (entity compliance / filing deadlines) with distinct triggers unlikely to collide with other skills, matching the "clear niche with distinct triggers" anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: anthropics/claude-for-legal
Path: corporate-legal/skills/entity-compliance/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.