CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, work product review, or help finding things in the Paperclip web UI.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/paperclip-board/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable, command-first skill body with clearly sequenced workflows and explicit approval/freshness checkpoints. Its main weaknesses are a monolithic single-file structure with no progressive disclosure, duplicated endpoint material, and a broken internal cross-reference.

Suggestions

Move the 'Key Endpoints Reference' table into a references/endpoints.md file and keep a one-line pointer in SKILL.md — it duplicates the inline curl examples and costs roughly 35 lines of tokens on every load.

Split the detailed onboarding steps, agent-hire JSON payloads, and the web-UI quick-search guide into references/ files so SKILL.md stays an overview with well-signaled one-level-deep links.

Fix the broken cross-reference to 'the Agent System Prompt Template (Section D below)' — no lettered sections exist — and consolidate the duplicated presentation-format examples under 'Presentation Rules'.

DimensionReasoningScore

Conciseness

The body is command-dense and product-specific with no generic concept explanations, but the 35-row "Key Endpoints Reference" table duplicates nearly every curl example already shown inline, and presentation formats appear both inside sections and again under "Presentation Rules" — fits anchor 3's 'mostly efficient but could be tightened', above anchor 2 since nothing pads concepts Claude already knows.

3 / 5

Actionability

Nearly every operation ships a copy-paste-ready `curl -sS` command with a complete JSON body (e.g., the agent-hire POST with full `adapterConfig`, `runtimeConfig`, and `permissions`), but a few PATCH bodies are placeholders ("{ ... updated config with new Collaboration section ... }") and the reference to "the Agent System Prompt Template (Section D below)" points to a lettered section that does not exist — anchor 4's concrete commands with minor gaps, short of anchor 5.

4 / 5

Workflow Clarity

Session Startup, Onboarding, and the Escalation Path Updates are clearly numbered with explicit checkpoints ("Only after board approval, update each affected agent", "Always re-read a document or config from the API before modifying it", auto-approve gate for the CEO hire), but there are no error-recovery feedback loops for failed API calls beyond the 401/403 rule — anchor 4's clear sequence with minor validation gaps, short of anchor 5's full feedback loops.

4 / 5

Progressive Disclosure

Section headers make the ~630-line body navigable, but there are no bundle/reference files at all: the Key Endpoints Reference table, detailed hire payloads, and web-UI search guide that belong in one-level-deep references are fully inlined in SKILL.md — anchor 3's 'content that should be separate is inline'; not anchor 4, which requires most content appropriately split across files.

3 / 5

Total

14

/

20

Passed

Description

83%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 description that explicitly answers both 'what' and 'when' with a well-scoped trigger list anchored to a named product. It would benefit from more operation-level action verbs and natural synonyms like "hiring", "budget", and "spend".

DimensionReasoningScore

Specificity

"Manage a Paperclip company as a board member via chat" plus "onboarding, company or agent management, approvals, task monitoring, cost oversight, work product review" lists several concrete functional areas, but terms like "company or agent management" remain area-level rather than operation-level, leaving minor coverage gaps — matches anchor 4, short of anchor 5's fully concrete action list.

4 / 5

Completeness

"Manage a Paperclip company as a board member via chat" clearly answers 'what', and "Use when the user wants onboarding, ... approvals, task monitoring, cost oversight, work product review, or help finding things in the Paperclip web UI" explicitly answers 'when' with concrete trigger phrases — matches anchor 5; anchor 4's caveat that 'when' could be more explicit does not apply here.

5 / 5

Trigger Term Quality

"onboarding", "approvals", "task monitoring", "cost oversight", and "help finding things in the Paperclip web UI" are phrases a user would naturally say, but common variations like "hiring", "budget", and "spend" are absent — anchor 4's good coverage with a few natural terms missing, above anchor 3's partial coverage, below anchor 5's synonym completeness.

4 / 5

Distinctiveness Conflict Risk

"Paperclip" and "Paperclip web UI" pin the skill to a clear niche with distinct triggers, but generic terms like "approvals" and "task monitoring" could still fire for general project-management skills — anchor 4's minor overlap risk, short of anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

paperclipai/paperclip

Path

skills/paperclip-board/SKILL.md

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.