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

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/004-commands-installation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 lean, well-structured overview that uses progressive disclosure effectively, pointing to a real reference for executable detail. Main gaps are redundant 'when to use' content, no in-body validation checkpoint for a batch file-overwrite operation, and actionability deferred to the reference.

Suggestions

Remove or trim the 'When to use this skill' section since it duplicates the frontmatter description's trigger phrases.

Add an explicit validation/verification step to the body (e.g., list the destination directory after copy and confirm all 13 commands are present) so the batch overwrite workflow clears the workflow_clarity cap.

Either inline the list of 13 command files or a concrete copy command in the body, or make the reference link more explicit about containing the executable step-by-step procedure.

DimensionReasoningScore

Conciseness

The body is short and well-organized, but the 'When to use this skill' section duplicates the frontmatter trigger phrases verbatim and 'What is covered in this Skill?' overlaps the Constraints section, so it could be tightened.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable (copy all files from assets/commands/ into one of four named destinations, preserve names, create the dir, report overwrites); the minor gap is that the file enumeration lives in the reference rather than the body.

4 / 5

Workflow Clarity

The ask-then-copy-then-report sequence is implied, but this is a batch/overwrite operation with no explicit validation or verification checkpoint in the body, so workflow clarity is capped at 3 per the rubric.

3 / 5

Progressive Disclosure

A concise overview pointing to a single one-level-deep reference (references/004-commands-installation.md, verified to exist) which in turn links the 13 real assets/commands files; navigation is clear and content is appropriately split.

5 / 5

Total

15

/

20

Passed

Description

90%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, specific description that clearly states both capability and trigger conditions with good synonym coverage. The only weakness is second-person voice ('you need to') which the rubric penalizes on specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions (install, select destination interactively, copy embedded command definitions), but the second-person phrasing 'Use when you need to install' triggers the rubric's -1 specificity penalty, pulling a base-4 down to 3.

3 / 5

Completeness

Both 'what' (install/copy embedded command definitions into command directories, selecting interactively) and 'when' (Use when... plus concrete trigger phrases) are explicitly and clearly answered.

5 / 5

Trigger Term Quality

The explicit 'This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite' covers multiple natural synonyms and path extensions.

5 / 5

Distinctiveness Conflict Risk

A clear niche (installing the Plinth Toolkit embedded command suite into one of four named framework command directories) with distinct triggers and minimal overlap risk.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.