skill-pr-delivery

Ship skill changes to PRs when Codex skills need source edits, projection sync, strict audit, reviewer evidence, commit, push, and PR status.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/skill-pr-delivery/SKILL.md

Quality

Content

67%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, concise, and has a clear workflow with validation feedback loops, but it is an instruction-only skill whose guidance lacks the executable commands needed for fully actionable steps, and one navigation target is missing.

Suggestions

Add concrete executable commands for the key gates — e.g., the projection-sync command, the strict-audit / Plugin Eval invocation, and the exact commit/push sequence — so the workflow is copy-paste ready.

Fix or remove the missing 'Infrastructure/references/deferred-skill-context/agent-ops-skill-pr-delivery/' pointer, since it currently degrades navigation to a non-existent path.

Tighten the Philosophy and Anti-Patterns bullets into specifics that earn their tokens, or fold them into the constraints that already cover the same ground.

Dimension	Reasoning	Score
Conciseness	The body is lean and bulleted with no concept padding, but a few Philosophy/Anti-Patterns bullets are generic guidance rather than load-bearing specifics, landing it just below fully lean.	4 / 5
Actionability	Concrete directives exist ('Classify the lane as create, harden, skillify...', 'Edit canonical skill source, not generated runtime mirrors'), but validation/commit/projection steps give no executable commands (no git, skill-factory, or projection-sync syntax), leaving key details missing.	3 / 5
Workflow Clarity	A clear sequence (classify → check repo → edit source → projection sync → commit/push) is present with an explicit fail-fast feedback loop ('stop at first failed gate; do not proceed until it is fixed and rerun'), though some checkpoint commands remain implicit.	4 / 5
Progressive Disclosure	Well-signaled one-level references to contract.yaml, evals.yaml, and task-profile.json (all present) with a dedicated Progressive Disclosure section; the gap is the broken/deep Infrastructure path which does not exist on disk.	4 / 5
	Total	15 / 20 Passed

Description

80%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 explicitly pairs a 'what' with a 'when' clause, with a clear niche. It loses points for technical-jargon triggers and minor overlap with generic commit/push skills.

Suggestions

Add concrete user-language trigger phrases (e.g., 'Use when the user asks to commit, push, or open a PR for skill changes') alongside the technical 'when' conditions.

Soften jargon like 'projection sync' and 'strict audit' or pair them with plain synonyms so users naturally trigger the skill.

Disambiguate from generic git skills by leading with the skill-specific surface (e.g., 'Deliver Codex skill packages to PRs') rather than 'commit, push'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'source edits, projection sync, strict audit, reviewer evidence, commit, push, and PR status' — covering the delivery pipeline comprehensively, matching the 'multiple specific concrete actions' anchor.	5 / 5
Completeness	It answers both 'what' ('Ship skill changes to PRs' plus the action list) and 'when' (explicit 'when Codex skills need...' clause), but the trigger conditions are technical rather than concrete user-language phrases, so it is not a full 5.	4 / 5
Trigger Term Quality	Natural terms like 'PR', 'commit', 'push', and 'skill' are present, but 'projection sync' and 'strict audit' are technical jargon and common synonyms/file extensions are missing, so it sits just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	'Codex skills' + 'PR delivery' carve a clear niche with distinct triggers, but the generic 'commit, push' actions carry minor overlap risk with general git/PR skills, keeping it just below 5.	4 / 5
	Total	17 / 20 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
Path: Skills/agent-ops/skill-pr-delivery/SKILL.md
Commit: f1f2f21

Reviewed: 2 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.