CtrlK
BlogDocsLog inGet started
Tessl Logo

004-commands-installation

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-organized instruction-only skill body with good progressive disclosure via a single real reference. It loses points on actionability and workflow clarity because the copy mechanics and a post-install verification checkpoint are not present in the SKILL.md itself.

Suggestions

Add a brief explicit copy mechanism or example (e.g., the concrete copy command or XInclude resolution step) so the core action is executable directly from SKILL.md without relying solely on the reference.

Add an explicit post-install verification step such as listing the installed files and confirming overwrites/non-overwrites, giving the batch operation a validation checkpoint.

Reorder the MUST constraints into an explicit numbered workflow (ask destination -> create dir -> copy files -> report overwrites -> verify) to make the sequence and checkpoint unmistakable.

DimensionReasoningScore

Conciseness

The body is lean: terse 'What is covered' bullets and four crisp MUST constraints with no padding and no explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

The MUSTs are concrete (choose one of four destinations, copy files from the reference, preserve names and report overwrites, create the dir if missing), but the actual copy mechanism and XInclude resolution are deferred to the reference rather than fully specified inline.

2 / 3

Workflow Clarity

A sequence is present (choose destination, copy, report overwrites, create dir if missing), but this batch file-write operation lacks an explicit verification/reporting checkpoint, capping it at 2 per the batch-operations guideline.

2 / 3

Progressive Disclosure

A clean, well-organized overview under 50 lines with a single clearly signaled one-level-deep reference to references/004-commands-installation.md (a real, verified file), giving easy navigation.

3 / 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.

A strong, well-structured description that clearly states capabilities, lists natural trigger phrases, and scopes itself to a distinct niche with no voice or over-claim issues. It answers both 'what' and 'when' explicitly.

DimensionReasoningScore

Specificity

Names concrete actions ('selecting the destination interactively and copying the embedded command definitions from project assets') and enumerates four specific destination directories, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does (install embedded command definitions from project assets) and when to use it via an explicit 'Use when...' clause plus a 'This should trigger for requests such as...' list, answering both what and when.

3 / 3

Trigger Term Quality

Provides realistic user phrasings ('Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite'), giving good natural-term coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (installing embedded project commands into four named framework dirs, 'Part of Plinth Toolkit') with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
jabrena/plinth
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.