Nemoclaw Maintainer Normalize Title Tags Agent Skill

Normalizes GitHub issue and PR titles by removing any bracketed [NemoClaw] tag case-insensitively, even when the tag appears later in the title. Use when cleaning issue tags, bulk-renaming titles, or normalizing repo title hygiene.

3k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

22044

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-normalize-title-tags

What comes with it

7 437 bytes besides the instruction

scripts/normalize-title-tags.ts

The instruction itself

10 sections, as written by the author

NemoClaw Maintainer — Normalize Title Tags

Preview and optionally apply bulk title cleanup for bracketed NemoClaw tags in GitHub issue and PR titles.

Examples

[NemoClaw][All Platforms] local-inference policy preset missing Ollama ports → [All Platforms] local-inference policy preset missing Ollama ports
[Bug] [Nemoclaw] [Slack] Slack configuration in Nemoclaw Onboard fails → [Bug] [Slack] Slack configuration in Nemoclaw Onboard fails

Prerequisites

You must be in the NemoClaw git repository.
The gh CLI must be authenticated with write access to NVIDIA/NemoClaw.
Default behavior is a dry run. Do not apply changes until the user approves the preview.

Workflow

Copy this checklist and track progress:

Title tag cleanup progress:
- [ ] Step 1: Verify GitHub auth
- [ ] Step 2: Preview proposed title changes
- [ ] Step 3: Confirm scope
- [ ] Step 4: Apply changes
- [ ] Step 5: Verify no matching tags remain in scope

Step 1: Verify GitHub Auth

gh auth status

Step 2: Preview Proposed Changes

node --experimental-strip-types --no-warnings \
  .agents/skills/nemoclaw-maintainer-normalize-title-tags/scripts/normalize-title-tags.ts

The script matches bracket tags whose content is nemoclaw, case-insensitively, anywhere in the title.

It prints a dry-run summary by default. Review the proposed renames with the user before applying anything.

Step 3: Confirm Scope

Ask the user which scope they want:

Default — all open and closed issues and PRs in NVIDIA/NemoClaw
State filter — optionally limit to open or closed
Repo override — only when the user explicitly wants a different repository

Step 4: Apply Changes

Apply to all items:

node --experimental-strip-types --no-warnings \
  .agents/skills/nemoclaw-maintainer-normalize-title-tags/scripts/normalize-title-tags.ts \
  --apply

Apply only to open items:

node --experimental-strip-types --no-warnings \
  .agents/skills/nemoclaw-maintainer-normalize-title-tags/scripts/normalize-title-tags.ts \
  --state open \
  --apply

Step 5: Verify

The script automatically re-runs the same search after --apply and exits non-zero if matching tags remain.

If verification fails, stop and show the remaining matches to the user instead of retrying blindly.

Notes

The script uses the GitHub Issues API, which covers both issues and pull requests.
It removes only bracket tags whose content is nemoclaw, ignoring case. Plain-text mentions of NemoClaw are untouched.
The default repository is NVIDIA/NemoClaw. Pass --repo OWNER/REPO only when the user explicitly wants a different repo.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take nvidia/nemoclaw-maintainer-normalize-title-tags from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.