CtrlK
BlogDocsLog inGet started
Tessl Logo

team-composition-analysis

Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.

53

Quality

60%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/team-composition-analysis/SKILL.md

The canonical home for this skill is team-composition-analysis in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is information-rich and actionable with concrete benchmarks and formulas, but it is overlong and inlines material that belongs in (missing) reference files, with broken cross-references and no validation checkpoints.

Suggestions

Move the full salary/equity benchmark tables and ASCII org charts into the referenced separate files (references/compensation-benchmarks.md, references/equity-calculator.md, examples/org-chart-evolution.md) and keep only an overview plus pointers in SKILL.md.

Create the referenced files (resources/implementation-playbook.md, references/*, examples/*) or remove the dangling references so navigation is not broken.

Add explicit validation/verification steps to the Quick Start workflow (e.g., confirm budget sums, check equity pool does not exceed reserved percentage).

DimensionReasoningScore

Conciseness

The ~410-line body inlines extensive benchmark tables (salary ranges, equity percentages, org charts) that the skill itself flags as belonging in separate reference files, padding the context with material that should be offloaded.

2 / 5

Actionability

Provides concrete numbers, executable formulas (Total Comp = Base x 1.30 + Equity), a worked budget example with arithmetic, and an 8-step Quick Start, with only minor gaps in procedural tooling.

4 / 5

Workflow Clarity

The Quick Start offers a clear 8-step sequence, but there are no validation or verification checkpoints and no error-recovery feedback loops for the planning workflow.

3 / 5

Progressive Disclosure

The body references five external files (resources/implementation-playbook.md, two references/ files, two examples/ files), none of which exist, and inlines bulk reference data that should be split out, leaving references broken and structure poor.

2 / 5

Total

11

/

20

Passed

Description

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

The description is specific and distinctive, clearly conveying what the skill does, but it omits any explicit "when to use" trigger guidance, which caps its completeness score.

Suggestions

Append an explicit "Use when..." clause with natural trigger phrases (e.g., "Use when planning startup hiring, org structure, compensation, or equity allocation from pre-seed through Series A").

Add common synonyms users would say ("org chart," "headcount plan," "salaries") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names four concrete, distinct actions ("team structures, hiring plans, compensation strategies, and equity allocation") with comprehensive coverage of the startup team-building niche.

5 / 5

Completeness

Clearly states what the skill does but provides no "Use when..." trigger clause, so the "when" is absent; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural user-facing terms (team structures, hiring plans, compensation, equity, pre-seed, Series A) but omits common synonyms like "org chart," "headcount," or "salaries."

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (early-stage startup team/equity planning by funding stage) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.