CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflows

Reusable git delivery workflows derived from local slash commands (commit, push, PR, release notes, and GitHub Actions failure triage with worktree-based fixes).

57

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/git-workflows/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 lean, well-structured overview that delegates detail cleanly to real reference files, but its workflows lack inline executable steps and validation feedback loops for destructive/external side effects.

Suggestions

Inline at least one concrete executable example (e.g., a sample conventional-commit command or the branch->commit->push->PR sequence) so the skill is actionable without always opening the reference.

Add an explicit validate->fix->retry checkpoint for the GitHub Actions triage and push/PR workflows (e.g., run CI locally or re-check status before submitting the PR).

DimensionReasoningScore

Conciseness

Lean ~40-line body with no concept re-explanation; the intro sentence and 'Source of truth' framing restate the description and could be trimmed slightly, keeping it just below anchor 5.

4 / 5

Actionability

Safety rules and explicit file pointers are actionable, but the executable command steps are delegated to reference files rather than given inline, leaving concrete guidance incomplete.

3 / 5

Workflow Clarity

A meta-workflow with a confirmation-before-side-effect checkpoint exists, but there is no validate->fix->retry feedback loop and the real steps are external, so the destructive/external-side-effect cap of 3 applies.

3 / 5

Progressive Disclosure

Clear concise overview with two well-signaled, one-level-deep references (source-commands.md, command-catalog.md), both verified as real files, with content appropriately split.

5 / 5

Total

15

/

20

Passed

Description

66%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 concretely names several git delivery workflows with natural trigger terms and a distinct niche, but omits an explicit 'Use when...' clause, capping completeness at 3.

Suggestions

Add an explicit 'Use when...' clause listing the trigger phrases (e.g., 'Use when the user asks to commit, push, open a PR, draft release notes, publish a version, or fix a failed GitHub Actions run').

Spell out a synonym such as 'pull request' alongside 'PR' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete workflow types (commit, push, PR, release notes, GitHub Actions triage with worktree fixes); phrased as nouns rather than verb-actions, just shy of the comprehensive anchor 5.

4 / 5

Completeness

Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms users would say (commit, push, PR, release notes, GitHub Actions) are present, but synonyms like 'pull request' and version-bump phrasing are missing.

4 / 5

Distinctiveness Conflict Risk

Clear git-delivery niche with distinct triggers and minimal conflict risk; only minor overlap with a generic git skill keeps it below 5.

4 / 5

Total

15

/

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
TencentCloudBase/CloudBase-AI-Toolkit
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.