CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflows

Always invoke this skill for any git-related request (commit messages, staging review, history, PR descriptions, etc.) so git workflows are handled consistently.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 high-quality, actionable skill body with executable scripts, explicit approval/validation gates on the destructive and batch operations, and clean one-level-deep references to a verified bundle. The only minor weakness is a slightly verbose repo-root argument explanation.

DimensionReasoningScore

Conciseness

The body is mostly lean operational guidance that avoids explaining concepts Claude already knows, but the repo-root argument paragraph ("Always provide the target Git repository root explicitly...") is somewhat over-explained and could be trimmed.

4 / 5

Actionability

Provides real, executable scripts with exact argument syntax and copy-paste examples (e.g. `scripts/git-diff.sh /path/to/repo main`), plus concrete commit-message and PR-body format templates covering the common cases.

5 / 5

Workflow Clarity

Multi-step operations are clearly sequenced with explicit validation checkpoints: operation 3 requires explicit user approval before drafting, operation 5 has a precondition check and an approval gate before executing commits, and an Error Handling section gives recovery guidance.

5 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with one-level-deep, clearly signaled references to `references/*.md` and `scripts/*`, all of which exist in the bundle; detail is appropriately split out rather than inlined.

5 / 5

Total

19

/

20

Passed

Description

75%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 strong, trigger-forward description that clearly tells Claude when to invoke it and names several concrete git capabilities. The main weakness is that the explicit "what" leans on a parenthetical and a benefit phrase rather than standing as a crisp capability list.

DimensionReasoningScore

Specificity

Names the git domain and lists several concrete actions ("commit messages, staging review, history, PR descriptions"), but the trailing "etc." leaves minor coverage gaps, stopping short of comprehensive.

4 / 5

Completeness

Has an explicit "when" ("Always invoke this skill for any git-related request") and a "what" via the parenthetical action list, but the what-clause "so git workflows are handled consistently" is a benefit statement rather than a crisp capability, so it falls just below a 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ("commit messages", "PR descriptions", "staging review", "history"), but omits common variants like "code review", "pull request", and "diff".

4 / 5

Distinctiveness Conflict Risk

Git workflows form a clear niche with distinct triggers, but the blanket "any git-related request" scope creates minor overlap risk with other potentially related git skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ceshine/ceshine-agent-skills
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.