docs: list nemoclaw user agent skills

[RlxChap2]

Summary

Adds the missing nemoclaw-user-agent-skills entry to the Agent Skills documentation so the page lists all user skills shipped under .agents/skills.

Related Issue

Fixes #5083

Changes

• Added nemoclaw-user-agent-skills to the Available Skills table.
• Added an example question that maps to nemoclaw-user-agent-skills.

Type of Change

• Code change (feature, bug fix, or refactor)
• Code change with doc updates
• Doc only (prose changes, no code sample modifications)
• Doc only (includes code sample changes)

Verification

• Git hooks passed during commit and push, or npx prek run --from-ref main --to-ref HEAD passes
• Targeted tests pass for changed behavior
• Full npm test passes (broad runtime changes only)
• Tests added or updated for new or changed behavior
• No secrets, API keys, or credentials committed
• Docs updated for user-facing behavior changes
• npm run docs builds without warnings (doc changes only)
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

---

Signed-off-by: RlxChap2 mmah02778@gmail.com

Summary by CodeRabbit

• Documentation
  • Added NemoClaw user agent skills to the available skills documentation, including guidance on obtaining and using the skills and the expected skills layout.
  • Added example question → triggered-skill mappings to help users discover which query will surface NemoClaw capabilities.
  • Clarified steps for cloning/updating and integrating these skills into your assistant workflow.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f7026a2a-f61f-4616-9953-b2880c563eea

📥 Commits

Reviewing files that changed from the base of the PR and between 1aa8036 and 2039e4d.

📒 Files selected for processing (1)

• docs/resources/agent-skills.mdx

✅ Files skipped from review due to trivial changes (1)

• docs/resources/agent-skills.mdx

---

📝 Walkthrough

Walkthrough

Updates docs/resources/agent-skills.mdx to document the nemoclaw-user-agent-skills skill by adding it to the Available Skills table and including an example question that triggers this skill.

Changes

Agent Skills Documentation

Layer / File(s)	Summary
Add nemoclaw-user-agent-skills to documentation docs/resources/agent-skills.mdx	Adds nemoclaw-user-agent-skills entry to the Available Skills table describing how to clone/update and use NemoClaw's agent skills and adds an example question mapping ("What NemoClaw skills are available for my coding assistant?") that triggers nemoclaw-user-agent-skills.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

documentation

Poem

🐰 A skill that hid behind the scenes,
Now listed where the reader leans,
NemoClaw's guide is whole and neat,
Skills and questions finally meet,
Hooray — the docs and rabbit cheer, so sweet!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding nemoclaw-user-agent-skills documentation to the Agent Skills page.
Linked Issues check	✅ Passed	The PR successfully addresses all coding requirements from issue #5083: added nemoclaw-user-agent-skills to the Available Skills table with the specified description, and added a corresponding example question to the Example Questions table.
Out of Scope Changes check	✅ Passed	All changes are directly aligned with issue #5083 requirements; only documentation updates to agent-skills.mdx were made with no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[miyoungc]

Thanks for the docs fix.

Before this can move forward, please read the NemoClaw contributing guide and make sure the PR satisfies the DCO/sign-off requirements:

• Contributing guide: https://github.com/NVIDIA/NemoClaw/blob/main/CONTRIBUTING.md
• Every commit must include a valid Signed-off-by: line for the author, using an email address associated with the GitHub account.
• If the DCO check is failing or the sign-off is not valid, amend or re-create the commit with git commit --signoff and push the updated branch.

After that, please confirm here that you read the contributing guide and that DCO is passing.

[miyoungc]

Update: this may have been a temporary CI failure.

All checks are now passing, so I am proceeding with merge review.

[miyoungc]

Correction: DCO and the status checks are passing, but the PR is still blocked by the verified-signature requirement.

The remaining issue is commit 2039e4d (docs: list nemoclaw user agent skills), which GitHub reports as unsigned. Please amend or recreate that commit with a verified GitHub commit signature, then force-push the branch. The later merge commit is verified, so this appears limited to the original contributor commit.

[miyoungc]

Requesting changes because this PR contains an unverified commit signature.

Repository policy requires PRs to satisfy both gates before merge:

• DCO must pass for every commit.
• GitHub must show every commit as verified.

DCO is currently passing here, but commit 2039e4d is unsigned/unverified. Please amend or recreate the contributor commit with a verified GitHub commit signature and push the updated branch. PRs with unverified commits or failing DCO cannot be accepted.

[miyoungc]

Correction on the remediation path: because force-push is not allowed, this PR cannot be fixed in place if the unsigned commit remains in the branch history.

The required path is to open a fresh PR with a clean commit history where every commit is both DCO-signed and GitHub-verified. We cannot accept this PR while it contains the unverified 2039e4d commit.

[RlxChap2]

Correction on the remediation path: because force-push is not allowed, this PR cannot be fixed in place if the unsigned commit remains in the branch history.

The required path is to open a fresh PR with a clean commit history where every commit is both DCO-signed and GitHub-verified. We cannot accept this PR while it contains the unverified 2039e4d commit.

should i open a new PR ?

[RlxChap2]

i'm gonna open a new PR rn

[RlxChap2]

Opened a fresh replacement PR with a clean one-commit history: #5522

The new commit includes the DCO sign-off and GitHub reports its signature as verified. I did not force-push the original branch.

[miyoungc]

Thank you for reopening a fresh PR. Closing this PR.