git-workflow-specialist

3 stars 1 forks
89
B

Git expert covering branching strategies, collaboration, conflict resolution, and best practices

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install sandraschi/advanced-memory-mcp/git-workflow-specialist
skilz install sandraschi/advanced-memory-mcp/git-workflow-specialist --agent opencode
skilz install sandraschi/advanced-memory-mcp/git-workflow-specialist --agent codex
skilz install sandraschi/advanced-memory-mcp/git-workflow-specialist --agent gemini

First time? Install Skilz: pip install skilz

Works with 14 AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/sandraschi/advanced-memory-mcp
2. Copy the agent skill directory:
cp -r advanced-memory-mcp/skills/technical/git-workflow-specialist ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Stars
3
Forks
1
Type
Technical
Meta-Domain
development
Primary Domain
git
Market Score
89

Agent Skill Grade

B
Score: 89/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
28/30
Ease of Use
22/25
Writing Style
9/10
Utility
18/20

Areas to Improve

  • Description needs trigger phrases
  • Inconsistent Confidence Levels
  • Missing Trigger Terms in Metadata

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-19

Developer Feedback

I took a look at your git-workflow-specialist skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 89/100 — solid B-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Progressive Disclosure Architecture (28/30) — the modular structure with separate files for detailed guidance really shines. The weakest spot is Spec Compliance (12/15), mainly around missing metadata that helps people discover and invoke your skill.

What's Working Well

  • Architecture is clean — SKILL.md as the entry point with detailed modules in separate files is exactly how PDA should work. You're not dumping everything into one file, which keeps token usage lean.
  • Strong utility focus — Your decision matrices and checklists (research-checklist.md, decision frameworks) give people actual tools to work with, not just theory. The problem-solving power here scored 8/8.
  • Consistent voice — Imperative form throughout ("Do X", "Check Y") makes instructions clear without being prescriptive. The writing stays objective and instructional.

The Big One: Missing Trigger Phrases

Your description field lacks explicit trigger terms, and this is costing you 2+ points in spec compliance. Right now it reads:

"Git expert covering branching strategies, collaboration, conflict resolution..."

People invoking Claude won't know to call your skill. You need trigger phrases baked into that description. Change it to something like:

"Performs git workflow specialist operations. Use when asked to 'git workflow', 'git branching strategy', 'merge conflict resolution', 'git collaboration patterns', or 'git best practices'."

This small change makes you...

Report Security Issue

Found a security vulnerability in this agent skill?