pluginstaller

Add a Codex plugin from a GitHub repo to a repo or personal marketplace using the current Codex plugin layout and marketplace metadata.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/pluginstaller/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.

The body is well-structured, actionable, and sequenced with validation checkpoints, but it does not surface its one reference file and carries some redundancy between the Workflow and Rules sections.

Suggestions

Link references/install-scope.md explicitly from the Scope guide (e.g. 'See [install-scope.md](references/install-scope.md) for path-resolution details') so the bundled reference is discoverable rather than duplicated inline.

Add an explicit feedback loop in step 2: 'If validation fails, fix the manifest/paths and re-validate before proceeding' to make the validate->fix->retry cycle concrete.

De-duplicate guidance shared between Workflow and Rules (relative paths, marketplace ordering) so each section earns its tokens without restating the other.

Dimension	Reasoning	Score
Conciseness	The body is lean, avoids explaining concepts Claude already knows, and uses tight sections, but the Rules section restates some Workflow guidance (relative paths, marketplace-as-source-of-truth, terminology), which could be trimmed.	4 / 5
Actionability	Guidance is mostly executable with concrete paths, marketplace schema fields, and exact policy values ('AVAILABLE', 'ON_INSTALL'), though a few steps ('Fetch the repo', 'Follow the current Codex plugin docs') remain high-level.	4 / 5
Workflow Clarity	A clear 11-step numbered sequence with explicit validation (validate canonical structure, verify in /plugins, fix-before-complete) is present, but the validate->fix->re-validate feedback loop is implied rather than spelled out.	4 / 5
Progressive Disclosure	Section structure (Inputs, Workflow, Rules, Scope guide) is clear, but the provided references/install-scope.md is never linked or signaled in the body and its content overlaps the inlined Scope guide, leaving a reference present but not clearly navigable.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is specific, third-person, and clearly distinct, but it omits an explicit 'Use when...' trigger clause, which caps its completeness and leaves the activation condition only weakly implied.

Suggestions

Append a 'Use when...' clause naming the natural trigger, e.g. 'Use when the user provides a GitHub repo for a Codex plugin and wants it installed into a repo or personal marketplace.'

Add a common synonym or file cue such as '.codex-plugin/plugin.json' to broaden natural trigger-term coverage.

Consider mirroring the body's trigger phrasing ('wants it available in Codex') so the description and the skill body share one explicit activation phrase.

Dimension	Reasoning	Score
Specificity	Names the concrete source ('a GitHub repo'), two install scopes ('repo or personal marketplace'), and the mechanism ('current Codex plugin layout and marketplace metadata'), listing several specific facets of the action rather than a single generic verb.	4 / 5
Completeness	The 'what' is explicit and clear, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ('Codex plugin', 'GitHub repo', 'marketplace'), giving good coverage, though a few common synonyms (e.g. 'install', '.codex-plugin') are absent.	4 / 5
Distinctiveness Conflict Risk	The scope is narrowly bounded to Codex plugin installation from a GitHub repo into a marketplace, a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: am-will/codex-skills
Path: skills/pluginstaller/SKILL.md
Commit: 9f954c3

Reviewed: 20 hours 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.