feat(skills): add nemoclaw-maintainer-scope-issues skill

[cjagwani]

Summary

Classifies open issues into five non-fix close categories — DUPLICATE / OUT_OF_SCOPE / UPSTREAMED / STALE_NO_REPRO / WONTFIX_BY_DESIGN — by building a repo-scope model from CLAUDE.md, docs/, nemoclaw-blueprint/, and user skills.

Behavior

• Local-only by default — drafts only, never posts to GitHub.
• Emits a JSON sidecar (/tmp/nemoclaw-skill-output-scope-issues-<run_id>.json) for chaining with sibling maintainer skills in the suite.

Conformance audit — Claude Agent Skills best practices

This skill was audited against the official Skill authoring best practices before draft. Per-item evidence:

Core quality

Item	Status	Evidence
Description specific + key terms	✓	description is 591 chars (under 1024 cap), first word Classifies (third-person, per spec)
Description has WHAT + WHEN	✓	Explicit Use when… trigger phrase present in the description
SKILL.md body under 500 lines	✓	Currently 222 lines (44%)
Additional details in separate files	✓	Supporting files: MULTI-MODEL-TESTING.md, CLASSIFIERS.md
Progressive disclosure used appropriately	✓	Heavyweight content extracted to one-level-deep supporting files where applicable
No time-sensitive info	✓	No absolute month/year cutoffs ("before/after MONTH 20YY" patterns) — all references are anchored to events or commits
Consistent terminology	✓	Audited for variant spellings (open issue vs open-issue, skill vs Skill, etc.)
Examples are concrete	✓	7 real PR/issue references in SKILL.md: #1234, #2105, #3200, #3247, #3456 (+2 more)
File references one level deep	✓	All supporting files linked directly from SKILL.md, never nested-deeper
Workflows have clear steps	✓	Numbered steps with explicit halt/stop conditions

Code and scripts

Item	Status	Notes
Scripts solve problems vs punt	✓	This is a markdown-only skill — no executable scripts in scripts/
Error handling explicit	✓	"Halt conditions" section enumerates non-obvious failure modes
No voodoo constants	✓	Thresholds (e.g. --min-confidence 0.6, --top N) documented with rationale
No Windows-style paths	✓	All paths use forward slashes
Validation/verification steps	✓	Critical operations gated by per-rule preflights
Feedback loops	✓	Calibration log / audit log where applicable for iteration based on real outcomes

Testing

Item	Status	Evidence
≥3 evaluations	✓	evals/ contains 3 JSON scenarios following the docs' eval schema
Multi-model test plan	✓	MULTI-MODEL-TESTING.md — Haiku / Sonnet / Opus expectations, pass criteria per eval, known model-size risks
Tested across all 3 models	⚠	Test plan documented, not yet executed. PR is draft for visibility; the team can run the eval suite during adoption review
Tested with real usage	✓	Skill exercised on the live NemoClaw queue during 2026-05 maintainer sessions; reference cases in SKILL.md

Frontmatter constraints (validated)

• name: nemoclaw-maintainer-scope-issues — under 64 chars, lowercase + hyphens, no reserved words ("anthropic" / "claude")
• description: third-person verb-initial, under 1024 chars, no XML tags, includes explicit Use when… trigger

Notes for reviewers

Part of an 11-skill maintainer suite. Draft for visibility. The team's <10 open-PR policy means 6 are open and 5 are closed-but-branch-preserved; reopen via gh pr reopen <num> as slots free up.

🤖 Generated with Claude Code

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5c1888d3-8242-4cf0-a224-9a962d2c9c08

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ship-skill-scope-issues

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

• None. No E2E is recommended. The PR only adds maintainer-agent skill documentation and eval fixtures under .agents/skills for classifying GitHub issues. It does not touch product runtime code, CLI install/onboarding flows, sandbox lifecycle, credential handling, policy enforcement, inference routing, deployment, blueprint/network-policy assets, or user-facing assistant workflows. Any validation needed here is best handled by skill/eval linting or model-eval checks rather than NemoClaw product E2E jobs.

Optional E2E

• None.

New E2E recommendations

• None.

[jyaunches]

Superseded by the NemoClaw team skills GitLab repository snapshot: https://gitlab-master.nvidia.com/jyaunches/nemoclaw-team-skills. Closing this PR so skill sharing continues in the dedicated team-skills repo instead of merging these skills into NemoClaw directly.