agentsclimarketplace

Oss maintainer triage

Skill shinzoxD/knackbox/skills/productivity/oss-maintainer-triage

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install
npx -y skills add shinzoxD/knackbox --skill oss-maintainer-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Triage open-source issues and PRs with labels, reproduction asks, and maintainer-friendly replies. Use whenever the user maintains a public repo and needs issue triage, good-first-issue labeling, incomplete bug report replies, or PR intake for an open-source project.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, as published. Nobody here has run it

OSS Maintainer Triage

Maintainer time is the scarce resource. Triage creates clarity: valid bug, needs repro, duplicate, out of scope, or ready for contribution.

Workflow

  1. Skim title/body; restate the ask in one line.
  2. Classify: bug, feature, question, docs, security, spam.
  3. Labels: type, area, status (needs-repro, good first issue, help wanted).
  4. Repro completeness; ask for versions/OS/steps when missing.
  5. PR intake: scope, tests, license/DCO, breaking changes.
  6. Reply templates that are kind and boundaried.
  7. Security: private reporting path, no public exploit detail.

Output format

## Triage: #<n or title>
**Type:** …
**Labels:** …
**Priority:** …
**Reply (public):**
…
**Internal note:** …

Rules

  1. Assume good intent until proven otherwise; still enforce scope.
  2. Do not promise timelines you cannot keep.
  3. good first issue must be actually small and well-scoped.
  4. Close duplicates with links; keep one thread canonical.
  5. Never dismiss security reports in public threads casually.
  6. Batch triage tables when many issues provided.

Edge cases

  • Entitled demands: firm boundaries, link CONTRIBUTING.
  • Drive-by huge PRs: ask to split; thank effort; state review capacity.
  • Abandoned issues: stale bot policy suggestions.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.