CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-composition-analysis

This skill should be used when the user asks to "plan team structure", "determine hiring needs", "design org chart", "calculate compensation", "plan equity allocation", or requests organizational design and headcount planning for a startup.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/team-composition-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A data-rich, highly actionable reference for startup team planning whose main problems are structural: it front-loads ~250 lines of benchmark detail that belongs in bundle files, points to reference directories that do not exist, includes boilerplate filler sections, and lacks any validation checkpoints in its workflow. The domain content itself is specific and immediately usable.

Suggestions

Create the referenced `references/` (and `examples/`) directories with the detailed compensation and equity benchmark tables, and reduce SKILL.md to an overview with clearly signaled one-level-deep links — currently the closing pointer is a dangling reference.

Remove the circular 'Use this skill when / Do not use this skill when' sections and the generic 'Instructions' section, which restate the skill's name without adding information.

Add explicit validation checkpoints to the Quick Start workflow, e.g., 'verify total comp budget stays within 70-100% of revenue for Series A' and 'confirm option pool remains 10-15% after planned allocations'.

DimensionReasoningScore

Conciseness

The bulk is dense, high-value data Claude does not reliably know (2024 salary ranges, equity percentages, org charts) with almost no conceptual padding, but there are trimmable spots: the circular 'Use this skill when / Do not use this skill when' sections, the generic 'Instructions' section ('Clarify goals, constraints, and required inputs'), and the 'Rule of Thumb' line duplicating the fully-loaded cost formula. This fits anchor 4 (efficient, minor instances that could be trimmed) rather than 5; it is well above anchor 3's 'noticeably unnecessary explanation'.

4 / 5

Actionability

As an instruction-only skill, the guidance is fully concrete and specific: exact dollar ranges per role and level, a worked dilution example ('$15M post-money; 15% pool = $2.25M'), a headcount budget formula with a worked '$1.1M' example, ASCII org charts, and hiring timelines with buffer rules. Specific examples cover the common cases (stage-based planning, comp, equity, budget), matching anchor 5; anchor 4's 'minor gaps' does not apply — a practitioner could execute directly from this.

5 / 5

Workflow Clarity

The 'Quick Start' gives a clear 8-step sequence (identify stage → define roles → prioritize → set comp → plan timeline → calculate budget → design org chart → allocate equity), but there are no validation checkpoints anywhere — the only nod is the generic 'Apply relevant best practices and validate outcomes'. The 'Compensation as % of Revenue' section could serve as a budget sanity check but is never framed as one. This matches anchor 3 ('steps listed but validation gaps; checkpoints missing or implicit') and not anchor 4, which requires most checkpoints present; the operations are advisory, not destructive/batch, so no cap applies.

3 / 5

Progressive Disclosure

Section structure is clear, but roughly 250 lines of benchmark tables (salary ranges, equity ranges, org charts) are inlined in SKILL.md when the rubric expects the file to be an overview pointing to detailed materials — and the closing pointer 'see references/ and examples/' references directories that do not exist in the bundle, so the disclosure path is broken. This matches anchor 3 ('content that should be separate is inline; references present but not clearly signaled') better than anchor 2, whose 'minimal structure' does not hold, and better than anchor 4, which requires references that actually resolve.

3 / 5

Total

15

/

20

Passed

Description

78%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.

A well-constructed trigger-focused description with natural, quotable phrases and clear startup scoping. Its main weakness is that the 'what' — the skill's actual capabilities — is only embedded in trigger phrases rather than stated directly, and a few common synonyms (staffing, salary benchmarking) are missing.

Suggestions

Lead with a direct capability statement (e.g., 'Designs team structures, hiring plans, compensation, and equity allocation for early-stage startups') before the 'Use when' triggers so the 'what' is explicit, not inferred.

Add common user phrasings such as 'staffing plan', 'salary benchmarking', 'equity split', or 'how many engineers do I need' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'plan team structure', 'design org chart', 'calculate compensation', 'plan equity allocation', 'determine hiring needs' — but they appear only inside quoted trigger phrases rather than as stated capabilities, leaving minor gaps in coverage (e.g., no mention of benchmarking or budget output). This matches anchor 4 ('lists several specific actions; minor gaps') better than anchor 5, which expects a standalone comprehensive statement of what the skill does.

4 / 5

Completeness

The 'when' is explicit and strong ('This skill should be used when the user asks to...'), but the 'what' is never stated as a capability — it is only implied through the quoted trigger actions, with no clause like 'Designs team structures and compensation plans for startups'. This sits between anchor 4 (both present, one could be more explicit) and anchor 5 (which requires both clearly and explicitly answered); the missing standalone what-clause keeps it at 4.

4 / 5

Trigger Term Quality

Quoted phrases like 'plan team structure', 'design org chart', 'calculate compensation', and 'plan equity allocation' are natural things a user would say, plus domain terms 'organizational design and headcount planning'. Common variations are missing ('staffing plan', 'salary benchmarking', 'equity split', 'hiring roadmap'), so it fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Startup-specific scoping ('for a startup') combined with distinct triggers like 'plan equity allocation' and 'design org chart' carves a clear niche with minimal overlap risk against generic HR or business skills. This clearly matches anchor 5 rather than anchor 4, whose 'minor overlap risk with closely related skills' would require ambiguity this description does not have.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/team-composition-analysis/SKILL.md

Reviewed

Table of Contents

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.