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.

70

Quality

86%

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable instruction skill with excellent progressive disclosure and concrete examples. Its main weaknesses are occasional conceptual padding and the absence of an explicit validation/verification checkpoint before the generated package is finalized.

Suggestions

Add a verification checkpoint in Step 7 (e.g. re-read the spec and confirm COMPANY.md/AGENTS.md fields, slugs, and reportsTo structure conform) before summarizing, since package generation is a batch operation.

Tighten the 'Workflow' and 'Writing workflow-aware agent instructions' sections by trimming the conceptual rationale ('A company is not just a list of agents...') to the actionable rules only.

Consider moving the detailed .paperclip.yaml adapter/env rules into a reference file to keep the main body leaner, since they are secondary to the core company-generation flow.

DimensionReasoningScore

Conciseness

Mostly efficient and skill-specific, but padded in places — e.g. 'A company is not just a list of agents with skills. It's an organization that takes ideas and turns them into work products' and the closing rationale in 'Writing workflow-aware agent instructions' explain concepts Claude can infer, so it could be tightened.

2 / 3

Actionability

Provides fully concrete, copy-paste-ready guidance: an exact directory tree, hard rules (URL-safe lowercase hyphenated slugs, reportsTo conventions), executable YAML examples for .paperclip.yaml and sources, and a specific command `git ls-remote https://github.com/owner/repo HEAD`.

3 / 3

Workflow Clarity

Steps 1-7 are clearly sequenced with an interview alignment gate, but generating an entire package is a batch operation with no explicit verification that the output conforms to the spec before summarizing, which caps workflow clarity at 2 per the batch-operation guideline.

2 / 3

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references to from-repo-guide.md, companies-spec.md, and example-company.md, all of which exist in references/ — content is appropriately split and easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

100%

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 states concrete capabilities and provides an explicit 'Use when...' trigger with natural user phrasings. It is concise, complete, and clearly distinct from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create agent company packages', 'scaffold an agent team, hire agents, or turn a repo/skills collection into a company package' — matching the top anchor for specific concrete actions.

3 / 3

Completeness

Clearly answers both what (create agent company packages conforming to agentcompanies/v1) and when via an explicit 'Use when...' trigger, satisfying the top anchor.

3 / 3

Trigger Term Quality

The 'Use when asked to create a company, scaffold an agent team, hire agents, or turn a repo/skills collection into a company package' clause covers natural phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Tied to a clear niche (agent companies / agentcompanies/v1) with distinct triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

12

/

12

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.