Menu
Tags the current git repository with a new version tag. Use when marking a release point in git history.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user wants to evaluate, score, review, or automatically improve an existing agent skill (a SKILL.md) — e.g. "optimize this skill", "score my skill", "review my SKILL.md", "how good is this skill", "auto-optimize", "improve skill quality". Use when a skill needs quality assessment against a rubric or iterative refinement.
Distills a session's repeatable workflow into a new project skill in .claude/skills/. Use when a session solved a non-trivial, repeatable problem and the workflow is worth capturing for reuse — e.g. "save this", "distill this", "turn this into a skill", "capture this workflow", "make a skill from this", or at the end of a session that produced a reusable pattern.
Use when the user wants to capture, replicate, or distill how a specific person (or topic/role) thinks into a reusable thinking-framework skill — e.g. "distill Munger", "make a Feynman skill", "build an X-perspective", "how does <person> think", or updating an existing <person>-perspective skill. Also use when the user expresses a vague need for a thinking partner or decision lens ("help me improve decision quality", "I need a mental-model advisor", "is there a way of thinking that helps me see business clearly").
Refines an existing project skill in .claude/skills/ with new learnings from the current session. Use when updating or improving an existing skill, or when distill-session identifies the learning extends an existing skill rather than warranting a new one — e.g. "update SKILL.md", "improve this skill", "extend this skill", "refine this skill", "tighten the skill description", or "this skill didn't trigger".
Picks the right Kubernetes Deployment update strategy (RollingUpdate / Recreate / Blue-Green / Canary) for the situation. Use when configuring a new Deployment, changing rollout config, or deciding how to ship a risky change.
Runs Multica CLI commands by mapping the user's request to the right `multica <command>` invocation. Use when the user asks to do anything with Multica — issues, agents, workspaces, autopilots, skills, squads, or the daemon.
| name | tag |
| description | Tags the current git repository with a new version tag. Use when marking a release point in git history. |
| when_to_use | tag a release, create a git tag, tag this version, add a version tag, mark release |
| argument-hint | [optional tag name, e.g. v1.2.3] |
| model | haiku |
| user-invocable | true |
| context | fork |
Tag the current git repository with a new version tag.
git tag --sort=-version:refname | head -5 to inspect existing tags and determine the tagging pattern.
vX.Y.Z semver, increment the patch version (Z+1) and use that.YY.MM.DD.git tag <new-tag> to create the tag.git tag --sort=-version:refname | head -3.Do not push the tag unless the user explicitly asks.