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 description is essentially a placeholder with no substantive content. It fails on all dimensions: it lists no concrete actions, provides no natural trigger terms, lacks both 'what' and 'when' information, and is indistinguishable from any other git-related skill. The duplicate trigger term suggests auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Manages git branching strategies, configures merge policies, sets up CI/CD-related git hooks, and resolves workflow conflicts.'
Add a 'Use when...' clause with natural trigger terms like 'branching strategy', 'git flow', 'merge policy', 'pull request workflow', 'release branch', 'feature branch'.
Differentiate from other potential git skills by specifying the scope — e.g., whether this covers branching models, PR workflows, release management, or all of the above.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Git Workflow Manager') and its category ('DevOps Basics') without describing what it actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no description of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'git workflow manager' repeated twice. These are not natural phrases users would say — users would more likely say things like 'branching strategy', 'merge conflict', 'pull request', 'git flow', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Git Workflow Manager' could overlap with any git-related skill. Without specific actions or scope boundaries, it would be impossible to distinguish from other 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 an empty template with no substantive content. It contains only generic boilerplate descriptions that repeat the phrase 'git workflow manager' without ever defining what a git workflow is, which workflows to use, or how to implement them. It provides zero actionable guidance, no code, no commands, and no real information.
Suggestions
Add concrete git workflow definitions (e.g., GitFlow, trunk-based development) with specific branch naming conventions and example commands like `git checkout -b feature/xyz`, `git merge --no-ff`.
Include executable examples showing common workflow operations: creating feature branches, handling pull requests, resolving merge conflicts, and tagging releases.
Define a clear multi-step workflow with validation checkpoints, e.g., pre-commit checks, branch protection rules, and merge criteria.
Remove all boilerplate sections ('Purpose', 'When to Use', 'Example Triggers') that contain no technical content and replace them with actionable reference material.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no specific technical content, and every section restates the same vague idea ('git workflow manager') without adding value. | 1 / 3 |
Actionability | There are zero concrete commands, code examples, configurations, or executable instructions. The skill describes what it could do in abstract terms but never provides any actual guidance on git workflows. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. There is no sequence, no validation, no checkpoints—just vague claims like 'provides step-by-step guidance' without any actual steps. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no structured navigation, and no bundle files. The content is a monolithic block of placeholder text with no meaningful organization of information. | 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
13d35b8
- 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.