CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-installer

Install, update, trust, or inspect Codewhale skills from GitHub or local skill folders. Use when the user asks for available skills or wants a community skill installed.

Quality

84%

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

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.

A tight, well-structured instruction skill with concrete commands and a sensible security guardrail around community skills. Its one real defect is the truncated final workflow step, which cuts off mid-sentence and leaves the name-conflict guidance incomplete; the trust-review step also lacks specifics on what to inspect.

Suggestions

Complete the truncated step 5 — the sentence ends at "take precedence over global `~/.codewhale/skills`, with" and never states the resolution.

Specify what to look for when reviewing a community SKILL.md before trusting it (e.g., prompt-injection in instructions, destructive or network-capable scripts, unexpected file writes).

Add a recovery step for failed installs (e.g., re-run /skill install, check the registry name, fall back to manual clone into ~/.codewhale/skills).

DimensionReasoningScore

Conciseness

The body is ~30 lean lines: a command list, a 5-step workflow, and a one-line security guardrail. It assumes Claude's competence — no explanation of what skills are, what GitHub is, or how installation works — so every token earns its place. Not below 5 because there is no padding or over-explanation anywhere (the opening sentence slightly duplicates the description but is a standard, minimal pattern).

5 / 5

Actionability

Concrete, executable commands are given ("/skill install github:<owner>/<repo>", "/skill trust <name>") and the workflow maps to them. Not 5: step 5 is truncated mid-sentence ("take precedence over global `~/.codewhale/skills`, with"), leaving an unusable instruction, and step 3 says to "inspect the SKILL.md" without stating what to look for (prompt injection, destructive scripts, network calls). Not 3: the guidance is genuinely executable apart from that one broken step.

4 / 5

Workflow Clarity

The 5-step workflow has a clear sequence and some checkpoints: review-before-trust in step 3 and a verify-installed check in step 4 ("restart the session if the skill does not appear"). Not 5: the truncated step 5 makes the name-conflict resolution incoherent, and there is no explicit feedback loop for the install failure case (e.g., what to do when /skill install errors). Not 3: sequence and several checkpoints are clearly present, not merely implied.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references — no references/, scripts/, or assets/ bundle exists, and nothing in the body points to files that should exist. Two well-labeled sections (## Commands, ## Workflow) plus a scoped closing guardrail make navigation trivial, matching the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

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

A strong description: concrete action verbs, explicit sources, and a genuine 'Use when...' trigger clause in third person. Its main weakness is that the 'when' triggers and action list are narrower than the skill's actual scope (list, activate, scaffold, uninstall are undocumented in the description).

Suggestions

Include remove/scaffold in the action list (e.g., 'Install, update, remove, trust, or inspect Codewhale skills') so the description matches the body's command set.

Broaden the trigger clause with natural variations such as 'add a skill', 'find new skills', or 'browse the community skill registry'.

Mention both install sources in the trigger (GitHub and local skill folders) to distinguish it from pure marketplace-install skills.

DimensionReasoningScore

Specificity

"Install, update, trust, or inspect Codewhale skills from GitHub or local skill folders" names four concrete actions plus two source types, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the body also supports list/activate/scaffold/uninstall, none of which the description covers, and short of 3 because coverage clearly exceeds 1-2 actions.

4 / 5

Completeness

Both parts are explicit: the 'what' ("Install, update, trust, or inspect...") and the 'when' ("Use when the user asks for available skills or wants a community skill installed"). The 'when' clause is present but only covers two triggers — asking for available skills and community installs — so it matches the 4 anchor ('when' could be more specific) rather than the 5 anchor's concrete multi-trigger coverage.

4 / 5

Trigger Term Quality

"asks for available skills", "community skill installed", "Codewhale skills", "GitHub" are natural user phrasings with good keyword coverage. Not 5: common variations like "add a skill", "skill marketplace", or the local skills path are missing; not 3: several natural phrases are present, not just generic ones.

4 / 5

Distinctiveness Conflict Risk

The skill-management niche ("Codewhale skills", "trust", "community skill") is distinct and unlikely to fire for unrelated skills. Minor overlap risk remains with adjacent skills like a skill-scaffolding or skills-listing utility, since creation and listing appear in the body but not the description, keeping it below the 'clear niche with minimal conflict' anchor.

4 / 5

Total

16

/

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

Hmbown/Codewhale

Path

crates/tui/assets/skills/skill-installer/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.