CtrlK
BlogDocsLog inGet started
Tessl Logo

paperclip-create-agent

Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.

71

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a well-structured, highly actionable nine-step workflow with executable commands, an explicit validation checkpoint, and clean progressive disclosure into real reference files. It is concise without sacrificing the concrete guidance the hiring task requires.

DimensionReasoningScore

Conciseness

The body is dense and procedural, assuming Claude's competence (it never explains what curl, an agent, or governance is), and each of the nine steps and step-6 config bullets conveys a concrete requirement rather than padding.

3 / 3

Actionability

It provides fully executable curl commands against real endpoints and a complete, copy-paste-ready POST payload with a concrete CTO example, plus a specific enumerated list of config fields to populate in step 6.

3 / 3

Workflow Clarity

Nine steps are clearly sequenced, with an explicit pre-submit validation checkpoint ('walk the draft-review checklist end-to-end and fix any item that does not pass') and a governance follow-up loop for approval state in step 9.

3 / 3

Progressive Disclosure

The body is an overview that points to real, one-level-deep bundle files (templates index, baseline role guide, draft-review checklist, API reference, agents/ directory), all of which exist in ./references/, with a clear final References section for navigation.

3 / 3

Total

12

/

12

Passed

Description

75%

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, complete, and distinctive, with a clear what-and-when structure. Its main weaknesses are the second-person 'you need' trigger voice and trigger terms that favor technical jargon over natural user phrasings.

Suggestions

Rewrite the trigger clause in third person without 'you' (e.g., 'Use when creating or hiring a new Paperclip agent, inspecting adapter options, comparing agent configs, or submitting a hire request') to avoid the second-person voice penalty.

Add natural user phrasings such as 'hire an agent', 'onboard a new agent', or 'add an agent' alongside the technical terms so triggers match what users actually say.

Consider leading the trigger clause with the most common user verb ('hire' / 'create an agent') before the more technical inspection and comparison actions.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('inspect adapter configuration options', 'compare existing agent configs', 'draft a new agent prompt/config', 'submit a hire request'), which would normally be a 3, but the second-person 'Use when you need to...' trigger clause triggers the rubric's voice penalty, reducing specificity by one.

2 / 3

Completeness

It explicitly answers both what ('Create new agents in Paperclip with governance-aware hiring') and when ('Use when you need to inspect... compare... draft... and submit a hire request'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

It contains relevant keywords ('create new agents', 'hire request', 'agent configs') but leans on technical jargon ('adapter configuration options', 'governance-aware hiring') and omits common natural variants like 'hire an agent' or 'onboard a new agent'.

2 / 3

Distinctiveness Conflict Risk

'Create new agents in Paperclip' carves a clear, narrow niche tied to a specific product and governance flow, making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

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: 3 suspicious

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.