nemoclaw-maintainer-policies

Provide read-only NemoClaw maintainer policy. Use for questions about Issue Type, labels, Project fields, release labels, triage, duplicates, blocked items, and maintainer decisions. Trigger keywords - maintainer policy, workflow policy, project workflow, issue type, labels, label taxonomy, needs labels, project status, blocked issue, duplicate issue, daily release label, release train, triage policy.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%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.

A well-structured reference-manifest skill that efficiently points to a real, well-organized bundle of one-level-deep references with clear per-file descriptions and use-case-specific reading orders. The main improvements would be removing minor reference duplication and adding an explicit validation feedback loop.

Suggestions

De-duplicate the References section: workflow-policy.md, project-workflow.md, daily-flow.md, and triage-instructions.md each appear in both an ordered reading list and the per-file list — consolidate or cross-reference to reduce redundancy.

Add an explicit validation feedback loop in 'Answering Workflow Questions' (e.g., 'If a label/field is not in label-taxonomy.json, do not apply it; flag it instead') to move workflow clarity toward 5.

Clarify the ../_shared/documentation-writing-review.md contract reference — it is not part of the local bundle, so note where it lives or inline the essential rule so the skill is self-contained for review.

Dimension	Reasoning	Score
Conciseness	The manifest is lean, assumes Claude's competence, and contains no concept padding, but a few reference files (e.g. workflow-policy.md) appear in both the ordered reading lists and the per-file list, a small redundancy that could be trimmed.	4 / 5
Actionability	Concrete, specific directives are given (read named files in order, use triage-instructions.md as the payload contract, validate allowed values with label-taxonomy.json, do not invent labels), which is mostly executable guidance; the actual decision rules live in the references rather than inlined, leaving minor gaps appropriate to a reference-manifest design.	4 / 5
Workflow Clarity	The 'Answering Workflow Questions' section gives a clear ordered sequence with an explicit validation reference (validate via label-taxonomy.json, do not invent states), but there is no explicit feedback loop for what to do when validation fails, keeping it just below 5.	4 / 5
Progressive Disclosure	All eight referenced bundle files exist and match the body's links; the SKILL.md is a clean overview/index with well-signaled one-level-deep references, per-file descriptions, and ordered reading paths for two distinct use cases, making navigation easy.	5 / 5
	Total	17 / 20 Passed

Description

95%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.

A well-crafted description that explicitly states both the capability and the use conditions with a strong, synonym-rich trigger-keyword list. Its only limitation is a narrow action verb set, which keeps specificity at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete read-only action ('Provide read-only NemoClaw maintainer policy') and enumerates a comprehensive scope of concrete topics (Issue Type, labels, Project fields, release labels, triage, duplicates, blocked items), but the verb set is essentially a single action applied broadly rather than multiple distinct actions, so it sits just below a clean 5.	4 / 5
Completeness	It clearly answers 'what' ('Provide read-only NemoClaw maintainer policy') and 'when' ('Use for questions about...') with an explicit trigger-keyword list, matching the anchor for explicit what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	An explicit 'Trigger keywords -' list provides comprehensive natural-term coverage with synonyms (maintainer policy / workflow policy / triage policy; blocked issue / duplicate issue / project status) that a maintainer would actually say.	5 / 5
Distinctiveness Conflict Risk	The NemoClaw maintainer-policy niche and domain-specific triggers (release train, needs labels, label taxonomy) make it clearly distinguishable with minimal conflict risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: NVIDIA/NemoClaw
Path: .agents/skills/nemoclaw-maintainer-policies/SKILL.md
Commit: e987b00

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

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.