CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plugin-installer

Install validated Codex plugins from trusted sources with quarantine validation, provenance, and rollback. Use when distribution and installation are the primary goals.

Quality

69%

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/plugin-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/infrastructure_ops/plugin-installer/SKILL.md

The canonical home for this skill is plugin-installer in jscraik/Agent-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

The body is well-structured and token-efficient with clear ownership boundaries, routing, and a fail-fast validation stance. However, it delegates its core execution protocol to reference files that are missing from the bundle, so the skill as shipped offers no executable install flow, and the bundled scripts go unmentioned.

Suggestions

Inline the staged install sequence (quarantine, validate, install, refresh, rollback) as numbered steps with explicit validation checkpoints in SKILL.md, since the delegated `references/workflow.md` is absent from the bundle and currently leaves the core procedure unactionable.

Create the missing `references/` files (workflow.md, contract.yaml, evals.yaml, task-profile.json) or remove the dead links so progressive disclosure actually resolves.

Reference the existing bundle scripts (e.g., `scripts/install-plugin-from-github.py`) from the body so the executable tooling is discoverable instead of orphaned.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: terse Inputs/Outputs, no re-teaching of concepts Claude knows. Minor trimmable instances remain, e.g., the maintenance-oriented line "Apply the context-disposition policy: move important still-valid context to references..." and overlap across Anti-Patterns, Failure Mode, and Gotchas.

4 / 5

Actionability

Concrete details exist (output fields, the validation command, allowlisted hosts), but the actual install procedure is entirely delegated via "Use the staged install protocol in `references/workflow.md"" — and that file is absent from the bundle, leaving no executable steps for the core task. Fits anchor 3 (some concrete guidance, incomplete) better than anchor 2 since inputs, outputs, and a fail-fast gate command are specified.

3 / 5

Workflow Clarity

The staged flow is only implied ("separate preview/quarantine validation from install, projection refresh, rollback") with no sequenced steps in the body, and the fail-fast validation policy ("stop at first failed gate and report blocker text") plus stop conditions are explicit but their checkpoints live in the missing workflow file. This lands on anchor 3: sequence present but implicit, validation described but not woven into ordered steps.

3 / 5

Progressive Disclosure

References are clearly signaled ("Read when" bullets with reasons), but all four cited files under `references/` (workflow.md, contract.yaml, evals.yaml, task-profile.json) do not exist in the bundle, so the primary detailed-content pointer is dead. Additionally, the bundled `scripts/` files (install-plugin-from-github.py, github_utils.py) are never referenced from the body, leaving navigation broken rather than merely imperfect — below anchor 3's "references present".

2 / 5

Total

12

/

20

Passed

Description

75%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: third-person, concise, with a clear what and an explicit Use-when clause. Trigger terms and concrete capabilities are well covered; the when-clause could name more concrete trigger phrases and the description could disambiguate against sibling plugin skills.

DimensionReasoningScore

Specificity

"Install validated Codex plugins from trusted sources with quarantine validation, provenance, and rollback" names the domain and several concrete capabilities (quarantine validation, provenance, rollback). It falls short of anchor 5 because "trusted sources" is vague and body-level features like visibility recovery are not covered.

4 / 5

Completeness

Both parts are present: a clear "what" (install with quarantine validation, provenance, rollback) and an explicit "Use when distribution and installation are the primary goals" clause. The when-clause lacks concrete trigger phrases, matching anchor 4 ("'when' could be more explicit or specific") rather than anchor 5.

4 / 5

Trigger Term Quality

Natural keywords a user would say are present: "install", "Codex plugins", "quarantine", "provenance", "rollback", "distribution". A few common variations are missing (e.g., "set up", "add", "deploy"), so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Install validated Codex plugins from trusted sources" carves a mostly distinct installation-only niche with minimal conflict risk. It stays at anchor 4 rather than 5 because closely related sibling skills (plugin creation, hardening) exist and are only disambiguated in the body, not the description.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

13

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/plugin-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/infrastructure_ops/plugin-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.