Triage Issue Local

Organization

warpdotdev

triage-issue-local

Repo-specific triage guidance for oz-for-oss. Only the categories declared overridable by the core triage-issue skill may be specialized here.

Overview

Publisher	warpdotdev
Repository	`oz-for-oss`
Skill name	`triage-issue-local`
Stars	313
Forks	43
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by warpdotdev on GitHub. Read the source before you install it.

Installation

Install the Triage Issue Local AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git /tmp/oz-for-oss
mkdir -p .claude/skills
cp -r /tmp/oz-for-oss/.agents/skills/triage-issue-local .claude/skills/triage-issue-local

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Triage Issue Local in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Triage Issue Local on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Triage Issue Local is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Repo-specific triage guidance for `oz-for-oss`

This file is a companion to the core triage-issue skill. It does not redefine the triage output schema, safety rules, or follow-up-question contract. It only specializes the override categories the core skill marks as overridable.

Heuristics

Distinguish observed symptoms from reporter hypotheses and proposed fixes.
Before asking any follow-up question, first try to answer it yourself through code inspection, documentation lookup, or web search. Only ask questions that you cannot resolve on your own and that only the reporter would know.
Ask targeted follow-up questions only for details the agent cannot derive itself and that materially improve triage confidence.
Prefer issue-specific questions over generic "please share more info" requests.

Label taxonomy

The label taxonomy for this repository is managed in .github/issue-triage/config.json. Prefer labels from that configuration, and avoid inventing new labels unless the prompt explicitly allows it.

warp:needs-support is a configured label for issues that cannot be resolved through OSS contributions (billing inquiries, plan changes, refund requests, subscription or account management, pricing questions, payment issues). When you triage such a report, request warp:needs-support, set close_issue to true, and direct the reporter to Warp support in statements; the workflow applies the label, posts the support-escalation comment, and closes the issue. Do not use this label or close_issue for issues that can be addressed via OSS contributions.

Recurring follow-up patterns

No repo-specific follow-up patterns have been captured for this repository yet. oz-for-oss is not a terminal or desktop application, so the GPU/driver, window-manager, shell-integration, and similar runtime-environment sub-items that only make sense for those products do not belong here. The weekly update-triage loop will propose additions as maintainer overrides reveal recurring patterns that are actually specific to this repository.

Owner-inference hints

No repo-specific owner-inference hints beyond .github/STAKEHOLDERS have been captured yet.

Frequently asked questions

What does the Triage Issue Local AI skill do?

Repo-specific triage guidance for oz-for-oss. Only the categories declared overridable by the core triage-issue skill may be specialized here.

Why use Triage Issue Local on TypingMind?

Because you install it once and use it with any model. Triage Issue Local is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Triage Issue Local in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Triage Issue Local?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Triage Issue Local?

As many as you like. As long as a model supports skills, you can use Triage Issue Local with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Triage Issue Local AI skill free?

Yes. It is published on GitHub by warpdotdev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Html Ppt Zhangzara Block Frame

nexu-io

OrganizationPopular

Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.

Html Ppt Zhangzara Cartesian

nexu-io

OrganizationPopular

An economics senior thesis on the employment effects of local minimum-wage increases — identification strategy, evidence, and limitations. Built as a decision-grade coursework defense deck for thesis…

Constraint Driven Development

addyosmani

CommunityPopular

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no…

Spec Driven Development

addyosmani

CommunityPopular

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Repo-specific triage guidance for oz-for-oss

Heuristics

Label taxonomy

Recurring follow-up patterns

Owner-inference hints

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

Repo-specific triage guidance for `oz-for-oss`