CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-creator

Create, update, or review Picoclaw skills. Use when writing a new skill, modifying an existing SKILL.md, turning a repeated workflow into a reusable skill, or organizing scripts, references, and assets for a skill.

71

Quality

88%

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%

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 well-structured, actionable guide with a clear sequenced workflow and verification/iteration checkpoints. Its main weaknesses are conceptual padding that assumes too little of Claude and a monolithic structure with detailed example material that is not split into reference files despite approaching the skill's own 500-line guidance.

Suggestions

Trim the 'About Skills' and 'What Skills Provide' conceptual sections to the non-obvious Picoclaw-specific conventions only, removing explanations of what skills are that Claude already knows.

Move the multi-pattern 'Progressive Disclosure Patterns' examples (the large PDF/BigQuery/cloud-deploy/DOCX code blocks) into a references file and link to it from SKILL.md, practicing the progressive disclosure the skill teaches.

Deduplicate progressive-disclosure guidance, which currently appears in both 'Progressive Disclosure Design Principle' and the 'references/' best-practice notes, to tighten the body.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes conceptual padding Claude already knows ('Skills are modular, self-contained packages that extend the agent's capabilities... Think of them as onboarding guides') and repeats progressive-disclosure ideas across sections, so it could be tightened. It is not score-1 verbose, but several paragraphs do not clearly earn their token cost.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: an executable bash snippet for creating the skill directory, exact naming rules, a file-structure diagram, worked examples (rotate_pdf.py, schema.md), and a verification checklist — actionable for an instruction-only skill.

3 / 3

Workflow Clarity

A clearly sequenced 6-step creation process with an explicit Step 5 verification checklist ('Confirm all referenced files actually exist', 'Test any scripts') and a Step 6 iterate feedback loop (use -> notice struggles -> update -> retest) matches the anchor for clear sequence with validation and feedback loops.

3 / 3

Progressive Disclosure

The skill is a well-organized but monolithic 355-line SKILL.md with no bundle files; the detailed 'Progressive Disclosure Patterns' section (~80 lines of large example code blocks) is inline content that could live in a reference file. Organization and navigation are clear, but content is not actually split across files, so it sits below the top anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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, concrete, and complete: it names specific actions, provides explicit 'Use when' triggers in natural language, and occupies a clear niche unlikely to conflict with other skills. It matches the strongest rubric anchors across all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create, update, or review Picoclaw skills' plus 'writing a new skill, modifying an existing SKILL.md, turning a repeated workflow into a reusable skill, or organizing scripts, references, and assets' — matching the anchor for several specific concrete actions.

3 / 3

Completeness

Explicitly states what it does ('Create, update, or review Picoclaw skills') and when to use it via an explicit 'Use when ...' clause enumerating triggers, satisfying both what and when.

3 / 3

Trigger Term Quality

Natural phrasings a user would actually say ('writing a new skill', 'modifying an existing SKILL.md', 'turning a repeated workflow into a reusable skill', 'organizing scripts, references, and assets') give good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The 'Picoclaw skills' niche with skill-authoring triggers is clearly distinct from domain-specific skills and unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

14

/

16

Passed

Repository
sipeed/picoclaw
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.