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

Securityby

Failed to scan

The risk profile of this skill

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

Quality

Content

71%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 well-structured, lean skill body with strong progressive disclosure and a clear verification-gated workflow. Its main weaknesses are incomplete actionability — the installer command is never named despite scripts existing — and a missing error-recovery feedback loop for a destructive operation.

Suggestions

Name the concrete installer command in the workflow (e.g. `python scripts/install-skill-from-github.py ...` / `python scripts/list-skills.py`) instead of the abstract "Run minimal installer helper command", and link the scripts so the guidance is copy-paste executable.

Add an explicit validate→fix→retry feedback loop after the filesystem verification step, since the skill performs overwrite-capable installs.

Deduplicate the Anti-Patterns and Constraints sections (overwrite-without-confirmation and untrusted-URL handling each appear twice) to recover the conciseness that the duplication costs.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or over-explanation of known concepts, but the Anti-Patterns and Constraints sections duplicate each other ("Do not overwrite existing installs without explicit confirmation" / "Treating untrusted URLs or paths as safe inputs"), which is minor trimming that could be done; not a 5 because of that redundancy.	4 / 5
Actionability	The workflow step "Run minimal installer helper command" never names the actual script or invocation, and the available scripts (install-skill-from-github.py, list-skills.py) are not referenced from the body, so executable guidance is incomplete despite the concrete output-contract fields; not a 4 because the key command detail is missing.	3 / 5
Workflow Clarity	A clear 5-step sequence with an explicit verify-filesystem checkpoint (step 4) and a required validation_evidence field, but it lacks an explicit validate→fix→retry feedback loop for a destructive/overwrite-capable operation; not a 5 because error-recovery feedback is absent.	4 / 5
Progressive Disclosure	The body is an overview with three well-signaled one-level-deep references (install-flows.md, troubleshooting.md, contract.yaml), each gated by an explicit "Read when" condition and verified to exist in references/, making navigation easy with no nesting.	5 / 5
	Total	16 / 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 clearly states both capability and explicit usage triggers with natural phrasing. It is comprehensive on completeness and distinctiveness, with only minor gaps in action coverage and trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and 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" — with only minor coverage gaps; not a 5 because it stops short of a comprehensive action list.	4 / 5
Completeness	Explicitly answers both what ("Install Codex skills into the canonical git source tree...") and when ("Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases are present ("list installable skills", "install a curated skill", "install a skill from another repo", "including private repos"); a few synonyms or path/extension variants are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Install Codex skills" carves a clear niche with distinct triggers and minimal conflict risk, reinforced by the body routing creation/refactor and release work to other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 2f91362

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.