Agent skill · Audited from source

github-bug-report-triage

skill · warpdotdev/oz-skillsMIT licenceAudited 21 Oct 2026 · source 3bd75ba5a136

★ 822pushed 66 days ago
✓SAFEGrade B · 89/100 · 21 Oct 2026 · 3bd75ba
822repo stars · whole warpdotdev/oz-skills

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 3bd75ba5a136 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “github-bug-report-triage (warpdotdev/oz-skills)”. Retrieved 21 Oct 2026. https://modelsatlas.com/skills/warpdotdev/github-bug-report-triage

Trust audit

Audit 0.4.1 · source read 21 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 3bd75ba5a136 · 21 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherwarpdotdev GitHub organizationOwner of the repository this skill is read from
  • Source folderwarpdotdev/oz-skills/.agents/skills/github-bug-report-triageThe exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdict3bd75ba5a136A new audit runs when the source changes
  • Repository statusNot archivedLast push 66 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.

---
name: github-bug-report-triage
description: Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.
license: MIT
---

# GitHub Bug Report Triage

Evaluate GitHub issues for bug reports only. Determine if they contain sufficient info to be actionable. If not, identify missing details and provide constructive feedback.

## Workflow

### 1. Locate Issue Template

**Check for existing templates:**
- `.github/ISSUE_TEMPLATE/bug_report.md`
- `.github/ISSUE_TEMPLATE/bug_report.yml`
- `.github/ISSUE_TEMPLATE/*.md`
- `.github/ISSUE_TEMPLATE.md`
- `ISSUE_TEMPLATE.md`

**If no template exists**, use `references/ISSUE_TEMPLATE.md` from this skill as the fallback template, then evaluate the issue against it.


### 2. Evaluate Issue Quality

**Critical questions:**

1. **Is this a bug report?**
   - If the issue is a feature request or a question, do not evaluate this issue

2. **Is the description clear?**
   - What's broken or wrong
   - Expected behavior vs. what actually happens
   - Impact or severity

3. **Can we reproduce it?**
   - Step-by-step reproduction
   - OR sandbox/StackBlitz/CodeSandbox link
   - OR minimal code example

**Be reasonable:**
- Don't require every template field to be filled
- Focus on minimum info needed to investigate
- Consider context (obvious bugs vs. edge cases)

### 3. Make Determination

**Ready to be actionable:**
- Has clear problem description
- Includes reproduction path OR enough context to debug
- Actually a bug (not feature/question)

**Needs more info:**
- Vague description ("it doesn't work")
- Missing reproduction steps AND no code example
- Unclear what the expected behavior should be
- Missing critical context (e.g., "crashes" but no error message)

### 4. Provide Feedback

**If ready:** Confirm issue is actionable.

**If needs info:** Specify what's missing. Be constructive and specific.

## Examples

### Example 1: Ready to Investigate

```markdown
**Issue**: Dropdown menu doesn't close on mobile Safari

**Description**: 
When clicking a dropdown menu item on iOS Safari, the menu stays 
open instead of closing. Works fine on desktop Chrome/Firefox.

**Steps**:
1. Visit https://stackblitz.com/edit/my-repro
2. Open on iOS Safari
3. Click dropdown, select any item
4. Menu stays open (should close)

**Environment**: iOS 16.3, Safari
```

**Evaluation**: ✅ Ready
- Clear description
- Has reproduction link
- Specific environment details

### Example 2: Needs More Info

```markdown
**Issue**: Button is broken

**Description**: 
The submit button doesn't work properly.
```

**Evaluation**: ❌ Needs info
**Missing**:
- What does "doesn't work" mean? (no click? error? wrong behavior?)
- Expected vs. actual behavior
- Steps to reproduce
- Any error messages

### Example 3: Edge Case - Reasonable

```markdown
**Issue**: Console error on form submit

**Description**:
Getting "Cannot read property 'value' of null" when submitting 
the contact form. Happens 100% of the time.

**Error**:
```
TypeError: Cannot read property 'value' of null
  at handleSubmit (ContactForm.tsx:45)
```

**Environment**: Chrome 120, Windows 11
```

**Evaluation**: ✅ Ready
- Clear error message with stack trace
- Specific file/line reference
- Reproducible (100% of time)
- **Note**: No explicit repro steps, but error is clear enough to investigate

### Example 4: Bug Report with Insufficient Reproducibility

```markdown
**Issue**: [glob-loader] Duplicate id warning on file update

**Description**:
I'm encountering an issue with the glob loader. Whenever I update 
the watched file, I get a warning message in the logs.


The warning message:
```
13:23:31 [WARN] [glob-loader] Duplicate id "russian-test" found in 
/Users/user/Code/project/content/posts/russian-test.md. Later items 
with the same id will overwrite earlier ones.
```

**Expected**: No warning message

**Link to Minimal Reproducible Example**: - N/A
```

**Evaluation**: ❌ Needs info
- Describes a real bug (warning message)
- Has error output and code reference
- BUT: No minimal reproduction provided
- Code link points to private repo (can't access to debug)

**Missing**:
- Minimal reproduction (example code or link to a working reproduction)

Excerpt, first 4,285 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 3bd75ba

Download folder ↗
git clone https://github.com/warpdotdev/oz-skills
git -C oz-skills checkout 3bd75ba5a136

The author documents no install command, so this uses the repository directly. Our verdict covers commit 3bd75ba5a136 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 3bd75ba5a136

Similar skills

Questions about github-bug-report-triage

Is github-bug-report-triage safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can github-bug-report-triage access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (3bd75ba5a136), read on 2026-10-21. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.