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
Quality
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 provides only a title and category metadata without describing any actual capabilities, use cases, or natural trigger terms. Claude would have no basis for selecting this skill appropriately from a list of alternatives.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Creates branches, manages merges, resolves conflicts, sets up git hooks, configures remote repositories').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about branching strategies, merge conflicts, git configuration, or workflow automation').
Remove the redundant duplicate trigger term and replace with varied natural language triggers like 'git branch', 'merge strategy', 'pull request workflow', 'gitflow'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Git Workflow Manager' is a title, not a description of capabilities. There are no verbs describing what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions listed) and 'when should Claude use it' (no use cases or explicit triggers beyond the skill name itself). | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'git workflow manager' repeated twice, which is not a natural phrase users would say. Missing common terms like 'branch', 'merge', 'pull request', 'commit', 'rebase', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Git Workflow Manager' is extremely vague and could overlap with any git-related skill. 'DevOps Basics' category provides no differentiation. No specific niche or distinct triggers are defined. | 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 template with no substantive content. It describes what a git workflow manager skill should do but provides zero actual guidance, commands, examples, or workflows. The entire content could be replaced with a single sentence without losing information.
Suggestions
Add concrete git workflow examples with executable commands (e.g., feature branch workflow: `git checkout -b feature/name`, commit conventions, PR process)
Include specific workflow patterns like GitFlow, trunk-based development, or GitHub Flow with step-by-step sequences
Provide copy-paste ready command sequences for common operations (branching, merging, rebasing, conflict resolution)
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Despite claiming to provide 'step-by-step guidance,' the skill contains zero actual steps for any git workflow task. | 1 / 3 |
Progressive Disclosure | No structure for discovery or navigation. The content is a flat list of vague claims with no references to detailed materials, examples, or related documentation. | 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
994edc4
- 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.