Imagine if Claude could work alongside your development team—not just answering questions, but helping you move work forward using the same standards your team values.
Anthropic’s new Skills Directory makes that possible. Skills are folders of instructions, scripts, and resources that Claude loads when needed, turning it into a specialist on the workflows that matter most to you.
Today, you’ll find three Skills from Zapier in the directory. Each one brings software development best practices directly into Claude’s workflow:
code-review evaluates code changes and highlights opportunities to improve quality, security, performance, and consistency—helping cut down on back-and-forth during PR reviews.
git-commit writes clear Conventional Commit messages with helpful context from Jira tickets, so future developers understand not just what changed, but why.
work-on-ticket pulls in ticket details, creates feature branches, and handles planning steps—so developers can start focused work without juggling tools.
When you pair these Skills with Zapier MCP, Claude not only understands how your work happens but can reliably carry out repeatable procedures across your tools. That means faster turnaround times and fewer manual steps.
By combining Agent Skills with Zapier MCP, organizations get AI that knows how work should be done—and does it reliably. Skills encode best practices; MCP runs them at scale, delivering faster turnaround, less busywork, and repeatable AI-powered processes.
Lisa Chapello, Director of AI Product Management at Zapier
What this means for your team
These Skills give teams more time to focus on meaningful work and keep projects moving:
Free up engineering time. Code reviews run continuously in the background, so your team can spend more time on architecture, learning, and mentorship.
Help newer developers grow faster. They get immediate, consistent feedback without waiting for review cycles.
Keep your codebase consistent. Branches follow the same conventions. Commit messages tell a clear story. Planning happens the same way every time.
Reduce friction in daily workflows. Skills follow the processes your team already uses, making adoption natural.
How it all works
Picture a typical sprint. A developer picks up a Jira ticket about refactoring a payment module. Instead of gathering context and setting up a branch manually, they use work-on-ticket. Claude fetches the ticket, creates a branch with your team’s naming conventions, and surfaces the acceptance criteria - all in seconds.
Once the work is ready for review, code-review steps in automatically. It checks the changes against your team’s security and performance standards and flags potential issues, like a risky query pattern. The developer can address these suggestions before requesting a human review.
When the code merges, git-commit generates a commit message that captures the reasoning behind the work and links back to the ticket. Months later, when another teammate investigates related code, they can follow the narrative without tracking down the original author.
The result: smoother handoffs, higher-quality code, and more time for deep technical work.
Get Started
Ready to see these skills in action? Try them out from our GitHub repo and share your feedback in the MCP channel in Zapier's Early Access Program Slack.
