New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Metalint

by managedcode in managedcode/dotnet-skills

Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters.

MITAuto-check passedDevelopment

Install Metalint

skills CLI
$ npx skills add managedcode/dotnet-skills --skill metalint -a claude-code

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

GitHub CLI
$ gh skill install managedcode/dotnet-skills metalint --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/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/Metalint/skills/metalint .claude/skills/metalint && 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/

Facts

Skill name
metalint
GitHub stars
486
Token cost
~1.4k tokens
SKILL.md length
655 words
Files
2
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters.

  • Works in 7 steps: Define underlying ownership first → Use Metalint only after those owners are… → Keep all wrapper configuration under… → …
  • : unified frontend lint commands
  • SKILL.md covers Trigger On, Do Not Use For, Inputs and Workflow, plus 7 more sections
  • Calls rg, npx and npm

What it does

Metalint is an agent skill from managedcode/dotnet-skills. Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters. USE FOR: unified frontend lint commands; combined ESLint, Stylelint, HTMLHint, or similar checks; CI orchestration over multiple frontend linters. DO NOT USE FOR: simple repos where Biome already covers the required surface; teams that have not decided which underlying linters own each file type. INVOKES: inspect the repository context, edit targeted files, and run relevant build…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `manifest.json`). Compatibility notes: Requires a .NET repository with a Node-based frontend and multiple underlying linters; Metalint is an orchestrator, not a replacement for the actual linter…

It sits in Development, covering Linting and formatting. It works with ESLint, .NET and npm. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : unified frontend lint commands
  • Combined ESLint
  • CI orchestration over multiple frontend linters
  • : simple repos where Biome already covers the required surface

Example prompts

  • “/metalint”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Requires a .NET repository with a Node-based frontend and multiple underlying linters; Metalint is an orchestrator, not a replacement for the actual linter configs it delegates to.

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Define underlying ownership first
  2. Use Metalint only after those owners are explicit.
  3. Keep all wrapper configuration under .metalint/ and keep the delegated configs reviewable.
  4. Add package scripts such as
  5. Treat formatter overlap carefully. If delegated tools can all fix files, define which ones are allowed to mutate which globs.
  6. Use Metalint in CI when the repo benefits from a single frontend lint step and formatter output such as GitHub annotations.
  7. Re-run the underlying owners directly when debugging Metalint issues so failures stay attributable.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. 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:

    • rg
    • npx
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, 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.

  • Compatibility

    Requires a .NET repository with a Node-based frontend and multiple underlying linters; Metalint is an orchestrator, not a replacement for the actual linter configs it delegates to.

    From compatibility in the SKILL.md frontmatter.

Context cost

Metalint loads about 1.4k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 655 words of instructions outside code blocks.

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

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 managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 655 words, ~1,387 tokens.

Download SKILL.mdSave it as .claude/skills/metalint/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
metalint
description
Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters. USE FOR: unified frontend lint commands; combined ESLint, Stylelint, HTMLHint, or similar checks; CI orchestration over multiple frontend linters. DO NOT USE FOR: simple repos where Biome already covers the required surface; teams that have not decided which underlying linters own each file type. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires a .NET repository with a Node-based frontend and multiple underlying linters; Metalint is an orchestrator, not a replacement for the actual linter configs it delegates to.

Metalint for Aggregated Frontend Linting in .NET Repositories

Trigger On

  • the repo wants one command to run several frontend linters together
  • the user asks for a unified lint entrypoint over ESLint, Stylelint, HTMLHint, or similar tools
  • the repo already has multiple linters and the problem is orchestration rather than choosing a single owner

Do Not Use For

  • simple repos where one tool such as Biome already covers the required surface
  • teams that have not decided which underlying linters own JS, CSS, and HTML yet
  • replacing the underlying linter configs with one vague wrapper config

Inputs

  • the nearest AGENTS.md
  • package.json
  • existing linter configs
  • any .metalint/ directory already checked in

Workflow

  1. Define underlying ownership first:
    • ESLint for JS or TS
    • Stylelint for CSS or SCSS
    • HTMLHint for static HTML
    • other delegated linters only when the repo really uses them
  2. Use Metalint only after those owners are explicit.
  3. Keep all wrapper configuration under .metalint/ and keep the delegated configs reviewable.
  4. Add package scripts such as:
    • lint: metalint
    • lint:fix: metalint --fix
  5. Treat formatter overlap carefully. If delegated tools can all fix files, define which ones are allowed to mutate which globs.
  6. Use Metalint in CI when the repo benefits from a single frontend lint step and formatter output such as GitHub annotations.
  7. Re-run the underlying owners directly when debugging Metalint issues so failures stay attributable.

Current Upstream Notes

  • Metalint v0.22.1 keeps the Bun, Deno, JSR, and npm-check-updates 21 support from v0.22.0 and fixes the formatter so console output preserves the intended column order. Re-run snapshot or parser tests for any CI integration that consumes Metalint's human-readable output.
  • Secretlint now ignores .gitignore. Re-run secret scanning against representative ignored and tracked fixtures after upgrading so the wrapper's effective file scope remains intentional.

Bootstrap When Missing

  1. Detect current state:
    • rg --files -g 'package.json' -g '.metalint/**' -g 'eslint.config.*' -g 'stylelint.config.*' -g '.htmlhintrc*'
    • rg -n '"metalint"|"eslint"|"stylelint"|"htmlhint"' --glob 'package.json' .
  2. Prefer a repo-local install:
    • npm install --save-dev metalint
  3. Install the delegated linters the repo actually needs; Metalint does not replace them.
  4. Create .metalint/metalint.config.js plus delegated config files under .metalint/ only when the repo wants that consolidated layout.
  5. Verify with:
    • npx metalint
    • npx metalint --fix
  6. Return status: configured if the repo now has a working aggregated entrypoint, or status: improved if orchestration was tightened.
  7. Return status: not_applicable when the repo intentionally stays with direct linter commands and does not want the wrapper layer.
Show full SKILL.md (250 more words)Show less

Handle Failures

  • If Metalint says a delegated linter is missing, install that linter or remove it from the wrapper config; Metalint cannot invent the underlying tool.
  • If fix mode causes conflicting rewrites, split ownership by glob instead of letting several tools mutate the same files blindly.
  • If the wrapper becomes harder to understand than direct commands, the repo probably does not need Metalint.
  • Debug noisy failures by running the delegated linter directly first, then come back to Metalint integration.

Deliver

  • one repeatable frontend lint entrypoint
  • explicit delegated-tool ownership
  • wrapper config that stays readable and attributable

Validate

  • each delegated linter is actually installed and configured
  • fix ownership is explicit across file types
  • CI output remains attributable to the right underlying tool
  • Metalint reduced operational friction instead of hiding the real owners

Ralph Loop

  1. Plan: analyze current state, target outcome, constraints, and risks.
  2. Execute one step and produce a concrete delta.
  3. Review the result and capture findings.
  4. Apply fixes in small batches and rerun checks.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with a reason.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current step
  • actions_taken: concrete changes made
  • verification: commands, checks, or review evidence
  • remaining: unresolved items or none

Example Requests

  • "Give this repo one frontend lint command."
  • "Wrap ESLint, Stylelint, and HTMLHint under Metalint."
  • "Use Metalint in GitHub Actions for frontend checks."

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in catalog/Tools/Metalint/skills/metalint of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Metalint 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.

Metalint compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Metalint this skillmanagedcode/dotnet-skills486—~1.4kAutomated safety check: PassMIT
Create Saleor Packagesaleor/apps162—~608Automated safety check: PassCustom licence
Igniteui Angular LintingIgniteUI/igniteui-angular599—~614Automated safety check: PassCustom licence
Antfuoyjt/uniapp-vue3-template627—~1.3kAutomated safety check: PassMIT
TypescriptLiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator1.8k—~1.5kAutomated safety check: PassGPL-3.0
Es X Major Version Prepeslint-community/eslint-plugin-es-x157—~801Automated safety check: PassMIT

Similar skills

  • Create Saleor Package

    saleor/apps

    Scaffold a new shared package in the saleor-apps monorepo under ./packages/.

    162 GitHub stars~608 tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Igniteui Angular Linting

    IgniteUI/igniteui-angular

    Quick-reference for linting the core Ignite UI for Angular library.

    599 GitHub stars~614 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Antfu

    oyjt/uniapp-vue3-template

    Anthony Fu's {Opinionated} preferences and best practices for web development

    627 GitHub stars~1.3k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • Typescript

    LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

    Write TypeScript that satisfies this repo's lint and tsconfig rules, and convert an existing .js file to .ts without breaking its call sites.

    1.8k GitHub stars~1.5k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Es X Major Version Prep

    eslint-community/eslint-plugin-es-x

    Prepare eslint-plugin-es-x for a major version release from a broad instruction such as "prepare the major version upgrade" or "prepare the next major release".

    157 GitHub stars~801 tokensUpdated 12 days ago
    DevelopmentAuto-check passed

  • Update npm Packages

    PowerShell/vscode-powershell

    Guide for updating NPM dependencies in vscode-powershell. An agent skill from PowerShell/vscode-powershell.

    1.9k GitHub stars~350 tokensUpdated 1 mo ago
    DevelopmentAuto-check: warnings

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Metalint

What does Metalint do?

Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters. Metalint is an agent skill from managedcode/dotnet-skills.NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters.

When should I use Metalint?

Metalint fits situations like: : unified frontend lint commands; combined ESLint; CI orchestration over multiple frontend linters; : simple repos where Biome already covers the required surface.

How do I install Metalint in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill metalint -a claude-code`. Or copy the skill folder (catalog/Tools/Metalint/skills/metalint in managedcode/dotnet-skills) into .claude/skills/metalint in your project. Claude Code loads it when a task matches its description.

How do I install Metalint in Codex?

Run `npx skills add managedcode/dotnet-skills --skill metalint -a codex`. Or copy the skill folder (catalog/Tools/Metalint/skills/metalint in managedcode/dotnet-skills) into .agents/skills/metalint in your project. Codex loads it when a task matches its description.

Can I use Metalint 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 managedcode/dotnet-skills --skill metalint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/metalint, .gemini/skills/metalint, .github/skills/metalint and .opencode/skills/metalint in your project.

What does Metalint need to run?

Going by SKILL.md and its folder, Metalint needs the command-line tools its instructions call (rg, npx and npm). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires a .NET repository with a Node-based frontend and multiple underlying linters; Metalint is an orchestrator, not a replacement for the actual linter configs it delegates to..

Does Metalint access the network?

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

Is Metalint 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 Metalint use?

Metalint is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Metalint use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Metalint?

Skills that share tags, products or a category with Metalint: Create Saleor Package (saleor/apps, 162 stars), Igniteui Angular Linting (IgniteUI/igniteui-angular, 599 stars), Antfu (oyjt/uniapp-vue3-template, 627 stars) and Typescript (LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Metalint?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

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