oncall-lookup
Skill3 starsChanged 5 months agoNo licenceView on GitHub
Look up Temporal Cloud oncall operational knowledge — alert triage, incident patterns, dashboards, commands, gotchas, and component behavior. Use this skill whenever the user asks about: oncall triage or alert handling, PagerDuty alert names or symptoms, Temporal Cloud operational issues (latency, errors, scaling, replication, visibility), what to do when paged, cell/namespace debugging, Astra/WAL/OpenSearch operational behavior, or anything related to running Temporal Cloud in production. Also use when the user mentions specific alert names like "PersistenceLatencySevereFiveMinutes" or symptoms like "shard ownership lost". Even if the user doesn't say "oncall", if their question is about Temporal Cloud operational triage, production incidents, or alert response — use this skill. Triggers: "oncall", "paged", "alert", "triage", "incident", "PagerDuty", "cell health", "shard ownership", "persistence latency", "visibility latency", "ResourceExhausted", "replication lag", "DLQ", "Astra", "WAL", "OpenSearch", "chronicle", "gotcha", "what do I do when", "how to handle", "on-call"
In this repository16 other files it gives its agents.
- canvas-commons-animationsSkill
- code-path-diagramSkill
- code-walkthroughSkill
- d2Skill
- dd-cli-usageSkill
- dialogueSkill
- git-stageSkill
- hyprnoteSkill
- live-transcribeSkill
- microSkill
- prose-styleSkill
- pr-respond-to-commentsSkill
- pr-review-simpleSkill
- pr-reviewSkill
- repro-creatorSkill
- should-gather-dataSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.