How do I install the Fiftyone Issue Triage skill?

Run npx skillmds@latest add tomevault-io/fiftyone-issue-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fiftyone Issue Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fiftyone Issue Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fiftyone Issue Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fiftyone Issue Triage?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fiftyone Issue Triage by tomevault-io

Name: Fiftyone Issue Triage
Author: tomevault-io

Fiftyone Issue Triage

Triages FiftyOne GitHub issues by categorizing as fixed, won't fix, not reproducible, or still valid. Use when reviewing GitHub issues, triaging bugs, or closing stale issues in the voxel51/fiftyone repository. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

FiftyOne Issue Triage

Category	When to Use
Already Fixed	Resolved in recent commits/releases
Won't Fix	By design, out of scope, or external behavior (browser, OS, third-party)
Not Reproducible	Cannot reproduce with provided info
No Longer Relevant	Outdated version, deprecated feature, or stale (6+ months)
Still Valid	Confirmed bug or valid feature request needing work

Workflow

1. Fetch Issue

gh issue view {number} --repo voxel51/fiftyone --json title,body,author,state,labels,comments

2. Analyze

Extract: issue type, version, reproduction steps, error message
Search related: gh issue list --repo voxel51/fiftyone --state all --search "keyword"
Check git history: git log --oneline --grep="keyword"

3. Assess Responsibility

External behavior (browser, OS, third-party)? → Won't Fix
User workflow/configuration issue? → Won't Fix (with workaround)
FiftyOne code/behavior issue? → Continue assessment

4. Assess Value

Before proposing fixes, ask: "Is a fix worth the effort?"

How many users affected?
Is workaround simple?
Would fix add complexity or hurt performance?

5. Check Documentation

grep -r "keyword" docs/source/ --include="*.rst"

6. Categorize and Respond

Quick Reference

Category	Key Indicator	Action
Already Fixed	Found in git log	Point to PR, suggest upgrade
Won't Fix	External/by design	Explain, provide workaround
Not Reproducible	Can't reproduce	Request more info
No Longer Relevant	Old/stale/deprecated	Explain, suggest new issue
Still Valid	Confirmed, no fix	Document root cause, propose fix

Response Tone

Always start with thanks, be friendly, then explain. Keep responses simple (no internal code details).

If User Willing to Contribute

Contribution guide: https://docs.voxel51.com/contribute/index.html
Discord: https://discord.com/invite/fiftyone-community (#github-contribution channel)
Point to relevant code files for the fix

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: fiftyone-issue-triagedescription: Triages FiftyOne GitHub issues by categorizing as fixed, won't fix, not reproducible, or still valid. Use when reviewing GitHub issues, triaging bugs, or closing stale issues in the voxel51/fiftyone repository. Use when this capability is needed.---# FiftyOne Issue Triage## Categories| Category | When to Use ||----------|-------------|| **Already Fixed** | Resolved in recent commits/releases || **Won't Fix** | By design, out of scope, or external behavior (browser, OS, third-party) || **Not Reproducible** | Cannot reproduce with provided info || **No Longer Relevant** | Outdated version, deprecated feature, or stale (6+ months) || **Still Valid** | Confirmed bug or valid feature request needing work |## Workflow### 1. Fetch Issue```bashgh issue view {number} --repo voxel51/fiftyone --json title,body,author,state,labels,comments```### 2. Analyze- Extract: issue type, version, reproduction steps, error message- Search related: `gh issue list --repo voxel51/fiftyone --state all --search "keyword"`- Check git history: `git log --oneline --grep="keyword"`### 3. Assess Responsibility- External behavior (browser, OS, third-party)? → Won't Fix- User workflow/configuration issue? → Won't Fix (with workaround)- FiftyOne code/behavior issue? → Continue assessment### 4. Assess ValueBefore proposing fixes, ask: "Is a fix worth the effort?"- How many users affected?- Is workaround simple?- Would fix add complexity or hurt performance?### 5. Check Documentation```bashgrep -r "keyword" docs/source/ --include="*.rst"```### 6. Categorize and Respond## Quick Reference| Category | Key Indicator | Action ||----------|---------------|--------|| Already Fixed | Found in git log | Point to PR, suggest upgrade || Won't Fix | External/by design | Explain, provide workaround || Not Reproducible | Can't reproduce | Request more info || No Longer Relevant | Old/stale/deprecated | Explain, suggest new issue || Still Valid | Confirmed, no fix | Document root cause, propose fix |## Response ToneAlways start with thanks, be friendly, then explain. Keep responses simple (no internal code details).## If User Willing to Contribute- **Contribution guide:** https://docs.voxel51.com/contribute/index.html- **Discord:** https://discord.com/invite/fiftyone-community (#github-contribution channel)- Point to relevant code files for the fix---> Converted and distributed by [TomeVault](https://tomevault.io/claim/voxel51) — claim your Tome and manage your conversions.

Frequently asked questions