CtrlK
BlogDocsLog inGet started
Tessl Logo

nemoclaw-maintainer-find-review-pr

Find high-priority open NemoClaw security PRs to review, including competing or superseded candidates.

63

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/nemoclaw-maintainer-find-review-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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, highly actionable workflow for a maintainer-audit task: concrete CLI commands, explicit validation gates and early exits, and strong safety railings that keep the skill read-only. Weakest points are minor redundancy around the closure-gating policy and the inlined parser-grammar detail that belongs in the comparator skill's reference material.

DimensionReasoningScore

Conciseness

The body is dense and nearly everything is domain-specific policy Claude could not know (the project-item jq filter, the parser grammar families, the closure-gating checklist, priority tiebreakers). Not 5, because there is minor trimmable repetition — the closure-gating rules in Step 4 are restated nearly verbatim in the Step 5 superseded example, and lines like "It records a relationship but does not prove that the target carries the source PR's work" overlap the preceding sentence. Not 3, since these are minor instances rather than whole padded sections.

4 / 5

Actionability

Guidance is largely copy-paste ready: the `gh project item-list ... | jq` candidate query, the `gh pr view --json ... --jq` field fetch, the supersession detector invocation with exact pattern families, and ready-to-fill output templates. Not 5, because of small gaps — Step 1 says to "fetch the body, author, branch, labels, and creation time with `gh pr view`" without giving the field list (the Step 3 command omits body/branch/labels), and the detector script lives in a sibling skill path that is assumed present.

4 / 5

Workflow Clarity

A clearly sequenced five-step workflow with prerequisites, an explicit early-exit checkpoint ("If no PRs remain, report that result and stop"), a fallback for unlinked PRs ("mark it as `(no linked issue)`"), an ordered tiebreaker list for the summary recommendation, and a literal pre-closure validation checklist (transfer, verify commits/attribution/CI, rerun comparator, confirm full scope, merge target). This matches the anchor "Clear sequence with explicit validation steps; ... checklists for complex processes". The batch-operation cap does not bind: although the skill scans many PRs, it is read-only reporting ("Never close a PR") and verification steps are present.

5 / 5

Progressive Disclosure

Sections are clearly organized by step with a Notes section, and external material is delegated via one-level-deep, well-signaled cross-skill references (`../nemoclaw-maintainer-pr-comparator/scripts/parse-supersession.sh` and `../nemoclaw-maintainer-policies/references/workflow-policy.md`); this bundle has no local reference files, so the body is the whole payload. Not 5, because the ~25-line parser-grammar section (supersession statement families) documents another skill's parser and would sit more naturally in a reference file, and the referenced sibling-skill paths cannot be verified from this bundle.

4 / 5

Total

17

/

20

Passed

Description

70%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 tight, third-person description with a specific domain and a distinctive capability (competing/superseded PR detection). Its main weakness is the absent explicit "Use when..." trigger clause, which caps completeness and leaves invocation context implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g., "Use when a NemoClaw maintainer asks for security PRs to review, triage, or a review-queue summary."

Include the common variation "pull requests" alongside "PRs" and natural maintainer phrasing like "triage" to broaden trigger-term coverage.

Optionally mention linking each PR to its issue, since that is a concrete capability of the skill currently only surfaced in the body.

DimensionReasoningScore

Specificity

Concrete attributes and actions are named: "Find high-priority open NemoClaw security PRs to review", "including competing or superseded candidates" — several specific actions (find, review, identify competing/superseded) with only minor gaps (e.g., linking PRs to issues is in the body but not the description). Not 3, because it goes beyond naming a domain with 1-2 generic actions; not 5, because coverage is one sentence with no additional actions or qualifiers.

4 / 5

Completeness

The "what" is clear (find open high-priority NemoClaw security PRs to review, including competing/superseded candidates), but there is no "Use when..." clause or equivalent explicit trigger guidance — when to invoke it is only weakly implied by the reporting context. Per the judging guideline, a missing explicit trigger clause caps completeness at 3; it is not 2 because the "what" half is specific and concrete.

3 / 5

Trigger Term Quality

Natural maintainer phrases are present: "security PRs", "review", "high-priority", "open", "competing", "superseded" — terms a user would naturally say. Not 3, since coverage goes beyond a few relevant keywords with no variations; not 5, because common variations are missing ("pull request" spelled out, "triage", repo/org names).

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — "NemoClaw security PRs", "Project Priority" semantics implied by "high-priority", and "competing or superseded" analysis — so trigger overlap with other skills is minimal. It clearly matches the anchor "Clear niche with distinct triggers; minimal conflict risk" and not the 4 anchor, which anticipates overlap with closely related skills.

5 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.