Official agent skill

Mcore Linting And Formatting

Linting and formatting for Megatron-LM. An agent skill from NVIDIA/skills.

OfficialApache-2.0Auto-check passedDevelopment

Install Mcore Linting And Formatting

skills CLI

$ npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills mcore-linting-and-formatting --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mcore-linting-and-formatting .claude/skills/mcore-linting-and-formatting && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "mcore-linting-and-formatting" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/mcore-linting-and-formatting into .claude/skills/mcore-linting-and-formatting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcore-linting-and-formatting", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NVIDIA/skills/tree/main/skills/mcore-linting-and-formatting

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills mcore-linting-and-formatting --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mcore-linting-and-formatting .agents/skills/mcore-linting-and-formatting && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mcore-linting-and-formatting" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/mcore-linting-and-formatting into .agents/skills/mcore-linting-and-formatting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcore-linting-and-formatting", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills mcore-linting-and-formatting --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mcore-linting-and-formatting .cursor/skills/mcore-linting-and-formatting && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mcore-linting-and-formatting" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/mcore-linting-and-formatting into .cursor/skills/mcore-linting-and-formatting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcore-linting-and-formatting", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NVIDIA/skills.git --path skills/mcore-linting-and-formatting

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills mcore-linting-and-formatting --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mcore-linting-and-formatting .gemini/skills/mcore-linting-and-formatting && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "mcore-linting-and-formatting" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/mcore-linting-and-formatting into .gemini/skills/mcore-linting-and-formatting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcore-linting-and-formatting", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NVIDIA/skills mcore-linting-and-formatting

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mcore-linting-and-formatting .github/skills/mcore-linting-and-formatting && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "mcore-linting-and-formatting" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/mcore-linting-and-formatting into .github/skills/mcore-linting-and-formatting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcore-linting-and-formatting", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills mcore-linting-and-formatting --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mcore-linting-and-formatting .opencode/skills/mcore-linting-and-formatting && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mcore-linting-and-formatting" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/mcore-linting-and-formatting into .opencode/skills/mcore-linting-and-formatting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcore-linting-and-formatting", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: mcore-linting-and-formatting
GitHub stars: 3.6k
Token cost: ~406 tokens
SKILL.md length: 112 words
Files: 5
Skills in repo: 390
Repo updated: Oct 9, 2026
First seen: Oct 9, 2026
Licence: Apache-2.0

At a glance

Linting and formatting for Megatron-LM. An agent skill from NVIDIA/skills.

Tasks that involve Linting and formatting
SKILL.md covers Running the Formatter, Import Ordering, Setting Up the Linting Group and Code Style Rules
Calls uv and bash

What it does

Mcore Linting And Formatting is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.

Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).

It sits in Development, covering Linting and formatting. It works with NVIDIA AI Platform and Ruff. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Linting and formatting

Example prompts

“/mcore-linting-and-formatting”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 14a98ae. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- uv
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mcore Linting And Formatting loads about 406 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 112 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~41
When it runs · the whole SKILL.md, loaded when a task matches: ~406

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 14a98ae, republished under its Apache-2.0 licence (© NVIDIA). 112 words, ~406 tokens.

Download SKILL.mdSave it as .claude/skills/mcore-linting-and-formatting/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: mcore-linting-and-formatting
description: Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.
license: Apache-2.0
when_to_use: Running linting or autoformat; fixing style violations before a PR; 'pre-commit fails', 'ruff error', 'isort', 'mypy', 'style violation', 'how do I format'…
metadata.author: Philip Petrakian <ppetrakian@nvidia.com>

Linting and Formatting

Running the Formatter

Run before opening a PR:

bash

# Check mode (no changes applied)
BASE_REF=main CHECK_ONLY=true SKIP_DOCS=false bash tools/autoformat.sh

# Fix mode
BASE_REF=main CHECK_ONLY=false bash tools/autoformat.sh

Tools invoked: black, isort, pylint, ruff, mypy.

Import Ordering

After editing imports in any Python files, always run uv run isort on those files before committing:

bash

uv run isort <file1>.py <file2>.py

Setting Up the Linting Group

Inside the container:

bash

uv sync --locked --only-group linting

This installs ruff, black, isort, pylint — the same tools used by tools/autoformat.sh and CI's linting job.

Code Style Rules

Type hints: required on all public API functions. Use X | None, not Optional[X].
Docstrings: Google-style on all public classes and functions.
Naming: follow Python conventions — snake_case for functions and variables, PascalCase for classes.
Line length: 119 characters (configured in pyproject.toml).
No bare except: always catch specific exception types.

Files

SKILL.md and 4 other files in skills/mcore-linting-and-formatting of NVIDIA/skills.

SKILL.md
BENCHMARK.md
evals/evals.json
skill-card.md
skill.oms.sig

Open the folder on GitHubat commit 14a98ae

Compare with similar skills

Mcore Linting And Formatting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mcore Linting And Formatting compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Mcore Linting And Formatting this skillNVIDIA/skills	3.6k	—	~406	Automated safety check: Pass	Apache-2.0	yesterday
Megatron-LM Linting and FormattingNVIDIA/Megatron-LM	18k	—	~316	Automated safety check: Pass	Apache-2.0	today
Minimizing Ty Ecosystem Changesastral-sh/ruff	50k	—	~4.6k	Automated safety check: Pass	MIT	today
Summarise Ecosystem Resultsastral-sh/ruff	50k	—	~2.2k	Automated safety check: Pass	MIT	today
Kedro Babysitkedro-org/kedro	11k	—	~4k	Automated safety check: Pass	Custom licence	yesterday
Saleor Commit Workflowsaleor/saleor	23k	—	~575	Automated safety check: Pass	BSD-3-Clause	yesterday

Similar skills

Megatron-LM Linting and Formatting
NVIDIA/Megatron-LM
Official
Runs the Megatron-LM autoformat script and its linting tools before a pull request, and keeps Python imports in order with isort.
18k GitHub stars~316 tokensUpdated today
DevelopmentAuto-check passed
Minimizing Ty Ecosystem Changes
astral-sh/ruff
Official
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
50k GitHub stars~4.6k tokensUpdated today
DevelopmentAuto-check passed
Summarise Ecosystem Results
astral-sh/ruff
Official
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
50k GitHub stars~2.2k tokensUpdated today
DevelopmentAuto-check passed
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
11k GitHub stars~4k tokensUpdated yesterday
DevelopmentAuto-check passed
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
23k GitHub stars~575 tokensUpdated yesterday
DevelopmentAuto-check passed
Mnemosyne Context
mnemosyne-oss/mnemosyne
Load this when working on the mnemosyne memory system — its repo, sync server, memory databases, or CI.
3.4k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed

More from NVIDIA/skills

All 390 skills in this repo

Vss Deploy Detection Tracking 2D
NVIDIA/skills
Official
A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.
3.6k GitHub starsUsed in 1 repo~4.5k tokens
Auto-check passed
HSB IP Def File Tool
NVIDIA/skills
Official
Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.
3.6k GitHub stars~2.9k tokensUpdated yesterday
Auto-check passed
Isaac Sim Mission Control Showcase
NVIDIA/skills
Official
Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.
3.6k GitHub stars~4.8k tokensUpdated yesterday
Auto-check passed
Defect Image Generation with Cosmos AnomalyGen
NVIDIA/skills
Official
Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.
3.6k GitHub stars~5k tokensUpdated yesterday
Auto-check: notes
Physical AI Video Augmentation on OSMO
NVIDIA/skills
Official
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
3.6k GitHub stars~4.7k tokensUpdated yesterday
Auto-check: notes
TAO Detection KPI Analysis
NVIDIA/skills
Official
Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.
3.6k GitHub stars~2.7k tokensUpdated yesterday
Auto-check: notes

Works with

Questions about Mcore Linting And Formatting

What does Mcore Linting And Formatting do?

Linting and formatting for Megatron-LM. An agent skill from NVIDIA/skills. Mcore Linting And Formatting is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Linting and formatting for Megatron-LM.

When should I use Mcore Linting And Formatting?

Mcore Linting And Formatting fits situations like: tasks that involve Linting and formatting.

How do I install Mcore Linting And Formatting in Claude Code?

Run `npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a claude-code`. Or copy the skill folder (skills/mcore-linting-and-formatting in NVIDIA/skills) into .claude/skills/mcore-linting-and-formatting in your project. Claude Code loads it when a task matches its description.

How do I install Mcore Linting And Formatting in Codex?

Run `npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a codex`. Or copy the skill folder (skills/mcore-linting-and-formatting in NVIDIA/skills) into .agents/skills/mcore-linting-and-formatting in your project. Codex loads it when a task matches its description.

Can I use Mcore Linting And Formatting in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill mcore-linting-and-formatting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcore-linting-and-formatting, .gemini/skills/mcore-linting-and-formatting, .github/skills/mcore-linting-and-formatting and .opencode/skills/mcore-linting-and-formatting in your project.

What does Mcore Linting And Formatting need to run?

Going by SKILL.md and its folder, Mcore Linting And Formatting needs the command-line tools its instructions call (uv and bash). Our summary lists: Python 3.

Does Mcore Linting And Formatting access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Mcore Linting And Formatting safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mcore Linting And Formatting use?

Mcore Linting And Formatting is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mcore Linting And Formatting use?

About 406 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Mcore Linting And Formatting?

Skills that share tags, products or a category with Mcore Linting And Formatting: Megatron-LM Linting and Formatting (NVIDIA/Megatron-LM, 18k stars), Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Summarise Ecosystem Results (astral-sh/ruff, 50k stars) and Kedro Babysit (kedro-org/kedro, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcore Linting And Formatting?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,555 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 9, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Mcore Linting And Formatting

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Linting and Formatting

Running the Formatter

Import Ordering

Setting Up the Linting Group

Code Style Rules

Files

Compare with similar skills

Similar skills

More from NVIDIA/skills

Related

Questions about Mcore Linting And Formatting