CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-installer

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%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 concise, highly actionable body that routes the agent to real helper scripts with concrete flags and examples, and is well-structured with verified one-level-deep references. The main weakness is workflow_clarity: batch install operations lack explicit validation/retry checkpoints, which the rubric caps at 3.

Suggestions

Add an explicit validation checkpoint after install (e.g. verify the skill directory now exists and contains a SKILL.md, and report failures with a retry path) to lift workflow_clarity past the destructive/batch cap of 3.

Document the error-recovery flow when a download fails with auth errors before falling back to git sparse checkout (current state vs. next action) so the install loop has a clear feedback step.

For multi-skill installs, note a per-skill success/failure summary so batch operations surface partial failures explicitly.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence with no padding or concept over-explanation; each section (Communication, Scripts, Behavior and Options, Notes) earns its place and delivers only skill-specific facts.

5 / 5

Actionability

Provides concrete, copy-paste-ready script invocations with real flags and examples (e.g. 'scripts/install-skill-from-github.py --repo <owner>/<repo> --path <path/to/skill>', '--format json', experimental examples) covering the common cases.

5 / 5

Workflow Clarity

Decision routing (list vs install-by-name vs install-by-url) and behavior guards are present, but installation is a batch/destructive-class operation with no explicit validate→fix→retry feedback loop; the rubric caps such skills at 3 when validation checkpoints are absent.

3 / 5

Progressive Disclosure

Well-organized sections with all referenced script paths existing one level deep in scripts/ (list-skills.py, install-skill-from-github.py); a short single-purpose skill with no nested references, so structure fully satisfies navigation needs.

5 / 5

Total

18

/

20

Passed

Description

87%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, third-person description that states concrete capabilities and provides an explicit 'Use when' trigger covering listing and both curated and repo-based installation. Minor specificity gaps (no update/uninstall) keep it just short of perfect on coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Install Codex skills', 'from a curated list or a GitHub repo path', 'list installable skills' — with only minor coverage gaps (no mention of update/uninstall); not a 5 because it is not fully comprehensive.

4 / 5

Completeness

Explicitly answers 'what' ('Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path') and 'when' via a concrete 'Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo' clause with concrete triggers.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('list installable skills', 'install a curated skill', 'install a skill from another repo'); good coverage but a few natural synonyms are missing, so above the midpoint but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Codex skill installer) with distinct triggers and minimal overlap risk with other skills; the GitHub-repo/curated-list framing is specific and unlikely to fire for unrelated skills.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
foryourhealth111-pixel/Vibe-Skills
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.