メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Answers FiftyOne Python SDK questions with accurate, runnable code. Use when the user asks how to do something in the FiftyOne Python SDK, asks a docs question, no skill or operator covers their goal, or the agent is unsure of the correct FiftyOne method, argument, or field path while writing code — e.g. "how do I do X in Python", "show me the SDK for filtering", "there's no operator for this, can I do it in code", "what's the API for embeddings", "write me a Python script to do Y".
Use when driving the FiftyOne App via the Playwright MCP — plugin/operator verification, demo or screencast recording, or any end-to-end UI automation against `fo.launch_app(...)`. Covers the critical "do not navigate after reload_dataset" crash, launcher patterns (remote=True, trigger-file IPC), MUI-specific input/dropdown gotchas, sidebar tag filtering, `data-cy` selectors, dialog scrolling, session refresh strategies, and cleanup. Trigger on mentions of "Playwright + FiftyOne", "automate FiftyOne App", "operator demo", "browser_navigate crash", "reload_dataset", or any FiftyOne session that silently dies after a UI action.
Use when integrating a model into FiftyOne's remote model zoo — detection, classification, segmentation, embedding, keypoint, or vision-language (VLM) models loaded via `register_zoo_model_source` and `load_zoo_model`, then applied with `dataset.apply_model`. Also for debugging zoo registration, `manifest.json` issues, custom `fom.Model` / `TorchModelMixin` subclasses, DataLoader pickle errors, or worker `ModuleNotFoundError` from spawned DataLoader workers.
Develops custom FiftyOne plugins (operators and panels) from scratch. Use when creating plugins, extending FiftyOne with custom operators, building interactive panels, or integrating external APIs.
Imports datasets into FiftyOne with automatic format detection. Supports all media types (images, videos, point clouds), label formats (COCO, YOLO, VOC, KITTI), multimodal grouped datasets, and Hugging Face Hub datasets. Use when importing datasets from local files or Hugging Face, loading autonomous driving data, or creating grouped datasets.
End-to-end dataset curation for FiftyOne: inspect schema and quality, audit annotations, analyze class distributions, explore embeddings, find duplicates, create curated subsets, and build train/val/test splits. Works with any computer vision dataset type.
| name | fiftyone-issue-triage |
| description | 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. |
| 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 |
gh issue view {number} --repo voxel51/fiftyone --json title,body,author,state,labels,comments
gh issue list --repo voxel51/fiftyone --state all --search "keyword"git log --oneline --grep="keyword"Before proposing fixes, ask: "Is a fix worth the effort?"
grep -r "keyword" docs/source/ --include="*.rst"
| 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 |
Always start with thanks, be friendly, then explain. Keep responses simple (no internal code details).