CtrlK
BlogDocsLog inGet started
Tessl Logo

status-card-query

Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.

59

Quality

68%

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 ./packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, highly actionable reference with copy-paste curl/JSON examples and an explicitly sequenced write-back workflow plus validation guards. Main gap is the absence of an explicit retry loop for failed write-backs.

DimensionReasoningScore

Conciseness

Lean prose that assumes Claude's competence and supplies tight executable curl/JSON without explaining what APIs are; a 5 is withheld only for minor over-explanation such as the 'union semantics' aside.

4 / 5

Actionability

Fully copy-paste-ready curl commands with real endpoints, auth headers, and complete JSON payloads, plus explicit field-by-field CompanySearchQuery semantics covering the common cases.

5 / 5

Workflow Clarity

Both modes are clearly sequenced and the write-back path is explicit ('First write the compiled query... Then... Send it to PUT'), with validation guards (201 check, 'report the ambiguity instead of inventing ids', run-scoped credential checks); not a 5 because there is no explicit retry/feedback loop if a write fails.

4 / 5

Progressive Disclosure

A compact single-file skill (no bundle files present) with clear, well-organized section headers and one-level inline content, which the simple-skill guidance allows to score 5.

5 / 5

Total

18

/

20

Passed

Description

51%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 specific and well-scoped to a niche domain, but it omits any explicit 'when to use' trigger guidance and leans on internal jargon rather than natural user language. Adding a 'Use when...' clause with everyday trigger terms would lift completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause naming the situations that call for this skill (e.g. authoring a Paperclip status card or being assigned a Summarizer compilation run).

Replace some internal jargon with natural user-facing trigger phrases (e.g. 'status report', 'search query for company issues') so users would actually say the terms.

Briefly separate the two modes so the reader sees distinct trigger conditions for agent authoring vs. summarizer compilation.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Create and maintain agent-authored Paperclip status cards', 'compile a prose interest prompt into bounded CompanySearchQuery objects', and 'write the first summary' — with only minor abstraction in 'maintain'; not a 5 because coverage is split across two modes without enumerating the sub-actions of each.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger guidance, which the rubric caps at 3; it is not a 4 because 'when' is entirely absent rather than weakly present.

3 / 5

Trigger Term Quality

Relies on technical jargon ('Paperclip', 'CompanySearchQuery', 'Summarizer run', 'agent-authored') with no natural phrases a user would actually say; missing the everyday synonyms a 3 would provide.

2 / 5

Distinctiveness Conflict Risk

Occupies a clear Paperclip-specific niche ('status cards', 'Summarizer generation run') with minimal overlap risk; not a 5 only because the dual-mode phrasing could let it loosely compete with a pure search-query skill.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.