nemoclaw-contributor-plan-issue
Plan, refine, scope, or divide a NemoClaw GitHub issue into independently valuable capability slices before implementation. Use when a user asks to plan an issue, refine its scope, define acceptance evidence, break it down, split it, or identify the first capability slice. Ask which lifecycle stage they want when a request such as "work on this issue" could mean planning or implementation. Do not use for generic implementation, PR publication, maintainer-loop, or requests without issue-planning intent. Trigger keywords - plan issue, refine issue, scope issue, break down issue, split issue, capability slices, acceptance criteria.
69
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The workflow reads GitHub issues and PRs, which are outsider-authored feeds containing free text.
- Repository
- NVIDIA/NemoClaw
- Commit
e94c06f
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.