CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-issue-interaction-ui

Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a highly actionable maintainer workflow with an explicit sequence, executable commands, invariants, a pre-merge checklist, and error-recovery guidance — near-perfect on actionability and workflow clarity. Its weaknesses are a monolithic structure with no progressive disclosure (all detail inline in one long file) and minor redundant repetition in the opening.

Suggestions

Split each stage's touch-list and invariants into one-level-deep reference files (e.g. references/shared-contract.md, references/server-service.md, references/ui-card.md) and keep SKILL.md as the order-of-operations overview with links.

Delete the duplicated "Do NOT install this on production Paperclip agents" line and the repeated audience statement — state the developer/maintainer scope once.

Move the verbatim checkbox-PR file inventory into a reference (or rely solely on the `git show --stat 4d5322c82` pointer) so the canonical example stays stable as the repo drifts.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, repo-specific facts (file paths, litigated invariants, exact idempotency key shape) and assumes competence, but there is redundant padding: "Do NOT install this on production Paperclip agents" appears verbatim at both the top and line 19, and the audience is restated three times in the opening. This is 'efficient with minor instances that could be trimmed' (level 4) rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

Guidance is fully executable: exact files to touch per layer (e.g. "server/src/services/issue-thread-interactions.ts — mapInteractionRow (the switch (row.kind)...)"), copy-paste commands ("git show --stat 4d5322c82", the complete NODE_ENV=test vitest invocation listing every test file), concrete schemas ("<kind>:<issueId>:<decisionKey>:<revisionId>"), and a worked canonical PR to model after. Matches the copy-paste-ready level-5 anchor.

5 / 5

Workflow Clarity

The order of operations is explicitly sequenced with rationale ("Do the shared contract first. It is the smallest correct change you can land"), stages 1→2→3→3a→4→5 each carry per-layer invariants, and there are real validation checkpoints with a feedback loop: a "Tests to run before requesting review" command block, a pre-merge checklist, and error recovery ("If UI vitest fails with `act is not a function`... Re-run with NODE_ENV=test"). Matches the explicit-validation-with-recovery anchor at level 5.

5 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/), so the ~290-line SKILL.md inlines everything: per-layer file inventories, server/UI invariants, and channel guidance that would naturally live in one-level-deep reference files. The few external pointers (the connector playbook link, the PAP-10415 plan, the checkbox PR) are clearly signaled, but the bulk of detailed content that should be separate is inline, matching the level-3 anchor rather than level 4's 'most content appropriately placed'.

3 / 5

Total

17

/

20

Passed

Description

73%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 well-targeted with an explicit 'Use when' clause and concrete kind-name triggers, giving it strong distinctiveness and good trigger quality. Its main weakness is that the capability statement is a single action padded with "end-to-end" rather than naming the concrete layers the skill actually covers.

Suggestions

Replace "end-to-end" with the concrete stages, e.g. "Add a new Paperclip issue-thread interaction kind end-to-end — shared contract, server service, UI card, channel connectors, and CLI/MCP/plugin helpers."

Broaden the trigger list to cover the remaining kinds and the generic phrase, e.g. add "request_item_verdicts, connection_intent, or interaction kinds".

State the audience in the description ("for contributors changing Paperclip itself") so it cannot be confused with agent-facing interaction skills.

DimensionReasoningScore

Specificity

"Add a new Paperclip issue-thread interaction kind end-to-end" names the domain and one concrete action, but the enumerated items ("request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks") are example objects of that one action rather than a list of several distinct actions. This matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor, not the level-4 anchor that requires several specific actions.

3 / 5

Completeness

Both halves are present: the what ("Add a new Paperclip issue-thread interaction kind end-to-end") and an explicit when clause with concrete triggers. However the 'what' leans on the vague qualifier "end-to-end" without naming the layers involved (shared contract, server, UI, docs), fitting level 4 ('when' explicit, 'what' could be more specific) rather than level 5 where both are fully concrete.

4 / 5

Trigger Term Quality

"Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks" includes the exact kind identifiers a contributor would naturally mention. A few natural terms are missing (e.g. "interaction kind" itself, request_item_verdicts, connection_intent), so it stops short of the comprehensive-synonym coverage of level 5 but clearly exceeds the partial keyword coverage of level 3.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — introducing a new issue-thread interaction kind in the Paperclip repo — and the named kinds ("request_confirmation", "ask_user_questions", "suggest_tasks") are distinct triggers that no other skill would claim. Minimal conflict risk, matching the clear-niche anchor at level 5.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

paperclipai/paperclip

Path

.agents/skills/create-issue-interaction-ui/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.