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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

57%

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

The body is well-organized with a clean overview, a sequenced workflow with a verification step, and properly structured one-level references. It loses points for duplicated anti-pattern/constraint content, an unnamed installer command, and the absence of an inline failure-retry loop.

Suggestions

Merge the "Anti-Patterns to Avoid" and "Constraints" sections, since both repeat the no-overwrite-without-confirmation and untrusted-input rules.

Name the actual installer helper command (and reference scripts/install-skill-from-github.py and scripts/list-skills.py) in the workflow instead of "Run minimal installer helper command".

Add an inline feedback loop after step 4 — e.g., "If verification fails, consult troubleshooting and re-run" — rather than only signposting failures externally.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no concept explanations, but "Anti-Patterns to Avoid" and "Constraints" duplicate the same two ideas ("Do not overwrite existing installs without explicit confirmation" / treating URLs and paths as untrusted), so it could be tightened.	2 / 3
Actionability	The required output contract lists concrete fields and the workflow is sequenced, but "Run minimal installer helper command" never names the actual command, leaving a key detail unspecified.	2 / 3
Workflow Clarity	The five-step sequence includes an explicit verify step ("Verify resulting filesystem state"), so it is not capped for missing validation, but there is no inline error-recovery feedback loop — failures are only delegated to troubleshooting.md.	2 / 3
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references (install-flows.md, troubleshooting.md, contract.yaml), each tied to a specific read-when condition, and all referenced files exist in references/.	3 / 3
	Total	9 / 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.

The description is specific, uses third-person voice, and pairs a concrete capability statement with an explicit "Use when" trigger clause. It scores at the top on all four dimensions with no over-claims or filler.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Install Codex skills into the canonical git source tree from a curated list or a GitHub repo path" and "list installable skills, install a curated skill, or install a skill from another repo (including private repos)" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what ("Install Codex skills into the canonical git source tree from a curated list or a GitHub repo path") and when (explicit "Use when..." triggers), satisfying the top anchor.	3 / 3
Trigger Term Quality	The "Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos)" clause covers natural phrases a user would actually say, with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	The niche is clearly scoped to installing Codex skills from curated/GitHub sources with distinct triggers, making overlap with other skills unlikely.	3 / 3
	Total	12 / 12 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
Commit: 5a6027f

Reviewed: 5 days 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.