source-code-management

caddy-security source code management and commit message rules. Use when creating, reviewing, or updating commit messages, especially when the user asks to create a commit message for a change in this repository.

Quality

88%

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

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable convention guide with concrete templates and examples, but it is verbose due to repeated indicator listings and is a long monolithic document that does not progressively disclose detail into bundled reference files.

Suggestions

Consolidate the change-indicator coverage: keep the product-surface and maintenance lists, and trim the prose "Selection rules" bullets that re-explain the same indicators, or move the full indicator reference into a bundled file.

Split the indicator catalog (product-surface + maintenance lists) into a references/ file and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Add a short validation checklist (subject under 87 chars, indicator+colon present, required body sections in order, links comma-separated) so the writer can self-verify before finalizing the message.

Dimension	Reasoning	Score
Conciseness	The change indicators are explained three times — in prose "Selection rules", then a full "product-surface indicators" list, then a "maintenance indicators" list — which is redundant and could be tightened, though most content is genuinely repo-specific rather than generic padding.	2 / 3
Actionability	Provides a copy-paste commit message template, a complete worked example, exact rules (87-char limit, colon form, ordered body sections, link formatting), and a concrete file workflow with the YYYYMMDD_HHMM_ prefix.	3 / 3
Workflow Clarity	The single action (write a commit message) is unambiguous with an explicit template, a fixed required-section order, and a clear tmp/commits file workflow; the simple-skill exception applies since this is not a destructive or batch operation.	3 / 3
Progressive Disclosure	The skill is a single well-organized SKILL.md with no bundle files and no external references, but at ~150 lines the indicator catalogs are inline monolithically where a separate reference file would aid navigation.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, well-scoped description that clearly states the skill's purpose and gives explicit, natural trigger conditions for when to invoke it. It answers both "what" and "when" without padding.

Dimension	Reasoning	Score
Specificity	Names concrete actions — "creating, reviewing, or updating commit messages" — tied to a specific domain (caddy-security commit message rules), matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	States both what it does ("commit message rules") and when to use it via an explicit "Use when creating, reviewing, or updating commit messages, especially when the user asks..." clause.	3 / 3
Trigger Term Quality	"commit message(s)" and "create a commit message for a change" are exactly the natural phrases a user would say, giving good coverage of likely trigger terms.	3 / 3
Distinctiveness Conflict Risk	Scoped to "caddy-security" and "this repository" with commit-message-specific triggers, forming a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: greenpau/caddy-security
Path: .codex/skills/source-code-management/SKILL.md
Commit: b96087f

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