CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

first-task

Guide the user's first Paperclip task when its description invokes /first-task. Interpret the opening answer, clarify their goal, propose a plan or a single task, and wait for approval before hiring agents or executing approved work.

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

70%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-sequenced, highly actionable onboarding workflow with explicit validation checkpoints and error-recovery loops. Its main weaknesses are repetitive restatement of approval-boundary rules and a monolithic single-file structure that inlines detailed API payloads that could be split out.

Suggestions

Consolidate the approval-boundary rules into a single statement (e.g. one 'Acceptance and authorization' note) instead of restating them in steps 1, 2, 3, and 4, trimming the resolverPolicy and idempotency paragraphs to the essential rule plus one example.

Move the two JSON payload examples and the native-tool argument-placement details (root fields vs payload fields, resolverPolicy rules) into a references/ file (e.g. references/native-cards.md), keeping SKILL.md as the workflow overview with clearly signaled one-level-deep links.

Add per-step markdown headers (e.g. '## 1. Take the user's path', '## 2. Propose and wait') so the long body is scannable without reading every bullet, and include a concrete paperclip_block argument example alongside the createTask/setDependencies ones.

DimensionReasoningScore

Conciseness

The body is dense and free of known-concept explanations, but the approval-boundary rule is restated across steps 1-4 and the resolverPolicy/idempotency paragraphs repeat the same cautions in several forms, so it could be noticeably tightened.

3 / 5

Actionability

Concrete tool names (request_human_input with interactionKind/continuationPolicy, create_task, set_dependencies, paperclip_block, the resolve-from-comment endpoint) and two near-copy-paste JSON payloads with explicit placeholder-replacement rules make the guidance mostly executable, though a few steps (e.g. paperclip_block, verifying a 'successful saved card receipt') lack a concrete payload or example.

4 / 5

Workflow Clarity

'Work in this order' provides a numbered 4-step sequence with branch handling, explicit validation checkpoints ('Wait for a successful saved card receipt', 'Wait for the saved accepted/rejected result'), and error-recovery feedback loops ('Retry an interrupted write using the same message and decision; inspect a conflicting result instead of proceeding').

5 / 5

Progressive Disclosure

No bundle files exist and the 135-line body carries only one heading, with roughly 60 lines of native-tool API mechanics and JSON payload examples inlined that could live in a references file; the numbered steps give some structure, but organization could be improved with per-step headers or split-out references.

3 / 5

Total

15

/

20

Passed

Description

87%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: concrete actions, an explicit command-based trigger, and both what-and-when answered clearly. Its only shortcoming is limited natural-term variation beyond the /first-task command itself and a couple of uncovered edge paths.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Interpret the opening answer, clarify their goal, propose a plan or a single task, and wait for approval before hiring agents or executing approved work') with only minor gaps such as rejection handling and child-task handoff, fitting the 'several specific actions; minor gaps' anchor rather than the fully comprehensive anchor above it.

4 / 5

Completeness

It clearly answers both 'what' (interpret, clarify, propose, wait for approval, hire, execute) and 'when' ('when its description invokes /first-task') with a concrete trigger phrase, matching the top anchor rather than the 'when could be more explicit' anchor below it.

5 / 5

Trigger Term Quality

The trigger 'when its description invokes /first-task' is explicit and natural (a user would say '/first-task' or 'first task'), but coverage stops there — no synonyms like 'onboarding' or 'getting started' — so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'first Paperclip task' plus the /first-task command invocation defines a clear niche with a distinct trigger, so the risk of firing for an unrelated skill is minimal.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

paperclipai/paperclip

Path

server/src/onboarding-assets/first-task/skills/first-task/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.