git-workflow-manager
Git Workflow Manager - Auto-activating skill for DevOps Basics. Triggers on: git workflow manager, git workflow manager Part of the DevOps Basics skill category.
33
0%
Does it follow best practices?
Impact
95%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/git-workflow-manager/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that functions more as a label than a useful skill description. It provides no concrete actions, no natural trigger terms, and no guidance on when Claude should select this skill. The repeated trigger term and boilerplate category reference add no value.
Suggestions
Replace the generic label with specific concrete actions, e.g., 'Manages git branching strategies, handles merge workflows, configures branch protection rules, and sets up gitflow or trunk-based development patterns.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about branching strategies, merge conflicts, pull request workflows, git flow, release branches, or repository workflow configuration.'
Remove the duplicated trigger term 'git workflow manager' and replace with diverse, natural keywords users would actually say, such as 'branching', 'merge strategy', 'git flow', 'trunk-based', 'feature branches', 'release process'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It says 'Git Workflow Manager' but never describes what it actually does - no mention of branching, merging, rebasing, commit strategies, or any specific git workflow operations. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states a name and category membership without explaining capabilities or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'git workflow manager' repeated twice. Users would never naturally say 'git workflow manager' - they would say things like 'branching strategy', 'merge conflict', 'git flow', 'pull request workflow', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any git-related skill. 'Git Workflow Manager' could mean anything from branching strategies to CI/CD pipelines to commit conventions, making it impossible to distinguish from other potential git or DevOps skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder or auto-generated template with no substantive content. It contains only meta-descriptions of what the skill claims to do without any actual git workflow instructions, commands, examples, or best practices. It provides zero value to Claude as a skill file.
Suggestions
Replace the meta-description sections with actual git workflow content: specific branching strategies (e.g., GitFlow, trunk-based), concrete git commands for each workflow step, and example scenarios.
Add executable command examples such as `git checkout -b feature/xyz`, `git rebase main`, merge conflict resolution steps, and PR workflows with validation checkpoints.
Include a clear multi-step workflow for common git operations (e.g., feature branch lifecycle: create → develop → rebase → PR → merge) with explicit validation steps like checking for conflicts or running CI.
If advanced topics exist (e.g., cherry-picking strategies, release branching, monorepo workflows), reference them via linked files rather than trying to cover everything inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual actionable content. Every section restates the same vague information about 'git workflow manager' without teaching anything Claude doesn't already know. | 1 / 3 |
Actionability | There are zero concrete commands, code examples, workflows, or specific instructions. The skill describes rather than instructs — phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' promise capabilities without delivering any actual guidance. | 1 / 3 |
Workflow Clarity | No workflow steps, sequences, or validation checkpoints are provided. The skill claims to offer 'step-by-step guidance' but contains no steps whatsoever. There is no process to follow for any git workflow task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-descriptions with no references to detailed materials, no links to related files, and no structured navigation. There is no actual content to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.