CtrlK
BlogDocsLog inGet started
Tessl Logo

company-creator

Create agent company packages that conform to agentcompanies/v1. Use when asked to create a company, scaffold an agent team, hire agents, or turn a repo/skills collection into a company package.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 well-structured, highly actionable skill body with concrete rules and executable examples, weakened mainly by a missing output-validation step in a batch file-generation workflow and some trimmable explanatory prose. Progressive disclosure is good with real, well-linked references.

Suggestions

Add an explicit validation step after Step 7 (e.g., re-check the generated package against the spec conventions / required schema fields) to satisfy the batch-operation validation requirement and lift workflow_clarity above 3.

Trim the rationale prose in the 'Workflow' and 'Writing workflow-aware agent instructions' sections to the bare guidance, removing sentences like 'This turns a collection of agents into an organization that actually works together.'.

Consider moving the .paperclip.yaml adapter type list and external-skill yaml reference into a dedicated reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but contains philosophical prose such as 'A company is not just a list of agents with skills…' and 'This turns a collection of agents into an organization that actually works together…' that could be trimmed without losing guidance value.

4 / 5

Actionability

Provides copy-paste-ready directory trees, concrete rules (URL-safe lowercase hyphenated slugs, reportsTo conventions), executable yaml examples for adapters/env inputs/external skill references, and a runnable `git ls-remote` command covering the common cases.

5 / 5

Workflow Clarity

A clear 7-step sequence exists with pre-write checkpoints (interview alignment, read-the-spec), but generating a multi-file package is a batch operation with no explicit post-generation validation/verification step, so the rubric's batch-operation cap limits this to 3.

3 / 5

Progressive Disclosure

All three bundle files (from-repo-guide.md, companies-spec.md, example-company.md) are clearly signaled with one-level-deep links, but the body itself carries dense detail (adapter type list, .paperclip.yaml and external-skill yaml blocks) that could arguably live in reference files.

4 / 5

Total

16

/

20

Passed

Description

92%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 strong, third-person description that clearly states what the skill does and when to use it, with concrete trigger phrases and a distinct niche. The only minor gap is slightly limited synonym coverage of trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create agent company packages that conform to agentcompanies/v1', 'create a company, scaffold an agent team, hire agents, or turn a repo/skills collection into a company package' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (create agent company packages conforming to agentcompanies/v1) and 'when' ('Use when asked to create a company, scaffold an agent team, hire agents…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('create a company', 'scaffold an agent team', 'hire agents', 'turn a repo/skills collection into a company package'), but offers limited synonyms or variations beyond these core verbs.

4 / 5

Distinctiveness Conflict Risk

The 'agentcompanies/v1' spec reference and agent-team/company-package triggers carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
paperclipai/paperclip
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.