4/ Create Your Own Skills and Commit Them to Git

When this pattern helps

Treat this as an extension point with an explicit trigger, inputs, permissions, and failure behavior. Start with a narrow workflow, document prerequisites, and verify the action in a disposable project before making it part of a team routine.

把它当作扩展点来设计：明确触发条件、输入、权限和失败处理。先从窄流程开始，写清前置条件，并在临时项目验证后再纳入团队日常。

Reuse across every project. Tips from the team:

If you do something more than once a day, turn it into a skill or command
Build a /techdebt slash command and run it at the end of every session to find and kill duplicated code
Set up a slash command that syncs 7 days of Slack, GDrive, Asana, and GitHub into one context dump
Build analytics-engineer-style agents that write dbt models, review code, and test changes in dev

See: Extend Claude with Skills — Claude Code Docs

Original source on X