expansion-kickoff

Kick off international expansion planning for a new country — gathers intake, runs EOR vs. entity framing, drafts cross-functional questions, surfaces country-specific flags, and creates a persistent tracker. Use when someone says "we're hiring in [country]", "expansion to [country]", or "first hire in [country]".

Quality

92%

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

85%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 clean, well-structured orchestrator body that is concise and well-sequenced with a clear guardrail checkpoint and sound progressive disclosure. Its main weakness is that the core expansion actions are delegated to a reference skill rather than concretely specified in-body.

Suggestions

Inline a brief outline of the substantive workflow — intake questions, EOR-vs-entity decision criteria, and tracker schema fields — so the body gives concrete guidance even if the `international-expansion` reference skill is unavailable.

Specify what 'run the full workflow' entails by listing the reference skill's key steps or linking to a specific section, so Claude knows the expected sequence without loading another skill blind.

Add a short verification step before creating the tracker (e.g., confirm intake is complete and the EOR/entity decision is recorded) to close the action loop.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept-explanation padding, assuming Claude's competence; the one-line overview and four numbered steps each earn their place, though the opening sentence lightly duplicates the frontmatter.	3 / 3
Actionability	Orchestration guidance is concrete (exact plugin paths to load, an exact guardrail message, an exact output file), but the substantive expansion work is delegated via 'run the full workflow' of the `international-expansion` reference skill, leaving key action details absent from the body itself.	2 / 3
Workflow Clarity	Four numbered steps form a clear sequence with an explicit validation checkpoint in step 3 (check for an existing tracker and branch with alternatives); the operation is non-destructive so the missing error-recovery loop does not cap the score.	3 / 3
Progressive Disclosure	A concise overview delegates substantive detail to a one-level-deep, clearly signaled reference (step 2 and the closing blockquote name the `international-expansion` skill), with content appropriately split; no nested multi-level reference chains.	3 / 3
	Total	11 / 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, specific description that states concrete capabilities, provides natural trigger phrases, and explicitly covers both what and when in third person. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions — 'gathers intake, runs EOR vs. entity framing, drafts cross-functional questions, surfaces country-specific flags, and creates a persistent tracker' — matching the 'multiple specific concrete actions' anchor rather than the partial score-2 anchor.	3 / 3
Completeness	It explicitly answers both 'what' (the five kickoff actions) and 'when' via an explicit 'Use when someone says...' trigger clause, satisfying the highest anchor.	3 / 3
Trigger Term Quality	Natural phrases a user would actually say are given explicitly — 'we're hiring in [country]', 'expansion to [country]', 'first hire in [country]' — giving good coverage of common variations rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	The international-expansion / EOR-vs-entity niche with country-specific triggers is a clear, narrow domain unlikely to fire for unrelated skills; third-person voice is used throughout with no first/second person.	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: employment-legal/skills/expansion-kickoff/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.