CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-installer

Install Codex skills into the canonical git source tree 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).

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/infrastructure_ops/infrastructure_ops/skill-installer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 instruction-only skill body with clear sequencing, verification checkpoints, and excellent signposted one-level-deep references to verified bundle files. Its main weakness is actionability: the pivotal workflow step defers to unnamed 'installer helper commands' whose concrete invocations exist only in a reference file, and there is no error-recovery loop around filesystem verification.

Suggestions

Name the helper scripts and at least one example invocation inline in the core workflow (e.g. `python3 Infrastructure/scripts/list-skills.py` and `install-skill-from-github.py --repo <owner>/<repo> --path <skill-path>`), instead of the abstract 'Run minimal installer helper command' step.

Add a feedback loop after 'Verify resulting filesystem state' — what check to run, and what to do when it fails (route to references/troubleshooting.md) — which would also satisfy the validation rigor expected for install/write operations.

Either reference the remaining bundle files (references/evals.yaml, references/task-profile.json, assets/skill-installer.png) from the body's navigation or remove them, and merge the duplicated rules in 'Anti-Patterns to Avoid' and 'Constraints' into a single section.

DimensionReasoningScore

Conciseness

The body is efficient — short sections, no explaining of concepts Claude already knows — but "Anti-Patterns to Avoid" and "Constraints" duplicate each other (the no-overwrite-without-confirmation and untrusted-input rules each appear twice), and the opening line restates the description. These are minor trimmable redundancies, matching 'efficient; minor instances of over-explanation' rather than the every-token-earns-its-place level of a 5.

4 / 5

Actionability

The Required output contract is concrete (named fields like schema_version, validation_evidence, restart_required) and the workflow names the classification step, but the core execution step is abstract — "Run minimal installer helper command" never names which script to run or with what arguments; the actual commands (e.g. `python3 Infrastructure/scripts/list-skills.py`) appear only in references/install-flows.md. This is some concrete guidance with key executable details missing, not the mostly-executable level of a 4.

3 / 5

Workflow Clarity

The 5-step core workflow is clearly sequenced and includes checkpoints — "Resolve source and destination with explicit user intent" before writing and "Verify resulting filesystem state" before reporting — fitting 'clear sequence with most checkpoints present'. It is not a 5 because there is no feedback loop for verification failure and the verification step names no concrete check (no command or comparison to perform).

4 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled 'Read when' section pointing one level deep to real files (references/install-flows.md, references/troubleshooting.md, references/contract.yaml — all verified present), each with an explicit trigger condition. It falls short of a 5 because the bundle also contains references/evals.yaml, references/task-profile.json, and assets/ images that are never referenced or navigable from the body — minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

83%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 with an explicit third-person statement of what the skill does and concrete 'Use when' trigger phrases covering listing, curated installs, and repo installs including private repos. The only weaknesses are minor: a few missing natural synonyms and no explicit boundary against skill-creation requests.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Install Codex skills into the canonical git source tree from a curated list or a GitHub repo path" plus "list installable skills" and "install a skill from another repo" — but omits verification and destination-resolution behaviors, leaving minor coverage gaps rather than the comprehensive coverage of a 5.

4 / 5

Completeness

It explicitly answers both questions: the what ("Install Codex skills into the canonical git source tree from a curated list or a GitHub repo path") and the when with concrete trigger phrases ("Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos)") — matching the top anchor exactly. It is not a 4 because the when-clause is already fully explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered ("list installable skills", "install a curated skill", "install a skill from another repo", "private repos"), but common synonyms such as "add a skill", "browse", or "catalog" are missing, so it falls just short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The install/list niche is mostly distinct with a clear trigger set, but the description does not delineate the create/refactor-vs-install boundary, so a request like "add a new skill" carries minor overlap risk with skill-creation skills — fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict profile of a 5.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/infrastructure_ops/infrastructure_ops/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.