CtrlK
BlogDocsLog inGet started
Tessl Logo

paperclip-dev-workspace-run-verify-fix

Run, verify, reseed, and repair Paperclip isolated dev workspace services. Use when asked to start or fix a managed project/worktree service and prove health, login readiness, cloned data, runtime visibility, and correct port ownership.

69

Quality

85%

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

77%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 content is highly actionable with executable commands, explicit validation, and strong feedback loops throughout a multi-step repair workflow. Its main weaknesses are recurring restatement of the same port-squat/reseed guidance and a monolithic single-file structure that inlines material a progressive layout would split out.

Suggestions

Consolidate the port-squat and reseed guidance into a single canonical section and have "Common failures" and "Recurring gotchas" link back to it instead of restating the procedure.

Move the detailed failure catalog (Common failures and fixes) into a reference file referenced one level deep from SKILL.md, keeping the run sequence and probes inline as the overview.

Trim restated identity-check rationale so each command appears with its justification once rather than across multiple sections.

DimensionReasoningScore

Conciseness

Nearly every line is operational and concrete, but the port-squat and reseed material recurs across "Port conflicts," "Common failures," and "Recurring gotchas," adding restatable padding that could be consolidated.

3 / 5

Actionability

Provides fully executable curl/lsof/readlink/npx commands with real env vars, expected outputs, and explicit reject conditions, covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

The numbered 10-step run sequence, the 7-step port-conflict procedure, and per-failure Symptom/Cause/Fix/Verify blocks include explicit validation checkpoints and feedback loops ("loop back to the narrowest repair step").

5 / 5

Progressive Disclosure

Section structure is clear, but the runbook is monolithic with no bundle files present and all detailed reference material inlined rather than split into one-level-deep files.

3 / 5

Total

16

/

20

Passed

Description

92%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, complete, and distinctive, clearly stating both the actions performed and the trigger conditions in third-person voice. Its only weakness is trigger-term phrasing that uses domain-internal jargon rather than the most natural user vocabulary.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Run, verify, reseed, and repair") plus concrete verification targets ("health, login readiness, cloned data, runtime visibility, and correct port ownership"), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (run/verify/reseed/repair workspace services) and when ("Use when asked to start or fix... and prove health, login readiness...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes the natural trigger "Use when asked to start or fix a managed project/worktree service," but leans on internal jargon and omits common synonyms, so it falls just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped narrowly to "Paperclip isolated dev workspace services" with distinct triggers, giving it a clear niche and minimal overlap with other skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (518 lines); consider splitting into references/ and linking

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.