CtrlK
BlogDocsLog inGet started
Tessl Logo

paperclip-board

Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.

68

Quality

82%

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

65%

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

Strong actionability with concrete executable commands, but the skill is a monolithic wall of text with redundant endpoint listings and missing explicit validation feedback loops on approval/destructive operations.

Suggestions

Split the Key Endpoints Reference table and presentation-format examples into a bundled reference file (e.g. references/endpoints.md) and point to it, removing the inline duplication.

Add explicit validate-then-retry feedback loops for approval and config-revision operations (e.g. re-fetch after PATCH and confirm the change took effect).

Tighten redundant curl blocks that duplicate the endpoint reference table, keeping only one canonical form per endpoint.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete curl/JSON, but the ~600-line body repeats endpoints inline AND in a full reference table, and presentation-format blocks add length that could be tightened.

2 / 3

Actionability

Provides fully executable curl commands with complete JSON bodies, specific presentation templates, and a copy-paste endpoint reference table.

3 / 3

Workflow Clarity

Onboarding and startup flows are well sequenced with a write-path freshness rule, but approval/destructive operations lack explicit validate-then-retry feedback loops, capping at 2 per the batch/destructive guidance.

2 / 3

Progressive Disclosure

A single monolithic SKILL.md with no references/scripts/assets bundle and no 'see X.md' pointers; the inline endpoint reference and presentation examples could be split into separate files.

2 / 3

Total

9

/

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.

The description is concise, third-person, specific, and pairs a clear capability statement with an explicit 'Use when' trigger, hitting every anchor at the top level.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review' — rather than vague language.

3 / 3

Completeness

Explicitly states both what ('Manage a Paperclip company as a board member via chat') and when (a 'Use when...' trigger clause), satisfying both halves.

3 / 3

Trigger Term Quality

The 'Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight' clause gives broad, natural phrasing a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The narrow 'Paperclip control plane' / 'board member' framing creates a clear niche unlikely to trigger for unrelated skills.

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

skill_md_line_count

SKILL.md is long (620 lines); consider splitting into references/ and linking

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.