ops
Skill40 starsChanged 4 months agoMITView on GitHub
Primary router for operations, deployment, incident, and lifecycle workflows. Analyzes intent and dispatches to deploy-checklist, incident-response, standup, status, revert. Use for pre-deploy verification, handling outages, daily summaries, progress checks, and safe rollbacks.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- holon-run/holontheir own version, first seen Nov 8, 2026
- guaardvark/guaardvarktheir own version, first seen Nov 5, 2026
- jthingelstad/elixir-mcptheir own version, first seen Nov 4, 2026
- tandregbg/core-claude-skillstheir own version, first seen Nov 4, 2026
- aya-taleb/biz-ready-skillstheir own version, first seen Nov 1, 2026
- vivekschaudhary/compasstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use design and setup.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkilldesign
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- guaardvark/guaardvark★ 306same name
- holon-run/holon★ 194same name
- tandregbg/core-claude-skills★ 4same name
- vivekschaudhary/compass★ 2same name
- vlting/claude-skills★ 2same name
- aya-taleb/biz-ready-skills★ 1same name
- Frutzmann/claude-code-setup★ 1same name
- harshsinghmp/muse-skills★ 1same name
- HDHNezherParking-cum-Y638-Intl-Ltd/titan★ 1same name
- jircdev/crew-plugin★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- web/llms-full.txtllms.txt
- web/llms.txtllms.txt
- adrSkill
- assist-reviewSkill
- bughuntSkill
- changeSkill
- coverageSkill
- debugSkill
- decomposeSkill
- deep-reviewSkill
- deploy-checklistSkill
- discoverSkill
- docsSkill
- documentationSkill
- draftSkill
- graphSkill
- impactSkill
- implementSkill
- incident-responseSkill
- initSkill
- integrationsSkill
- jiraSkill
- learnSkill
- new-trackSkill
- planSkill
- quick-reviewSkill
- revertSkill
- reviewSkill
- standupSkill
- statusSkill
- tech-debtSkill
- testing-strategySkill
- tourSkill
- uploadSkill
The file
Files
Ops - Operations & Lifecycle Router
/draft:ops groups all operational, deployment, and runtime lifecycle commands.
When to Use
- Preparing a deployment or release
- Responding to incidents or outages
- Generating team standup / activity summaries
- Checking overall project or track status
- Performing git-aware reverts or rollbacks
Routing Logic
Intent keywords drive deterministic dispatch. Multi-intent requests are sequenced (e.g., status then incident).
| User Intent Keywords | Dispatches To | Purpose |
| upload for review, git upload, submit code, open PR | /draft:upload | Pre-upload gate: review, approvals, validators, then push |
| deploy checklist, pre-deploy, release check, readiness | /draft:deploy-checklist | Pre-deployment verification with rollback triggers |
| incident, outage, sev, postmortem, triage | /draft:incident-response | Full incident lifecycle (triage → mitigate → postmortem) |
| standup, daily summary, what did I do, activity report | /draft:standup | Git activity standup summary (read-only) |
| status, progress, what's the state, track overview | /draft:status | Progress overview across tracks and git |
| revert, rollback, undo, git revert, restore | /draft:revert | Git-aware safe rollback of changes or tracks |
Dispatch Examples
User: "run the deploy checklist for the auth track"
→ dispatches to /draft:deploy-checklist [track auth]
User: "we had an outage last night, start postmortem"
→ dispatches to /draft:incident-response postmortem
User: "give me today's standup"
→ dispatches to /draft:standup
User: "what's the current status of the project"
→ dispatches to /draft:status
User: "revert the last two commits on this branch safely"
→ dispatches to /draft:revert
Integration Notes
Ops commands often read draft/tracks.md, draft/*/plan.md, and git metadata. They feed forward into documentation and jira flows when needed.
Direct invocation of the leaf skills continues to work for power users and scripts during the deprecation window.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.