CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

source-code-management

Create or review caddy-security commit messages using repository indicators, required body sections, and timestamped message files. A message request does not create a commit.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/source-code-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a strong, rule-dense instruction set: concrete indicator vocabulary, exact subject and body formatting, a template plus worked example, and an unambiguous file-output workflow with validation checkpoints. Its only real weaknesses are the redundant Acceptance criteria recap and the absence of a single consolidated step-by-step procedure.

DimensionReasoningScore

Conciseness

The body is dense with repository-specific rules and explains nothing Claude already knows; the only trimmable material is the Acceptance criteria section, which restates ~10 lines of rules already given, matching 'efficient; minor instances that could be trimmed' rather than the lean 5.

4 / 5

Actionability

Everything is executable: exact indicator labels, the `indicator: concise subject under 87 characters` format, a copy-paste message template, a complete worked example, the `tmp/commits` location with `YYYYMMDD_HHMM_` prefix, and the required `git commit -F` command — fully covering the common cases.

5 / 5

Workflow Clarity

It has an explicit pre-step ("Inspect the requested diff and `git status --short`, including staged and unstaged work, before describing it") and validation checkpoints (review for tmp/ references, Tests must not claim unrun checks), but the workflow is spread across topic sections rather than a single sequenced procedure and lacks an error-recovery loop, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

With no bundle files, the single SKILL.md is well-sectioned (rules, indicators, body rules, template, workflow, acceptance criteria) and its one cross-reference to ../release-and-versioning/SKILL.md is clearly signaled; content is appropriately placed inline, with only minor room to split the indicator tables into a reference file.

4 / 5

Total

17

/

20

Passed

Description

58%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 states a specific, appropriately narrow capability with concrete artifacts (indicators, body sections, timestamped message files) and a useful scope clarification that a message request does not commit. Its main weakness is the complete absence of 'when to use this' trigger guidance and thin natural-language keyword coverage beyond "commit messages".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to write, create, review, or improve a commit message in the caddy-security repository".

Include natural keyword variations users would actually say, such as "git commit", "commit message subject/body", or "describe this diff/changes".

Optionally note the deliverables users would ask for by name — the timestamped message file under tmp/commits and the accompanying git commit -F command — to sharpen the 'what'.

DimensionReasoningScore

Specificity

"Create or review caddy-security commit messages using repository indicators, required body sections, and timestamped message files" lists several concrete actions with only minor gaps (the git commit -F workflow and review-only behavior are not mentioned), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

The 'what' is clear (create or review caddy-security commit messages with indicators, body sections, and timestamped files) but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3; it is not 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

"commit messages" plus "create" and "review" are relevant natural keywords, but common variations users would say ("git commit", "commit", "diff", "write a commit message") are missing, so coverage is not yet at the 'good keyword coverage, a few missing' level.

3 / 5

Distinctiveness Conflict Risk

"caddy-security commit messages" carves out a clear niche, but the generic "commit messages" trigger could also match a general commit-message skill, leaving minor overlap risk rather than the minimal-conflict profile of a 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

greenpau/caddy-security

Path

.codex/skills/source-code-management/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.