CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-installer

Use when listing or installing Codex skills from curated sources, GitHub repo paths, private repos, or local package locations.

Quality

78%

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 ./skills-system/skill-installer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 strongly actionable body: real commands with flags, worked examples, an exact output template, and explicit validation/blocker language for both the installer and SDK contract checks. The weaknesses are efficiency (redundant Philosophy/SDK prose) and a slightly scattered workflow ordering with no explicit retry loop, plus a heavy inline SDK section that belongs in the existing reference files.

Suggestions

Delete the redundant line 'Install skills with the helper scripts.' and collapse the Philosophy section into the When To Use bullets; fold the SDK Package Checks detail into a new reference file (e.g., references/sdk-checks.md) with a one-line pointer, keeping only the blocked/pass/fail rule inline.

Present the install flow as a single numbered sequence (route selection → run script → validate → report source/destination/validation → restart message) so the checkpoints already described in Behavior and SDK sections form one explicit checklist.

Add a brief retry instruction for the documented download-to-git fallback and reference the unreferenced bundle files (task-profile.json, assets) from the body so every bundle file is discoverable.

DimensionReasoningScore

Conciseness

Mostly efficient — the Scripts, Behavior and Options, and Notes sections are dense tables of commands and facts — but there is avoidable fat: the two-paragraph 'Philosophy' section is abstract framing Claude could infer, line 40 ('Install skills with the helper scripts.') redundantly repeats the bullet list above it, and the 24-line jargon-heavy 'SDK Package Checks' section (ordered lanes, Tessl, OTEL, scorer-calibration) is verbose relative to the simple install task. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'); it is above anchor 2 (not 'several unnecessary explanations') but below anchor 4 because the Philosophy and SDK sections are more than minor trimmings.

3 / 5

Actionability

Fully executable commands with real flags are given throughout — `scripts/list-skills.py --format json`, `scripts/install-skill-from-github.py --repo <owner>/<repo> --path <path/to/skill>`, `--url https://github.com/<owner>/<repo>/tree/<ref>/<path>` — plus worked examples for both listing and installing, an exact output template for listings, and a concrete restart message. The common cases (curated name, repo path, URL, experimental) each have a copy-paste-ready invocation, matching anchor 5 ('fully executable; copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

The sequence is clear: decide route from the user's input type (When To Use), run the matching script, then report source, destination, validation, and restart guidance (Examples), and validation checkpoints are explicit — the installer aborts on an existing destination, and SDK steps require a start receipt, `skills package verify`, and `blocked_validation` classification on missing contract files. It is below anchor 5 because the install flow itself has no validate-and-retry feedback loop (the mainline 'download falls back to git sparse checkout' is stated as behavior, not as a retry instruction), and the ordering is scattered across Philosophy/When To Use/Scripts/Examples rather than one checklist; the SDK checklist partially compensates, placing this above anchor 3's 'checkpoints missing or implicit'.

4 / 5

Progressive Disclosure

Structure is good: a References section clearly signals four one-level-deep files (references/contract.yaml, references/evals.yaml, references/skill-factory/install-flows.md, references/skill-factory/troubleshooting.md), all of which exist in the bundle, and the 136-line body stays at overview altitude for most sections. It falls short of anchor 5 because the long SDK Package Checks section is detailed inline content that would fit the existing references pattern (install-flows.md already absorbs similar detail), `task-profile.json` and the assets are never pointed to, and `references/skill-factory/` duplicates contract.yaml/evals.yaml/task-profile.json from the parent references/ directory, which muddies navigation slightly — matching anchor 4 ('most content is appropriately placed; references mostly clear; minor organization gaps') and clearly above anchor 3.

4 / 5

Total

16

/

20

Passed

Description

73%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 solid, trigger-first description with explicit 'Use when...' guidance, good natural keyword coverage, and a distinct niche. Its main weakness is thin capability coverage — 'listing or installing' captures only two of the skill's actions and the 'what' is folded into the 'when' clause rather than stated separately.

Suggestions

Lead with a one-sentence capability statement (e.g., 'Lists, installs, and verifies Codex skill packages') before the 'Use when...' clause so 'what' is explicit rather than embedded in the trigger sentence.

Add one or two more concrete actions to the capability list, such as reporting install validation as pass/fail/blocked or checking whether a skill is already installed locally, to lift specificity from '1-2 actions' toward comprehensive.

Include a common synonym such as 'catalog' alongside 'curated sources' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Codex skills") and two concrete actions ("listing or installing") and enumerates concrete source types ("curated sources, GitHub repo paths, private repos, or local package locations"), but covers only two actions and omits capabilities the body documents such as validation/pass-fail-blocked reporting and checking whether a skill is already installed. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive"); it is above anchor 2 because the actions and sources are named, but below anchor 4 because the action list is not 'several'.

3 / 5

Completeness

Both 'what' and 'when' are answered: what = "listing or installing Codex skills", when = "from curated sources, GitHub repo paths, private repos, or local package locations", with an explicit "Use when..." clause so it is not capped at 3. It sits below anchor 5 because the 'what' is embedded in the single 'when' sentence rather than stated as a distinct capability statement (compare the anchor-5 example's two-sentence structure), so the what/when split is present but less explicit than it could be.

4 / 5

Trigger Term Quality

Natural phrases users would say are present — "installing Codex skills", "GitHub repo paths", "private repos", "curated sources" — giving good keyword coverage across the main trigger surfaces. It falls short of anchor 5 because common synonyms like "catalog", "download a skill", or "what skills are available" are missing, but it clearly exceeds anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct — installing Codex skill packages from specific sources — with triggers (curated catalog, GitHub repo paths, private repos) unlikely to fire for unrelated skills; other skill-creation or code-review skills would not match this description. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk') and is above anchor 4's 'minor overlap risk'.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

jscraik/Agent-Skills

Path

skills-system/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.