agentleFS
NVIDIAKnown publisherNVIDIA/nemoclaw-community/.agents/skills/nemoclaw-community-maintainer-policies/SKILL.md

nemoclaw-community-maintainer-policies

Skill142 starsChanged 3 months agoApache-2.0View on GitHub

Provide read-only NemoClaw Community maintainer policy for Issue Type, labels, title conventions, triage, and example publication metadata.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Read workflow-policy.md for the source-of-truth hierarchy and authorization boundary.

    line 16
  2. Distinctive:

    Read triage-instructions.md before classifying an issue or pull request.

    line 17
  3. Distinctive:

    Read label-taxonomy.md for human-facing label policy.

    line 18
  4. Very specific:

    Use label-taxonomy.json to validate machine values.

    line 19
  5. Distinctive:

    Read examples.md for representative classifications.

    line 20
  6. Distinctive:

    Use plain language and distinguish native Issue Type from PR type, routing, workflow, example-kind, and provenance labels.

    line 22

≈ “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 Maintainer Policies

This package is the canonical maintainer-policy source for NemoClaw Community.

References

  • Read workflow-policy.md for the source-of-truth hierarchy and authorization boundary.
  • Read triage-instructions.md before classifying an issue or pull request.
  • Read label-taxonomy.md for human-facing label policy.
  • Use label-taxonomy.json to validate machine values.
  • Read examples.md for representative classifications.

Use plain language and distinguish native Issue Type from PR type, routing, workflow, example-kind, and provenance labels. Do not invent labels or perform metadata writes without explicit authorization.

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.