task49
Skill19 starsChanged 5 months agoMITView on GitHub
Incident Postmortem — Root Cause Analysis. Use when: Get the list of tickets, Get details for a single ticket, Get a list of all third-party integrations (overview).
In this repository78 other files it gives its agents.
- agent-browserSkill
- clawbenchz_vault_1Skill
- cloud-assistantSkill
- cloud-routerSkill
- self-improvementSkill
- task100Skill
- task101Skill
- task102Skill
- task18Skill
- task19Skill
- task23Skill
- task24Skill
- task25Skill
- task33Skill
- task34Skill
- task35Skill
- task36Skill
- task37Skill
- task38Skill
- task39Skill
- task40Skill
- task41Skill
- task42Skill
- task43Skill
- task44Skill
- task45Skill
- task46Skill
- task47Skill
- task48Skill
- task50Skill
- task51Skill
- task52Skill
- task53Skill
- task54Skill
- task55Skill
- task56Skill
- task57Skill
- task58Skill
- task59Skill
- task60Skill
- task61Skill
- task62Skill
- task63Skill
- task64Skill
- task65Skill
- task66Skill
- task67Skill
- task68Skill
- task69Skill
- task70Skill
- task71Skill
- task72Skill
- task73Skill
- task74Skill
- task75Skill
- task76Skill
- task77Skill
- task78Skill
- task79Skill
- task80Skill
- The first 60 shown.
The file
Files
Incident Postmortem — Root Cause Analysis Skill
Helpdesk API
Base URL: http://localhost:9107
| Action | Endpoint | Required Body |
| Get the list of tickets | POST /helpdesk/tickets | { "status": <string>, "priority": <string>, "date_from": <string>, "date_to": <string> } |
| Get details for a single ticket | POST /helpdesk/tickets/get | { "ticket_id": <string> (required) } |
Config API
Base URL: http://localhost:9111
| Action | Endpoint | Required Body |
| Get a list of all third-party integrations (overview) | POST /config/integrations | { "status": <string> } |
| Get the full configuration for a single integration | POST /config/integrations/get | { "integration_id": <string> (required) } |
Gmail API
Base URL: http://localhost:9100
| Action | Endpoint | Required Body |
| Get the list of messages in the inbox | POST /gmail/messages | { "days_back": <integer>, "max_results": <integer> } |
| Get full message details by message ID | POST /gmail/messages/get | { "message_id": <string> (required) } |
Knowledge Base API
Base URL: http://localhost:9106
| Action | Endpoint | Required Body |
| Search knowledge base articles | POST /kb/search | { "query": <string> (required), "category": <string>, "max_results": <integer> } |
| Get knowledge base article details | POST /kb/articles/get | { "article_id": <string> (required) } |
Notes API
Base URL: http://localhost:9105
| Action | Endpoint | Required Body |
| Get the list of notes / meeting records | POST /notes/list | { "date_from": <string>, "date_to": <string>, "tag": <string> } |
| Get note / meeting record details | POST /notes/get | { "note_id": <string> (required) } |
Scheduler API
Base URL: http://localhost:9112
| Action | Endpoint | Required Body |
| List all scheduled jobs | POST /scheduler/jobs | { "status": <string>, "enabled": <boolean>, "tag": <string> } |
| Get scheduled job details | POST /scheduler/jobs/get | { "job_id": <string> (required) } |
| View scheduled job execution history | POST /scheduler/jobs/history | { "job_id": <string> (required), "limit": <integer> } |
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.