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

75%

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/skills/infrastructure_ops/plugin-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 well-organized, lean skill body that delegates detail to real one-level-deep bundle files and includes explicit fail-fast validation. All dimensions sit at 4: the meta-noise 'context-disposition policy' line, some overlap between boundary/failure/gotcha sections, unexplained reference entries, and an unverifiable external path keep it from anchor 5.

Suggestions

Delete or move the 'Apply the context-disposition policy' line out of the Workflow section; it describes skill-authoring practice, not plugin installation.

Give each References entry a one-line purpose (or 'read when' guidance) for evals.yaml, contract.yaml, and task-profile.json so navigation matches the signaling already present for workflow.md.

Add an explicit numbered install sequence in the body (or a stronger summary of the workflow.md steps) and verify the external contract and validation script paths resolve from the bundle.

DimensionReasoningScore

Conciseness

The body is fragment-style and lean throughout with no explanations of concepts Claude already knows, but the 'Apply the context-disposition policy' line in Workflow is authoring meta-noise unrelated to installing plugins, and Execution Boundaries, Failure Mode, and Gotchas partially restate each other.

4 / 5

Actionability

Provides a concrete validation command, enumerated Inputs/Outputs, explicit allowlisted hosts, and a working pointer to references/workflow.md containing the full command matrix. Minor gaps: no inline install command in the body, and the validation script path (Infrastructure/scripts/...) is not present in the bundle.

4 / 5

Workflow Clarity

The install sequence lives in a clearly signaled one-level reference (references/workflow.md) with a 6-step procedure and blocker list, and the body includes an explicit fail-fast validation checkpoint with blocker reporting, so the destructive-operation cap at 3 does not apply. It falls short of 5 because the body's own sequencing is only implicit.

4 / 5

Progressive Disclosure

Structure is good: a 'Read when' navigation block, one-level-deep references that exist in the bundle (references/workflow.md verified), and a References section. Minor gaps: evals.yaml, contract.yaml, task-profile.json, and assets/ are listed without purpose signaling, and the external contract path ../../../../../Infrastructure/... is not verifiable in this bundle.

4 / 5

Total

16

/

20

Passed

Description

67%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 description with a clear 'what' and an explicit 'Use when' clause covering concrete capabilities (quarantine validation, provenance, rollback). Its main weakness is trigger-term quality: the 'when' clause is meta-criteria rather than phrases a user would naturally say, and natural synonyms like 'add plugin' or 'GitHub' are absent.

Suggestions

Rewrite the trigger clause to concrete user phrases, e.g. 'Use when the user asks to install, add, or deploy a plugin from a GitHub URL or other source repo.'

Add natural synonyms and concrete nouns users would say (e.g. 'add plugin', 'GitHub', 'source repo', 'pinned ref') alongside the existing jargon like 'provenance' and 'quarantine'.

Name the destination context (e.g. 'into a Codex plugin root / Plugins directory') so the trigger more precisely distinguishes install requests from plugin creation or hardening requests.

DimensionReasoningScore

Specificity

Names the domain (Codex plugin installation) and several concrete capabilities — 'quarantine validation, provenance, and rollback' — but the install flow itself (resolve, stage, promote, verify) is not enumerated and 'trusted sources' is abstract, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Both a clear 'what' ('Install validated Codex plugins from trusted sources with quarantine validation, provenance, and rollback') and an explicit 'Use when' clause are present, but the 'when' is circular ('distribution and installation are the primary goals') rather than concrete user trigger phrases, so it does not reach anchor 5.

4 / 5

Trigger Term Quality

'Install' and 'plugins' are natural user terms, but the trigger clause 'when distribution and installation are the primary goals' is meta-criteria users would not naturally say, and common variations like 'add plugin', 'GitHub', or 'marketplace' are missing while jargon like 'provenance' dominates.

3 / 5

Distinctiveness Conflict Risk

'Install validated Codex plugins' carves a distinct install-focused niche separate from plugin creation or hardening skills, with only minor overlap risk against closely related sibling plugin skills since the description itself performs no routing.

4 / 5

Total

15

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/plugin-factory/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.