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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill git-workflow-managerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely underdeveloped and essentially non-functional for skill selection purposes. It provides only a title and category metadata without any actual description of capabilities, use cases, or natural trigger terms. Claude would have no meaningful basis to select this skill over others.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Manages git branching strategies, handles merge conflicts, sets up CI/CD pipelines, configures git hooks')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about branching, merging, pull requests, git flow, or repository management')
Remove the duplicate trigger term and add varied natural language triggers like 'branch', 'merge', 'PR', 'git flow', 'repository setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Git Workflow Manager' as a title with no explanation of what it actually does. No specific capabilities like 'create branches', 'manage merges', or 'resolve conflicts' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague title, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 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 | The description is extremely generic - 'Git Workflow Manager' and 'DevOps Basics' could overlap with any git-related or DevOps skill. No specific niche or distinct triggers are defined. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes itself in generic marketing language but provides zero actionable guidance on git workflows, branching strategies, merge processes, or any concrete DevOps practices. The skill fails on all dimensions because it contains no actual instructions.
Suggestions
Add concrete git workflow examples (e.g., feature branch workflow, GitFlow, trunk-based development) with actual git commands
Include executable code snippets showing common operations like creating branches, handling merges, and resolving conflicts
Define a clear workflow sequence with validation steps (e.g., 1. Create branch, 2. Make changes, 3. Run tests, 4. Create PR, 5. Review checklist)
Remove all generic boilerplate text and replace with specific, actionable guidance that Claude doesn't already know
| 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 in abstract terms but never shows how to actually manage git workflows. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Despite being a 'workflow manager' skill, there are no sequences, validation checkpoints, or actual process guidance. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or related documentation that would help Claude learn git workflow management. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.