CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 an exemplary progressive-disclosure index: concise, well-organized, with real one-level references and concrete per-use-case reading orders. The only gap is the absence of an explicit validation/retry feedback loop in the answering workflow.

DimensionReasoningScore

Conciseness

The body is a lean manifest/index: one-line file descriptions plus brief answering rules, with no over-explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Gives concrete, ordered reading lists per use case ('Read workflow-policy.md, project-workflow.md, and daily-flow.md in that order') and specific directives ('Use label-taxonomy.json to validate allowed values'), with only minor gaps in fully spelled-out procedures.

4 / 5

Workflow Clarity

Sequences the two main workflows (workflow questions vs agent implementation) with ordered references and explicit guardrails ('Do not invent labels'), but lacks an explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

Clear overview manifest with well-signaled, one-level-deep references; every referenced file exists in references/ and each is annotated with its scope, enabling easy navigation.

5 / 5

Total

18

/

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.

The description is strong: third-person voice, explicit what/when structure, and a comprehensive trigger-keyword list scoped to a distinct NemoClaw maintainer niche. The only minor gap is a narrow set of action verbs despite broad topic coverage.

DimensionReasoningScore

Specificity

Names the domain ('Provide read-only NemoClaw maintainer policy') and enumerates concrete capability areas (Issue Type, labels, Project fields, release labels, triage, duplicates, blocked items), though the action verbs are limited to 'provide' and 'answer questions'.

4 / 5

Completeness

Clearly states both what ('Provide read-only NemoClaw maintainer policy') and when ('Use for questions about...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The explicit 'Trigger keywords' list provides comprehensive, natural maintainer-facing terms (maintainer policy, label taxonomy, release train, triage policy) including synonyms and variants a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The NemoClaw-specific niche and explicit trigger list make it clearly distinguishable from other skills with minimal overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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