Archive Analysis
ai-analyst-lab/ai-analyst
Save completed analyses to the knowledge system's analysis archive for future reference.
Read and record root causes in the Linear incident-alert knowledge base.
Install Incident Alert Tickets
$ npx skills add langfuse/langfuse --skill incident-alert-tickets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install langfuse/langfuse incident-alert-tickets --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/incident-alert-tickets .claude/skills/incident-alert-tickets && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "incident-alert-tickets" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/incident-alert-tickets into .claude/skills/incident-alert-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-alert-tickets", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/langfuse/langfuse/tree/main/.agents/skills/incident-alert-ticketsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add langfuse/langfuse --skill incident-alert-tickets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install langfuse/langfuse incident-alert-tickets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/incident-alert-tickets .agents/skills/incident-alert-tickets && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "incident-alert-tickets" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/incident-alert-tickets into .agents/skills/incident-alert-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-alert-tickets", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langfuse/langfuse --skill incident-alert-tickets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install langfuse/langfuse incident-alert-tickets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/incident-alert-tickets .cursor/skills/incident-alert-tickets && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "incident-alert-tickets" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/incident-alert-tickets into .cursor/skills/incident-alert-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-alert-tickets", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/langfuse/langfuse.git --path .agents/skills/incident-alert-tickets--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add langfuse/langfuse --skill incident-alert-tickets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install langfuse/langfuse incident-alert-tickets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/incident-alert-tickets .gemini/skills/incident-alert-tickets && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "incident-alert-tickets" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/incident-alert-tickets into .gemini/skills/incident-alert-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-alert-tickets", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install langfuse/langfuse incident-alert-ticketsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add langfuse/langfuse --skill incident-alert-tickets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/incident-alert-tickets .github/skills/incident-alert-tickets && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "incident-alert-tickets" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/incident-alert-tickets into .github/skills/incident-alert-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-alert-tickets", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langfuse/langfuse --skill incident-alert-tickets -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install langfuse/langfuse incident-alert-tickets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/incident-alert-tickets .opencode/skills/incident-alert-tickets && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "incident-alert-tickets" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/incident-alert-tickets into .opencode/skills/incident-alert-tickets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-alert-tickets", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
incident-alert-tickets- GitHub stars
- 36k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 847 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Read and record root causes in the Linear incident-alert knowledge base.
- Works in 3 steps: List Linear issues carrying the… → Match on monitor ID first (tickets carry… → Read the matched ticket's cause sections…
- Tasks that involve Root cause analysis
- SKILL.md covers When to Apply, Ticket Contract, Lookup and Compare and Classify, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Incident Alert Tickets is an agent skill from langfuse/langfuse. Read and record root causes in the Linear incident-alert knowledge base. Use before and after investigating a named Datadog monitor, incident.io alert or incident, or on-call page to find or record root causes.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering Root cause analysis, Incident response and Knowledge bases. It works with Datadog. The repository describes itself as: 🪢 Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.
When your agent uses it
- Tasks that involve Root cause analysis
- Tasks that involve Incident response
- Tasks that involve Knowledge bases
Example prompts
- “/incident-alert-tickets”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- List Linear issues carrying the incident-alert label.
- Match on monitor ID first (tickets carry it in the alert header), then on
- Read the matched ticket's cause sections and comments.
What it can do on your machine
Read from SKILL.md and the folder at commit cb2ceba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Incident Alert Tickets loads about 1.6k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 847 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 847 words (~1,563 tokens).
“Incident-alert tickets turn on-call debugging into searchable knowledge: one Linear ticket per production alert/monitor, one dated section per distinct root cause. This skill owns lookup, comparison, and the human-gated write-back; calling skills own the investigation itself. The team SOP is…”
- name
- incident-alert-tickets
Files
Just SKILL.md in .agents/skills/incident-alert-tickets of langfuse/langfuse.
Open the folder on GitHubat commit cb2ceba
Compare with similar skills
Incident Alert Tickets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Incident Alert Tickets this skilllangfuse/langfuse | 36k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Archive Analysisai-analyst-lab/ai-analyst | 304 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Incident Triage Harnessmadebyaris/advance-minimax-m3-cursor-rules | 126 | — | ~984 | Automated safety check: Pass | MIT | |
| Broken API InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Playbook Lookuppapadopouloskyriakos/agentic-chatops | 107 | — | ~363 | Automated safety check: Notes | None | |
| Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan | 109 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Incident Triage Harness
madebyaris/advance-minimax-m3-cursor-rules
Walks an agent through an evidence-first incident investigation across logs, metrics, code and screenshots, from first symptom to the smallest safe mitigation.
Broken API Interviewer
PrepLabsAI/InterviewMentor
An on-call SRE interviewer who just got paged about a broken checkout API.
Playbook Lookup
papadopouloskyriakos/agentic-chatops
Query past incident resolutions from the knowledge base. An agent skill from papadopouloskyriakos/agentic-chatops.
Post-Incident Debrief
VeryGoodOpenSource/vgv-wingspan
Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.
Root-Cause Troubleshooting
davidYichengWei/agentic-engineering-framework
Diagnoses compile errors, runtime exceptions, failing tests, pipeline failures and production alerts from code and logs, giving a root cause before any fix.
More from langfuse/langfuse
All 33 skills in this repoLinear Context Handover
langfuse/langfuse
Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it.
Add Model Price
langfuse/langfuse
A skill your agent uses when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI…
Backend Dev Guidelines
langfuse/langfuse
Build or review Langfuse backend code. An agent skill from langfuse/langfuse.
Langfuse Codebase Navigator
langfuse/langfuse
Navigate Langfuse repositories, code areas, and agent skills.
Refactor React Effects
langfuse/langfuse
Refactor avoidable React useEffect usage in Langfuse frontend code.
Add To Dependabot CSV
langfuse/langfuse
Append GitHub Dependabot or Snyk/code-scanning alerts to an existing vulnerability CSV after verifying their API metadata.
Related
Works with
Questions about Incident Alert Tickets
What does Incident Alert Tickets do?
Read and record root causes in the Linear incident-alert knowledge base. Incident Alert Tickets is an agent skill from langfuse/langfuse. Read and record root causes in the Linear incident-alert knowledge base.
When should I use Incident Alert Tickets?
Incident Alert Tickets fits situations like: tasks that involve Root cause analysis; tasks that involve Incident response; tasks that involve Knowledge bases.
How do I install Incident Alert Tickets in Claude Code?
Run `npx skills add langfuse/langfuse --skill incident-alert-tickets -a claude-code`. Or copy the skill folder (.agents/skills/incident-alert-tickets in langfuse/langfuse) into .claude/skills/incident-alert-tickets in your project. Claude Code loads it when a task matches its description.
How do I install Incident Alert Tickets in Codex?
Run `npx skills add langfuse/langfuse --skill incident-alert-tickets -a codex`. Or copy the skill folder (.agents/skills/incident-alert-tickets in langfuse/langfuse) into .agents/skills/incident-alert-tickets in your project. Codex loads it when a task matches its description.
Can I use Incident Alert Tickets in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add langfuse/langfuse --skill incident-alert-tickets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-alert-tickets, .gemini/skills/incident-alert-tickets, .github/skills/incident-alert-tickets and .opencode/skills/incident-alert-tickets in your project.
What does Incident Alert Tickets need to run?
SKILL.md names no scripts, command-line tools or credentials: Incident Alert Tickets is instructions for the agent only.
Does Incident Alert Tickets access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Incident Alert Tickets safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Incident Alert Tickets use?
Incident Alert Tickets has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Incident Alert Tickets use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Incident Alert Tickets?
Skills that share tags, products or a category with Incident Alert Tickets: Archive Analysis (ai-analyst-lab/ai-analyst, 304 stars), Incident Triage Harness (madebyaris/advance-minimax-m3-cursor-rules, 126 stars), Broken API Interviewer (PrepLabsAI/InterviewMentor, 112 stars) and Playbook Lookup (papadopouloskyriakos/agentic-chatops, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Incident Alert Tickets?
langfuse (a GitHub organization) maintains it in langfuse/langfuse, which has 35,626 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 11, 2026.
Source: langfuse/langfuse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.