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.

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is highly actionable with executable scripts, clear sequenced workflows, and explicit approval/validation checkpoints, supported by a well-organized one-level-deep reference structure. The only weakness is mild verbosity in the repeated repo-root argument explanation.

Suggestions

Consolidate the repo-root argument justification (currently repeated across lines 21–28 and within each operation) into a single concise note near the script listing to reduce redundancy.

Trim the prose in "Workflow Notes" and the cached-diff section where the same repo-root guidance is restated, keeping only the actionable command forms.

DimensionReasoningScore

Conciseness

The body is mostly lean and task-focused with no basic-concept padding, but the repeated, lengthy prose justifying the repo-root argument (lines 21–28 and re-explanations in each operation) could be tightened into a single note.

2 / 3

Actionability

Provides concrete, copy-paste-ready script invocations with arguments and examples (e.g. `scripts/git-diff.sh /path/to/repo main`) plus a complete commit-message template and PR format, rather than abstract direction.

3 / 3

Workflow Clarity

Operations are clearly sequenced (1–5 with sub-operations 1a/1c) and include explicit validation/approval checkpoints ("Only move on... after an explicit approval", precondition checks, and an Error Handling section with recovery steps).

3 / 3

Progressive Disclosure

Clear overview with well-signaled one-level-deep references (general/python/rust code review guidelines and auto_commit_workflow.md, all verified present) and organized scripts/, with detailed content appropriately split out of SKILL.md.

3 / 3

Total

11

/

12

Passed

Description

100%

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, uses natural trigger terms, and explicitly pairs a clear "what" with an explicit "when" invocation clause in third-person voice. It is concise and avoids vague fluff.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — "commit messages, staging review, history, PR descriptions" — matching the anchor for listing several specific concrete actions rather than a single vague domain.

3 / 3

Completeness

Explicitly answers both what (git workflow handling across commits/staging/history/PRs) and when ("Always invoke this skill for any git-related request"), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say ("commit messages", "staging review", "history", "PR descriptions"), giving good coverage of common phrasings rather than just one keyword.

3 / 3

Distinctiveness Conflict Risk

The "git-related request" niche is clearly bounded with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.