agentleFS
NVIDIAKnown publisherNVIDIA/nemoclaw-community/.agents/skills/nemoclaw-community-contributor-examples/SKILL.md

nemoclaw-community-contributor-examples

Skill142 starsChanged 3 months agoApache-2.0View on GitHub

Guide NemoClaw Community contributors through classifying, naming, adding, moving, renaming, and reviewing repository examples. Use when work affects examples, recipes, partner contributions, field demos, developer tools, catalog collections, category indexes, upstream links, or example paths.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to keep the example catalog navigable as it grows without changing an example's runtime or security boundaries accidentally.

    line 11
  2. Distinctive:

    Before drafting or reviewing a new top-level example README, follow the canonical Example README Template.

    line 19
  3. Distinctive:

    Treat it as the required information contract instead of copying the template into this skill.

    line 21
  4. Distinctive:

    Read the target example's README and nearby deployment documentation before classifying or naming it.

    line 23
  5. Distinctive:

    When moving or renaming an existing example, also read references/restructure-checklist.md and inventory every repository reference before …

    line 27
  6. Distinctive:

    Update the public catalog, repository links, contribution commands, notices, submodule configuration, and external-document follow-ups in …

    line 32
  7. Very specific:

    Run the smallest relevant example checks, then the repository-wide checks required by CONTRIBUTING.md.

    line 35
  8. Distinctive:

    Treat directory placement as navigation, not a support or maturity promise.

    line 40
  9. Distinctive:

    Do not classify provenance from technology usage alone.

    line 41
  10. Distinctive:

    Do not broaden egress, permissions, credential exposure, host access, or agent authority as part of a catalog change.

    line 43
  11. Distinctive:

    Do not retain duplicate compatibility directories.

    line 45
  12. Distinctive:

    Keep public drafts sanitized.

    line 49
  13. Distinctive:

    Ask maintainers when ownership or artifact type remains ambiguous after inspecting the example.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --><!-- SPDX-License-Identifier: Apache-2.0 -->

NemoClaw Community Contributor Examples

Use this skill to keep the example catalog navigable as it grows without changing an example's runtime or security boundaries accidentally.

Workflow

  1. Read references/example-taxonomy.md. For issue and pull request metadata, also read the canonical maintainer taxonomy.
  2. Before drafting or reviewing a new top-level example README, follow the canonical Example README Template. Treat it as the required information contract instead of copying the template into this skill.
  3. Read the target example's README and nearby deployment documentation before classifying or naming it.
  4. Select the artifact type first. For recipes, select contributor provenance second. Use an outcome-oriented leaf name.
  5. When moving or renaming an existing example, also read references/restructure-checklist.md and inventory every repository reference before editing.
  6. Preserve contributor attribution, deployment behavior, security policy, credential handling, teardown behavior, and Compose/Helm parity.
  7. Update the public catalog, repository links, contribution commands, notices, submodule configuration, and external-document follow-ups in the same change.
  8. Run the smallest relevant example checks, then the repository-wide checks required by CONTRIBUTING.md.

Boundaries

  • Treat directory placement as navigation, not a support or maturity promise.
  • Do not classify provenance from technology usage alone. Require explicit attribution or repository history.
  • Do not broaden egress, permissions, credential exposure, host access, or agent authority as part of a catalog change.
  • Do not retain duplicate compatibility directories. Document path migrations and update callers.
  • Base README commands, results, compatibility, support, security, and performance claims on repository evidence. Do not draft from an issue alone.
  • Keep public drafts sanitized. Do not include secrets, internal links, tenant details, private paths, or nonpublic environment names. Use obvious placeholders for private values.
  • Require a human contributor to review and correct coding-agent drafts before submission.
  • Ask maintainers when ownership or artifact type remains ambiguous after inspecting the example.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.