CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

follow-up-results

Find progress or deliverables from earlier Paperclip work and add user-requested feedback with human attribution.

Quality

73%

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 ./integrations/assistant-plugins/shared/skills/follow-up-results/SKILL.md

The canonical home for this skill is follow-up-results in paperclipai/paperclip

SKILL.md
Quality
Evals
Security

Quality

Content

81%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-built instruction-only skill: it names the exact Paperclip tools, sequences them with explicit validation and retry discipline, and stays lean without over-explaining. Remaining polish is structural — section headers, consistent spacing, and isolating host/version-sensitive availability notes — plus example tool invocations.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — every paragraph carries operational rules ('copy its exact value', 'reuse it on retries') with no padding or explanation of known concepts. Minor trim instances remain: host- and version-sensitive statements like 'ChatGPT currently supports Events in Work Cloud chats and dots' and 'This release has no replay cursor' sit in the main flow rather than an 'old patterns'/'deprecated' section, so they penalize conciseness slightly.

4 / 5

Actionability

Concrete, executable guidance throughout: exact tool names ('paperclip_connection', 'paperclip_search_tasks', 'paperclip_read_task', 'paperclip_list_deliverables', 'paperclip_read_document', 'paperclip_add_comment'), exact event types ('paperclip.task.status_changed', 'paperclip.task.comment_created', 'paperclip.task.document_updated'), and precise rules ('Use one UUID requestId per intended comment and reuse it on retries'). Minor gaps: no example invocations showing arguments or payloads for the tools, leaving a few specifics to be discovered.

4 / 5

Workflow Clarity

The sequence (connect -> locate task -> inspect deliverables -> summarize -> comment -> optionally monitor) is coherent with explicit validation checkpoints ('Wait for paperclip_connection to return before calling tools that need companyId', 'If search leaves multiple plausible matches, ask which task they mean before writing', 'Read current task state and deliverables before reporting') and explicit error-recovery feedback loops (requestId reuse on retries, 'after a gap, recover with task/history and document tools'). Not the level below (4) because validation is not merely present but explicit and paired with recovery paths for every risky write.

5 / 5

Progressive Disclosure

At ~19 lines with no bundle files, all content appropriately lives inline in SKILL.md and there are no buried or nested references, fitting the under-50-line exception. Minor organization gaps keep it below 5: no section headers to signpost the paragraphs (connection, task lookup, summarizing, commenting, monitoring), and a stray doubled blank line (lines 15-16) creates a small formatting inconsistency.

4 / 5

Total

17

/

20

Passed

Description

53%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.

The description communicates a clear niche (follow-up on earlier Paperclip work plus attributed feedback) with a concrete what, and its distinctiveness is helped by the Paperclip brand term. Its main weakness is the missing explicit 'when to use' trigger clause, which also leaves natural trigger phrases ('status', 'check on results', 'comment') uncovered.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about the status, progress, or results of earlier Paperclip work, or wants to add a comment/feedback to a Paperclip task.'

Include natural trigger synonyms users would actually say — 'status', 'check on', 'results', 'comment' — so the skill surfaces for phrasings beyond 'progress' and 'deliverables'.

List a few more concrete actions from the body (inspect deliverables, verify completion vs. creation, monitor task events) to raise specificity and distinguish the skill from generic task-status skills.

DimensionReasoningScore

Specificity

The description names the domain ('earlier Paperclip work') and two actions ('Find progress or deliverables', 'add user-requested feedback with human attribution') but is not comprehensive — inspection, verification, and monitoring actions from the body are absent. This matches anchor 3 (domain plus 1-2 concrete actions); it is not 4 because 'find' and 'add feedback' are broad strokes rather than the several specific actions the level-4 example lists.

3 / 5

Completeness

The 'what' is clear (find progress/deliverables and add feedback), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'from earlier Paperclip work' only weakly implies the when, which caps completeness at 3 per the judging guidelines. Not 4 because the when-condition cannot be considered explicit or specific.

3 / 5

Trigger Term Quality

Some natural keywords users would say are present ('progress', 'deliverables', 'feedback'), but common variations and synonyms are missing — 'status', 'check on', 'comment', 'results', 'follow up'. Not 2 because the existing terms are genuinely natural rather than generic; not 4 because the coverage of natural phrasings has visible holes.

3 / 5

Distinctiveness Conflict Risk

'Paperclip' carves a clear niche, so false triggering against unrelated skills is unlikely, and 'with human attribution' further signals the specific persona-comment workflow. Not 5 because the generic verbs ('find progress or deliverables', 'add feedback') leave minor overlap risk with closely related task-management or status-reporting skills; not 3 because the Paperclip qualifier makes it more distinct than 'somewhat specific'.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

paperclipai/paperclip

Path

integrations/assistant-plugins/shared/skills/follow-up-results/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.