Skills fiftyone-pr-triage

📦

fiftyone-pr-triage

Name: fiftyone-pr-triage
Author: AdonaiVera

Content revision r1 Safe ⚙️ External commands

Triage FiftyOne Issues

Maintainers often need consistent issue triage across reports, comments, and code evidence. This skill provides a focused workflow and response templates for FiftyOne GitHub issues.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "fiftyone-pr-triage" from https://skillstore.io/skills/adonaivera-fiftyone-pr-triage.md and its manifest at https://skillstore.io/api/skills/adonaivera-fiftyone-pr-triage/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/adonaivera-fiftyone-pr-triage.md Signed manifest GET /api/skills/adonaivera-fiftyone-pr-triage/manifest Signed lockfile GET /api/skills/adonaivera-fiftyone-pr-triage/lockfile

Test it

Using "fiftyone-pr-triage". A reporter describes a bug from an old FiftyOne version, and the affected feature was later removed.

Expected outcome:

Category: No Longer Relevant. The response explains the version gap, mentions the removed feature, and asks for a new issue if current versions fail.

Using "fiftyone-pr-triage". A bug report includes clear reproduction steps, and no related fix appears in recent history.

Expected outcome:

Category: Still Valid. The response confirms the behavior, summarizes the root cause, and lists the next investigation or fix step.

Using "fiftyone-pr-triage". A maintainer finds a merged pull request that fixed the same traceback.

Expected outcome:

Category: Already Fixed. The response points to the fix, suggests upgrading, and asks the reporter to confirm the result.

Security Audit

Safe

v8 • 7/5/2026 Open versioned report

Static alerts are caused by Markdown fences, inline code formatting, and documented local investigation commands. I found no prompt injection, data exfiltration, credential access, obfuscated code, or unauthorized execution intent in SKILL.md.

Files scanned

241

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/adonaivera-fiftyone-pr-triage/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/adonaivera-fiftyone-pr-triage/security.svg)](https://skillstore.io/skills/adonaivera-fiftyone-pr-triage?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/adonaivera-fiftyone-pr-triage?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/adonaivera-fiftyone-pr-triage/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/adonaivera-fiftyone-pr-triage.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

AdonaiVera. (2026). fiftyone-pr-triage security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/adonaivera-fiftyone-pr-triage/audits/8

BibTeX citation

@techreport{adonaivera-adonaivera-fiftyone-pr-triage-2026,
  author = {AdonaiVera},
  title = {fiftyone-pr-triage security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/adonaivera-fiftyone-pr-triage/audits/8},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "fiftyone-pr-triage security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "AdonaiVera"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/adonaivera-fiftyone-pr-triage/audits/8"
identifiers:
  - type: other
    value: "skillstore:adonaivera-fiftyone-pr-triage:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Reduce Maintainer Backlog

Apply consistent categories and response templates when processing older FiftyOne issues.

Validate Bug Reports

Check code references, recent commits, and reproduction evidence before deciding whether a bug is still valid.

Draft Support Responses

Create clear issue replies that explain the decision, evidence, and next action for the reporter.

Try These Prompts

Classify One Issue

Read this FiftyOne issue summary and classify it using the five triage categories. Explain the evidence and draft a short response.

Check For Prior Fixes

Use the workflow to compare this issue with recent commits and closed issues. Decide if it is already fixed or still valid.

Prepare Maintainer Reply

Based on this investigation summary, choose the best category and write a maintainer reply with evidence, next steps, and respectful tone.

Audit A Backlog Batch

Triage these related FiftyOne issues as a batch. Group duplicates, identify stale reports, flag still valid bugs, and propose closure comments.

Best Practices

Verify issue details, comments, and reported FiftyOne version before assigning a category.
Use repository evidence, linked pull requests, and reproduction results to support each response.
Keep replies concise, respectful, and clear about next steps for the reporter.

Avoid

Close an issue only because it is old.
Claim a fix without evidence from commits, releases, or related issues.
Run command examples against untrusted repositories without reviewing the command and environment.

Frequently Asked Questions

What does this skill help triage?

It helps classify and respond to FiftyOne GitHub issues using a structured maintainer workflow.

Does it run GitHub or git commands automatically?

No. It provides investigation examples that a reviewer may choose to run.

Can it decide if an issue should be closed?

It can recommend a category, but a maintainer should verify evidence before closing any issue.

Can teams use it outside FiftyOne?

Yes, but the categories and templates are written for the FiftyOne project.

What evidence should reviewers collect?

Reviewers should collect version details, reproduction steps, code references, related issues, and recent commits.

Which tools can use this skill?

The report lists support for Claude, Codex, and Claude Code.

Developer Details

Author

AdonaiVera

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/AdonaiVera/fiftyone-skills/tree/main/pr-triage/skills/fiftyone-pr-triage

Ref

6eec4a59f63ff83440a84c18d1aef79743bc714e

Maintenance freshness

7/21/2026

Usage

6 downloads · 233 views

File structure

📄 SKILL.md

fiftyone-pr-triage

Install with my Agent

Agent-readable resources

Test it

Security Audit

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Skillstore Score

What You Can Build

Reduce Maintainer Backlog

Validate Bug Reports

Draft Support Responses

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details