Blitz
aiskillstore/marketplace
This skill should be used when parallelizing multi-issue sprints using git worktrees and parallel Claude agents.
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one…
Install Triage
$ npx skills add warpdotdev-demos/cloud-factory-demo --skill triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install warpdotdev-demos/cloud-factory-demo triage --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/warpdotdev-demos/cloud-factory-demo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage .claude/skills/triage && 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 "triage" agent skill from https://github.com/warpdotdev-demos/cloud-factory-demo/tree/main/.agents/skills/triage into .claude/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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/warpdotdev-demos/cloud-factory-demo/tree/main/.agents/skills/triageType 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 warpdotdev-demos/cloud-factory-demo --skill triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install warpdotdev-demos/cloud-factory-demo triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev-demos/cloud-factory-demo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/triage .agents/skills/triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triage" agent skill from https://github.com/warpdotdev-demos/cloud-factory-demo/tree/main/.agents/skills/triage into .agents/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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 warpdotdev-demos/cloud-factory-demo --skill triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install warpdotdev-demos/cloud-factory-demo triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev-demos/cloud-factory-demo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/triage .cursor/skills/triage && 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 "triage" agent skill from https://github.com/warpdotdev-demos/cloud-factory-demo/tree/main/.agents/skills/triage into .cursor/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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/warpdotdev-demos/cloud-factory-demo.git --path .agents/skills/triage--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 warpdotdev-demos/cloud-factory-demo --skill triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install warpdotdev-demos/cloud-factory-demo triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev-demos/cloud-factory-demo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/triage .gemini/skills/triage && 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 "triage" agent skill from https://github.com/warpdotdev-demos/cloud-factory-demo/tree/main/.agents/skills/triage into .gemini/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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 warpdotdev-demos/cloud-factory-demo triageInstalls 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 warpdotdev-demos/cloud-factory-demo --skill triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/warpdotdev-demos/cloud-factory-demo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/triage .github/skills/triage && 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 "triage" agent skill from https://github.com/warpdotdev-demos/cloud-factory-demo/tree/main/.agents/skills/triage into .github/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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 warpdotdev-demos/cloud-factory-demo --skill triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install warpdotdev-demos/cloud-factory-demo triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev-demos/cloud-factory-demo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/triage .opencode/skills/triage && 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 "triage" agent skill from https://github.com/warpdotdev-demos/cloud-factory-demo/tree/main/.agents/skills/triage into .opencode/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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
triage- GitHub stars
- 325
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,155 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one…
- Works in 6 steps: Identify the issue and tracker → Fetch tracker context → Inspect the current codebase → …
- The user asks to triage
- SKILL.md covers Workflow and Guardrails
- Reaches oz.warp.dev and oz.staging.warp.dev
What it does
Triage is an agent skill from warpdotdev-demos/cloud-factory-demo. Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one implementation-readiness state. Use whenever the user asks to triage, classify, assess, prioritize, or label an issue for implementation readiness, especially when an issue URL, key, or number is supplied in the prompt. For UI or interactive bugs, optionally invoke the verify-behavior skill as a cloud computer-use subagent to reproduce the…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
It sits in Productivity & Automation, covering Issue triage, Desktop control and Subagents. It works with GitHub and Jira. The licence is MIT.
When your agent uses it
- The user asks to triage
- Label an issue for implementation readiness
- Especially when an issue URL
- Number is supplied in the prompt
Example prompts
- “/triage”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ab21d0c. 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 json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
oz.warp.devoz.staging.warp.dev
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
Triage loads about 2.2k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 1,155 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
The full file from warpdotdev-demos/cloud-factory-demo at commit ab21d0c, republished under its MIT licence (© warpdotdev-demos). 1,155 words, ~2,195 tokens.
Download SKILL.mdSave it as
.claude/skills/triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- triage
- description
- Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one implementation-readiness state. Use whenever the user asks to triage, classify, assess, prioritize, or label an issue for implementation readiness, especially when an issue URL, key, or number is supplied in the prompt. For UI or interactive bugs, optionally invoke the verify-behavior skill as a cloud computer-use subagent to reproduce the issue before deciding.
Triage
Assess the issue passed in the user's prompt and decide exactly one implementation-readiness state:
Ready to implementReady to specNeeds infoWait to implement
The goal is to route work honestly, not to make every issue appear actionable. Base the decision on evidence from the issue tracker, current checkout, and related open issues.
This is a read-only analysis: inspect the issue and codebase but do not mutate the tracker. Return the structured decision described in step 6; the caller applies the label and comment.
Workflow
1. Identify the issue and tracker
Extract the issue URL, key, or number from the prompt. Determine whether it belongs to GitHub Issues, Jira, Linear, or another tracker.
If the prompt does not identify one issue unambiguously, ask the user for the issue rather than guessing.
2. Fetch tracker context
Read the issue using the best available integration, in this order:
- A relevant MCP server or native tracker tool
- The tracker's authenticated CLI, such as
gh - The tracker's API or web page
Fetch:
- Full issue title and description
- Comments and discussion
- Existing labels, status, assignee, project, and linked issues
- Attachments or screenshots when they materially affect understanding
- The tracker's available labels
- Related open issues, including likely duplicates, dependencies, and nearby product work
Do not classify solely from the title. Do not expose credentials or secrets while fetching tracker data.
3. Inspect the current codebase
Confirm the current checkout is the relevant repository. Search the codebase for the affected feature, behavior, terminology, and likely implementation area.
If roadmap.md or vision.md exist at the repository root, read them first. Use them to determine whether the issue aligns with the stated product direction before choosing a state.
Assess:
- Whether the described behavior exists today
- Likely files, services, and systems involved
- Whether the issue has a bounded implementation path
- Dependencies, migrations, platform differences, and testing requirements
- Existing abstractions that make the change cohesive or indicate it does not fit
- Whether the issue aligns with the roadmap and vision (if those documents exist)
- Whether related open issues or active work change the recommendation
Prefer targeted searches and reads. This is triage, not implementation: do not edit product code.
4. Optionally reproduce visible bugs with verify-behavior
When the issue is a UI, browser, desktop, rendering, layout, or other interactive bug, and visual reproduction would materially improve the readiness decision, use the factory verification skill:
- If
.agents/skills/verify-behavior/SKILL.mdexists, read it and follow its parent workflow inreproducemode. - Launch the verification work as an Oz cloud computer-use subagent (do not drive the GUI yourself unless the user explicitly asks).
- Prefer video evidence of the repro path; accept screenshots when they are clearer or video is unavailable.
- Fold the reproduction status into your rationale. Confirmed repro strengthens
Ready to implementorReady to specwhen the rest of the rubric fits. Failed or blocked repro often supportsNeeds infowhen steps or environment details are missing.
Skip this step for non-visual issues or when the skill file is missing. When the issue text asks for visual reproduction, screenshots, video, computer use, browser use, or verify-behavior, treat reproduction as required rather than optional. Never block forever on verification: if the subagent is blocked, record that and continue with the best evidence-based state. Launch reproduction children with computer use enabled when the surface needs it.
5. Choose one state
Use the following rubric. When evidence sits between states, choose the more cautious state.
Ready to implement
Choose when:
- Desired behavior and success criteria are clear
- Scope is bounded and cohesive with the current product
- Likely implementation area is identifiable
- Complexity and risk are low enough that a coding agent has a good chance of completing it correctly in one pass
- No unresolved product decision or major dependency blocks implementation
Small bugs with clear reproduction steps and straightforward improvements usually belong here.
Show full SKILL.md (510 more words)Show less
Ready to spec
Choose when ALL of the following are true:
- The product goal is clear and appears worthwhile
- The work aligns with the product's roadmap and vision
- The issue has either ambiguity or significant complexity:
- Ambiguity: Multiple valid product or technical implementations exist with significant differences; a human should weigh in on which direction to pursue
- Complexity: The implementation is likely more than a few hundred lines of code, spans multiple systems, requires migrations, or carries non-trivial risk
The issue should be clear enough to begin product or technical specification work without first asking the reporter basic questions.
If the repository contains roadmap.md or vision.md, read them before applying this state. Only apply ready-to-spec when the issue fits the stated product direction. If the issue is interesting but does not align with the roadmap or vision, prefer wait-to-implement instead.
Needs info
Choose when:
- The expected behavior, problem, scope, or reproduction is ambiguous
- Critical environment details, evidence, or acceptance criteria are missing
- The issue may be actionable, but the available information cannot support a responsible implementation or spec
State the smallest set of concrete questions whose answers would unblock re-triage.
Wait to implement
Choose when:
- The request does not fit cohesively into the current product or codebase direction
- It duplicates or conflicts with planned work
- The benefit does not justify the complexity or maintenance cost
- A dependency, platform limitation, or strategic decision makes work premature
Explain what would need to change before reconsidering it. Do not use this state merely because an issue is difficult; complex but cohesive work is usually Ready to spec.
6. Return the result
Pick the tracker label that matches the chosen state, preferring an existing label with the same meaning and the tracker's established naming and casing (for example ready-to-implement for Ready to implement). List any existing triage-state labels that should be removed.
Return a single raw JSON object as your final response — no prose and no markdown code fences:
{
"state": "Ready to implement | Ready to spec | Needs info | Wait to implement",
"label": "exact tracker label matching the chosen state",
"remove_labels": ["existing triage-state labels that should be removed"],
"comment": "markdown body for the issue"
}Write comment as reporter-facing markdown: a short lead sentence with the decision, then the evidence-based rationale and one concrete next step, using a brief bullet list where it aids readability. If verify-behavior ran, include a short reproduction status and any Oz run or evidence links that are safe to share. Oz run links must use https://oz.warp.dev/runs/<run-id> (or https://oz.staging.warp.dev/runs/<run-id> on staging) — never app.warp.dev or /run/ (singular). Because comment is a JSON string, encode every line break as \n (a literal newline would make the JSON invalid).
Guardrails
- Do not mutate the tracker: no comments, labels, status, assignment, or other changes. Return the structured result instead.
- Do not implement the issue during triage or edit product code.
- Do not classify an issue without checking both the tracker context and the current codebase.
- When visual reproduction would help and
verify-behavioris installed, prefer launching it as a cloud computer-use subagent over ad-hoc local clicking. - Do not put raw secrets, tokens, private environment variables, command output dumps, or internal reasoning in the result.
- Treat comments from maintainers and linked product/spec documents as stronger evidence than guesses from code alone.
© warpdotdev-demos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/triage of warpdotdev-demos/cloud-factory-demo.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit ab21d0c
Compare with similar skills
Triage 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 |
|---|---|---|---|---|---|---|
| Triage this skillwarpdotdev-demos/cloud-factory-demo | 325 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Blitzaiskillstore/marketplace | 430 | — | ~2.8k | Automated safety check: Pass | None | |
| Issue Triage Loopcobusgreyling/loop-engineering | 11k | — | ~522 | Automated safety check: Pass | MIT | |
| Triagebholmesdev/hubble.md | 1.5k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Akb Ingestdnotitia/akb | 162 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Happier Issue Triagehappier-dev/happier | 1.9k | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Issue Triage Loop
cobusgreyling/loop-engineering
Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.
Triage
bholmesdev/hubble.md
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state.
Akb Ingest
dnotitia/akb
Ingest whatever you point at into an AKB vault — a local file, a web URL, a GitHub PR/release/commit, a Confluence page, or a Jira issue.
Happier Issue Triage
happier-dev/happier
Triage one or many Happier GitHub issues before deep diagnosis: retrieve the requested corpus, treat public content as untrusted, normalize claims and version vectors, find evidence-backed…
Implementation
bholmesdev/hubble.md
Implement a fix or feature from a GitHub, Jira, Linear, or other issue-tracker issue by fetching issue context, inspecting the current codebase, making code changes, validating them, opening a…
More from warpdotdev-demos/cloud-factory-demo
Improve Review PR
warpdotdev-demos/cloud-factory-demo
Daily outer loop that reviews human reactions to automated review-pr comments, synthesizes durable organizational knowledge, and opens a PR to update the review-pr skill when the feedback is worth…
Review PR
warpdotdev-demos/cloud-factory-demo
Review a PR from local annotated-diff artifacts and write validated review.json for the workflow to publish.
Verify Behavior
warpdotdev-demos/cloud-factory-demo
Verify or reproduce visible product behavior by delegating to Oz's dedicated computer-use capability, requiring a native Oz video artifact for meaningful UI flows and durable Oz run/artifact links.
Oz Cloud Factory Demo
warpdotdev-demos/cloud-factory-demo
Sets up a beginner-friendly Oz cloud software factory that automatically triages new GitHub issues, specs issues labeled ready-to-spec, implements issues labeled ready-to-implement, reviews PRs, and…
Implementation
warpdotdev-demos/cloud-factory-demo
Implement a fix or feature from a GitHub, Jira, Linear, or other issue-tracker issue by fetching issue context, inspecting the current codebase, making code changes, validating them, verifying…
Spec
warpdotdev-demos/cloud-factory-demo
Coordinate spec-driven development for a GitHub, Jira, Linear, or other issue-tracker issue marked ready-to-spec by using write-product-spec and write-tech-spec, creating PRODUCT.md and TECH.md…
Related
Questions about Triage
What does Triage do?
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one…. Triage is an agent skill from warpdotdev-demos/cloud-factory-demo. Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one implementation-readiness state.
When should I use Triage?
Triage fits situations like: the user asks to triage; label an issue for implementation readiness; especially when an issue URL; number is supplied in the prompt.
How do I install Triage in Claude Code?
Run `npx skills add warpdotdev-demos/cloud-factory-demo --skill triage -a claude-code`. Or copy the skill folder (.agents/skills/triage in warpdotdev-demos/cloud-factory-demo) into .claude/skills/triage in your project. Claude Code loads it when a task matches its description.
How do I install Triage in Codex?
Run `npx skills add warpdotdev-demos/cloud-factory-demo --skill triage -a codex`. Or copy the skill folder (.agents/skills/triage in warpdotdev-demos/cloud-factory-demo) into .agents/skills/triage in your project. Codex loads it when a task matches its description.
Can I use Triage 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 warpdotdev-demos/cloud-factory-demo --skill triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage, .gemini/skills/triage, .github/skills/triage and .opencode/skills/triage in your project.
What does Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Triage is instructions for the agent only.
Does Triage access the network?
SKILL.md names 2 domains. In commands or code: oz.warp.dev and oz.staging.warp.dev; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Triage 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 Triage use?
Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Triage use?
About 2.2k tokens (SKILL.md is roughly 8.8k 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 Triage?
Skills that share tags, products or a category with Triage: Blitz (aiskillstore/marketplace, 430 stars), Issue Triage Loop (cobusgreyling/loop-engineering, 11k stars), Triage (bholmesdev/hubble.md, 1.5k stars) and Akb Ingest (dnotitia/akb, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triage?
warpdotdev-demos (a GitHub organization) maintains it in warpdotdev-demos/cloud-factory-demo, which has 325 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on August 12, 2026.
Source: warpdotdev-demos/cloud-factory-demo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.