nemoclaw-community-contributor-examples

Standardize classification, naming, and structural migration of agent workflow examples.

86|42|Updated May 6, 2026
One-click install
npx skills add https://github.com/NVIDIA/nemoclaw-community --skill nemoclaw-community-contributor-examples
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-community-contributor-examples
Source: https://github.com/NVIDIA/nemoclaw-community/tree/main/.agents/skills/nemoclaw-community-contributor-examples
Command: npx skills add https://github.com/NVIDIA/nemoclaw-community --skill nemoclaw-community-contributor-examples

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of maintaining a navigable and consistent catalog of agent workflow examples as the repository grows, ensuring that organizational structure remains logical without disrupting existing runtime or security configurations.

Core Features & Use Cases

  • Taxonomy Enforcement: Provides standardized classification for recipes, demos, launchables, and tools based on contributor provenance and artifact type.
  • Restructuring Guidance: Offers a systematic checklist for moving or renaming examples while preserving Git history, contributor attribution, and deployment parity.
  • Use Case: When a contributor adds a new partner-authored recipe, this skill ensures it is placed in the correct directory, follows the naming convention, and maintains all necessary documentation links.

Quick Start

Use the nemoclaw-community-contributor-examples skill to validate the proposed path and metadata for a new community recipe before submitting a pull request.

Frequently Asked Questions about nemoclaw-community-contributor-examples

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize community examples in a repository to maintain consistent structure?

To classify a new agent workflow recipe, apply the standardized taxonomy based on contributor provenance and artifact type. This skill validates the proposed path and metadata to ensure correct placement within the repository directory structure.

What is the best way to rename or move example files while preserving Git history?

The best way to rename or move example files while preserving Git history is to follow a systematic restructuring checklist. This process maintains contributor attribution, documentation links, and deployment parity without disrupting existing runtime configurations.

How do I validate metadata for a new community recipe before submitting a pull request?

Validate metadata for a new community recipe by checking it against the defined example taxonomy and restructuring checklist. This ensures the recipe follows the correct naming convention and maintains all necessary documentation links before pull request submission.

When should I use a taxonomy enforcement process for agent workflow examples?

Use taxonomy enforcement for agent workflow examples when contributors add new partner-authored recipes or when restructuring the repository. It ensures artifacts are placed in correct directories, maintaining discoverability and operational stability across the growing catalog.

Does restructuring the community repository disrupt existing security or runtime configurations?

Restructuring the community repository does not disrupt existing security or runtime configurations when following the systematic migration checklist. The process preserves Git history, contributor attribution, and deployment parity to maintain operational stability.