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

71%

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/openai/paperclip/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

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

The body is a lean, instruction-only workflow that names exact Paperclip tools, sequences them correctly, and includes genuine validation checkpoints and error-recovery loops for ambiguous lookups and duplicate comment writes. Its main weaknesses are the absence of section headers, missing failure paths for connection/search failures, and time-sensitive host-support details that could be quarantined.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational constraints ('Wait for paperclip_connection to return before calling tools that need companyId', 'Use one UUID requestId per intended comment and reuse it on retries') and explains nothing Claude already knows. It falls slightly short of 'every token earns its place' because the host-support detail ('ChatGPT currently supports Events in Work Cloud chats and dots; ordinary Claude/Codex tool connections do not imply Events support') is time-sensitive and could be trimmed or quarantined.

4 / 5

Actionability

The guidance names exact tools and preconditions — 'Identify the connected company with paperclip_connection', 'search for it with paperclip_search_tasks', 'use paperclip_add_comment as the connected person' — which is directly executable for an MCP-driven workflow. It stays at level 4 rather than 5 because no invocation examples or argument shapes are given (e.g., how to filter paperclip_search_tasks or what fields paperclip_read_document returns).

4 / 5

Workflow Clarity

The sequence is clear and ordered (connect and wait for companyId → search by durable ID or user reference → read task/deliverables/documents → summarize → comment → optionally monitor events) with real checkpoints: 'If search leaves multiple plausible matches, ask which task they mean before writing' and 'Read current task state and deliverables before reporting', plus an error-recovery loop for comments ('inspect recent comments and do not issue the same feedback under a new ID'). It misses level 5 only for minor gaps — no failure paths for a failed paperclip_connection or a task that cannot be found, and no checklist despite covering several fragile write operations.

4 / 5

Progressive Disclosure

At roughly 19 lines with no bundle files (references/, scripts/, assets/ are all absent) and no nested references, all content appropriately lives inline in topically organized paragraphs (connection, task lookup, summarizing, comments, event monitoring). It sits at level 4 rather than 5 because there are no section headers to aid navigation, and the two event-subscription paragraphs form a distinct advanced mode that could be signaled or split out.

4 / 5

Total

16

/

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 is concise, in third person, and names a distinct niche with two concrete actions, but it lacks any explicit 'when to use' trigger clause and natural trigger synonyms users would actually say (follow up, check status, results). Adding a 'Use when...' clause with those phrases would lift both completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to follow up on, check the status of, or see results from earlier Paperclip work, or wants to add feedback to a task.'

Include natural synonyms users would say — 'follow up', 'check status', 'results', 'comment' — alongside the current 'progress' and 'deliverables' keywords.

Name one or two more concrete actions (e.g., searching tasks by title, reading deliverables) to broaden capability coverage beyond the current two.

DimensionReasoningScore

Specificity

The description names its domain ('earlier Paperclip work') and exactly two concrete actions — 'Find progress or deliverables' and 'add user-requested feedback with human attribution'. This matches the anchor for a domain plus 1-2 concrete actions that is not comprehensive (no mention of searching tasks, reading documents, or monitoring); it lists too few actions to reach the 'several specific actions' level 4 anchor.

3 / 5

Completeness

The 'what' is clear (find progress/deliverables from earlier Paperclip work and add attributed feedback), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. 'When' is only weakly implied by 'user-requested feedback', matching the 'clear what, missing or weakly implied when' anchor rather than level 4 which requires an explicit 'when'.

3 / 5

Trigger Term Quality

Relevant keywords are present ('progress', 'deliverables', 'feedback', 'Paperclip', 'earlier work'), but common natural variations users would say — 'follow up', 'check status', 'results', 'comment' — are absent despite the skill being named 'follow-up-results'. This fits 'some relevant keywords but missing common variations or synonyms' rather than level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The description carves a clear niche ('earlier Paperclip work', 'deliverables', 'feedback with human attribution') and would rarely trigger for unrelated skills, fitting 'mostly distinct; minor overlap risk'. It falls short of level 5 because triggers like 'progress', 'feedback', and 'find results' could still overlap with sibling Paperclip skills (e.g., task creation or commenting skills) without a distinguishing 'use when' phrase.

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/openai/paperclip/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.