expansion-update

Update the status of an in-progress international expansion project — recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities. Use when work has happened since the last session and the expansion tracker needs to reflect the current state.

Quality

86%

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

87%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 tight, highly actionable skill body with concrete paths and templates and good progressive disclosure through a clearly signaled reference. The main gap is workflow clarity: the multi-step process lacks an explicit validation/verification checkpoint before persisting changes.

Suggestions

Add an explicit verification checkpoint before writing the tracker, e.g. 'Summarize the proposed status changes and confirm with the user before writing the file.'

Include a light feedback loop for the destructive-ish write step: if the tracker is malformed or dependencies break after updates, surface the issue and re-confirm rather than silently saving.

Trim the opening paragraph that restates the frontmatter description so the body starts directly with the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean — concrete file paths, prompt templates, and output blocks with no padding or explanation of concepts Claude already knows. The only slack is the opening paragraph restating the frontmatter description, which is minor; overall every token earns its place.	3 / 3
Actionability	Guidance is concrete and copy-paste ready: exact tracker path ('expansion-[slug].yaml'), an exact fallback message, a single-prompt update template, and fixed output format blocks. This matches the fully-executable anchor for an instruction-only skill.	3 / 3
Workflow Clarity	Seven steps are clearly sequenced with edge-case handling (missing tracker, overdue items, unblocking), but there is no explicit validation checkpoint or feedback loop (e.g., confirm changes with the user before writing, verify no orphaned dependencies). The sequence is present and detailed but checkpoints are implicit, matching the 2-anchor rather than the validation-gated 3-anchor.	2 / 3
Progressive Disclosure	The body is a concise overview split into clear Instructions/Examples sections, with the detailed schema, status rules, and dependency logic deferred to a clearly signaled one-level-deep reference ('load it before doing substantive work'). Organization and navigation are clean with no deep nesting.	3 / 3
	Total	11 / 12 Passed

Description

85%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 specific, complete, and distinct description with an explicit 'Use when' clause and three concrete actions. Its only weak spot is trigger-term quality: the activation condition is situational rather than a rich set of natural keywords users would say.

Suggestions

Expand the 'Use when' clause with natural keyword variations a user might actually say, e.g. 'Use when updating an expansion tracker, checking expansion status, or when work has happened on a country expansion since the last session.'

Consider adding the concrete trigger noun 'country expansion' alongside 'international expansion project' to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities' — matching the anchor for several specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly answers both 'what' (update status of an in-progress expansion project, recalculating/unblocking/flagging/surfacing) and 'when' via an explicit 'Use when...' clause, matching the anchor for both answered with explicit triggers.	3 / 3
Trigger Term Quality	The trigger is situational ('Use when work has happened since the last session and the expansion tracker needs to reflect the current state') with only 'expansion project'/'expansion tracker' as natural terms; it lacks broader coverage of keyword variations a user would actually say. It is above the jargon-only anchor but below the multi-variation 3-anchor.	2 / 3
Distinctiveness Conflict Risk	The international-expansion-project tracker niche is narrow and tied to the employment-legal domain, making it unlikely to fire for unrelated skills and matching the clear-niche anchor.	3 / 3
	Total	11 / 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: employment-legal/skills/expansion-update/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.