CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured planning workflow with an exact report contract and explicit stop conditions; it earns top conciseness marks. It stops short of full marks on actionability and workflow clarity because key discovery and validation detail lives in external _shared references rather than inline.

DimensionReasoningScore

Conciseness

Lean and efficient prose that assumes Claude's competence, with no concept padding and every section earning its place; matches the 'lean and efficient' anchor.

5 / 5

Actionability

Provides a concrete, copy-paste-ready report template and structured actionable steps, but discovery and validation guidance delegate to external _shared references rather than being fully self-contained executable instructions.

4 / 5

Workflow Clarity

Clear sequenced workflow with explicit stop conditions and a hard-stop gate ('Stop discovery when current evidence supports one coherent plan'), though some validation checkpoints live in referenced files rather than inline, leaving a minor gap versus the top anchor.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep _shared references and no local bundle files; structure is good with only minor organization gaps, fitting just below the clear-overview top anchor.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete capabilities, provides explicit 'Use when' trigger guidance with natural keywords, and sharply distinguishes itself from adjacent skills with a do-not-use clause. Minor keyword-synonym gaps keep trigger quality and specificity just below the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete planning actions ('Plan, refine, scope, or divide a NemoClaw GitHub issue into independently valuable capability slices') with minor gaps in coverage, fitting the 'several specific actions' anchor rather than comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ('Plan, refine, scope, or divide...') and when ('Use when a user asks to plan an issue, refine its scope...') with concrete trigger phrases and an explicit do-not-use boundary.

5 / 5

Trigger Term Quality

Good keyword coverage of natural phrases users say ('plan issue, refine issue, scope issue, break down issue, split issue, capability slices, acceptance criteria') but presented as a keyword list and missing some synonyms, so below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear NemoClaw issue-planning niche with distinct triggers and explicit conflict avoidance ('Do not use for generic implementation, PR publication, maintainer-loop'), giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 suspicious

Warning

Total

15

/

16

Passed

Repository
NVIDIA/NemoClaw
Reviewed

Table of Contents

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.