Agent skill

Corvus Analyzers

by corvus-dotnet in corvus-dotnet/Corvus.JsonSchema

Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json.

Apache-2.0Auto-check passedDevelopment

Install Corvus Analyzers

skills CLI

$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -a claude-code

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

GitHub CLI

$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-analyzers --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/corvus-dotnet/Corvus.JsonSchema.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/corvus-analyzers .claude/skills/corvus-analyzers && 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 "corvus-analyzers" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-analyzers into .claude/skills/corvus-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-analyzers", 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/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-analyzers

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 corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -a codex

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

GitHub CLI

$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-analyzers --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/corvus-dotnet/Corvus.JsonSchema.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/corvus-analyzers .agents/skills/corvus-analyzers && 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 "corvus-analyzers" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-analyzers into .agents/skills/corvus-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-analyzers", 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 corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -a cursor

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

GitHub CLI

$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-analyzers --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/corvus-dotnet/Corvus.JsonSchema.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/corvus-analyzers .cursor/skills/corvus-analyzers && 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 "corvus-analyzers" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-analyzers into .cursor/skills/corvus-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-analyzers", 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/corvus-dotnet/Corvus.JsonSchema.git --path .github/skills/corvus-analyzers

--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 corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -a gemini-cli

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

GitHub CLI

$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-analyzers --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/corvus-dotnet/Corvus.JsonSchema.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/corvus-analyzers .gemini/skills/corvus-analyzers && 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 "corvus-analyzers" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-analyzers into .gemini/skills/corvus-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-analyzers", 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 corvus-dotnet/Corvus.JsonSchema corvus-analyzers

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 corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/corvus-dotnet/Corvus.JsonSchema.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/corvus-analyzers .github/skills/corvus-analyzers && 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 "corvus-analyzers" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-analyzers into .github/skills/corvus-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-analyzers", 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 corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -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 corvus-dotnet/Corvus.JsonSchema corvus-analyzers --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/corvus-dotnet/Corvus.JsonSchema.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/corvus-analyzers .opencode/skills/corvus-analyzers && 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 "corvus-analyzers" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-analyzers into .opencode/skills/corvus-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-analyzers", 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: corvus-analyzers
GitHub stars: 199
Token cost: ~876 tokens
SKILL.md length: 244 words
Files: 1
Skills in repo: 26
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json.

: understanding what each analyzer checks
SKILL.md covers Production Analyzers…, CTJ-NAV Refactoring, Migration Analyzers… and Analyzer Packaging Convention, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Writing code that passes analyzer checks

What it does

Corvus Analyzers is an agent skill from corvus-dotnet/Corvus.JsonSchema. Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json. Covers 10 production diagnostics (CTJ001-CTJ010) for correct and performant V5 code, the CTJ-NAV refactoring for navigating from types to JSON Schema definitions, and the analyzer packaging convention. USE FOR: understanding what each analyzer checks, writing code that passes analyzer checks, packaging analyzer DLLs. DO NOT USE FOR: the 25 migration analyzers (use corvus-v4-migration for the workflow and CVJ001-CVJ025 reference).

Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring. The repository describes itself as: Support for Json Schema validation and entity generation. The licence is Apache-2.0.

When your agent uses it

: understanding what each analyzer checks
Writing code that passes analyzer checks
Packaging analyzer DLLs
: the 25 migration analyzers (use corvus-v4-migration for the workflow and CVJ001-CVJ025 reference)

Example prompts

“/corvus-analyzers”

What it can do on your machine

Read from SKILL.md and the folder at commit b9e3040. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are csharp and xml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Corvus Analyzers loads about 876 tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 244 words of instructions outside code blocks.

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

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 corvus-dotnet/Corvus.JsonSchema at commit b9e3040, republished under its Apache-2.0 licence (© corvus-dotnet). 244 words, ~876 tokens.

Download SKILL.mdSave it as .claude/skills/corvus-analyzers/SKILL.md (or your agent's skills folder).

name: corvus-analyzers
description: Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json. Covers 10 production diagnostics (CTJ001-CTJ010) for correct and performant V5 code, the CTJ-NAV refactoring for navigating from types to JSON Schema definitions, and the analyzer packaging convention. USE FOR: understanding what each analyzer checks, writing code that passes analyzer checks, packaging analyzer DLLs. DO NOT USE FOR: the 25 migration analyzers (use corvus-v4-migration for the workflow and CVJ001-CVJ025 reference).

Corvus.Text.Json Analyzers

Production Analyzers (CTJ001-CTJ010)

These analyzers ship with the main library to ensure correct and performant usage.

ID	Summary	Severity
CTJ001	Prefer UTF-8 string literals (`"name"u8`) over string-based overloads	Warning
CTJ002	Remove unnecessary .NET type conversions	Warning
CTJ003	Use static lambdas in `Match<TOut>` for zero-allocation	Info
CTJ004	Missing `Dispose()` on `ParsedJsonDocument`	Warning
CTJ005	Missing `Dispose()` on `JsonWorkspace`	Warning
CTJ006	Missing `Dispose()` on `JsonDocumentBuilder`	Warning
CTJ007	Discarded `EvaluateSchema()` result	Warning
CTJ008	Prefer `NameEquals()` over `Name ==` for zero-allocation comparison	Info
CTJ009	Rent `Utf8JsonWriter` from workspace instead of creating new	Info
CTJ010	Prefer `ReadOnlyMemory`/`Span`-based `Parse` overloads	Info

Key Patterns

CTJ001 — UTF-8 literals:

csharp

// ❌ Triggers CTJ001
element.GetProperty("name");

// ✅ Preferred
element.GetProperty("name"u8);

CTJ004-006 — Dispose:

csharp

// ❌ Triggers CTJ004
var doc = ParsedJsonDocument<JsonElement>.Parse(json);

// ✅ Correct
using var doc = ParsedJsonDocument<JsonElement>.Parse(json);

CTJ008 — NameEquals:

csharp

// ❌ Triggers CTJ008
if (property.Name == "foo") { ... }

// ✅ Preferred — zero-allocation UTF-8 comparison
if (property.NameEquals("foo"u8)) { ... }

CTJ-NAV Refactoring

Navigate from a generated C# type to its source JSON Schema definition. This is a code action (refactoring), not a diagnostic — it appears in the lightbulb menu.

Migration Analyzers (CVJ001-CVJ025)

These are in a separate package (Corvus.Text.Json.Migration.Analyzers) and detect V4→V5 migration patterns. See the corvus-v4-migration skill for the workflow, and docs/MigrationAnalyzers.md for the full reference.

Analyzer Packaging Convention

Roslyn analyzer projects in this repo manually pack their DLL and dependency DLLs into analyzers/dotnet/cs instead of relying on normal build output:

xml

<!-- In the .csproj -->
<Target Name="PackAnalyzer" AfterTargets="Build">
  <!-- Copies DLLs into analyzers/dotnet/cs for NuGet packaging -->
</Target>

This is the same pattern used by both the V5 source generator (src/Corvus.Text.Json.SourceGenerator/) and the V4 source generator (src-v4/Corvus.Json.SourceGenerator/).

Suppressed Warnings

These warnings are suppressed project-wide — don't add #pragma warning disable for them:

JSON001, CS8500, IDE0065, IDE0290

Cross-References

For migration workflow using CVJ analyzers, see corvus-v4-migration
For dispose patterns (CTJ004-006), see corvus-parsed-documents-and-memory and corvus-mutable-documents
Full reference: docs/Analyzers.md, docs/MigrationAnalyzers.md

Files

Just SKILL.md in .github/skills/corvus-analyzers of corvus-dotnet/Corvus.JsonSchema.

Open the folder on GitHubat commit b9e3040

Compare with similar skills

Corvus Analyzers 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.

Corvus Analyzers compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Corvus Analyzers this skillcorvus-dotnet/Corvus.JsonSchema	199	—	~876	Automated safety check: Pass	Apache-2.0	today
Guidelinesakash-network/node	1.1k	22 repos	~577	Automated safety check: Pass	MIT	2 days ago
Component Refactoringlangflow-ai/langflow	156k	—	~3.5k	Automated safety check: Pass	MIT	today
Migrate Core Code to Submodulestinyhumansai/openhuman	42k	—	~2.6k	Automated safety check: Pass	GPL-3.0	today
Systematic Code Refactoringluongnv89/claude-howto	42k	—	~3k	Automated safety check: Pass	MIT	8 days ago
Codexskills-directory/skill-codex	1.5k	3 repos	~1.8k	Automated safety check: Pass	MIT	25 days ago

Similar skills

Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
1.1k GitHub starsUsed in 22 repos~577 tokens
DevelopmentAuto-check passed
Component Refactoring
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
156k GitHub stars~3.5k tokensUpdated today
DevelopmentAuto-check passed
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
42k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
42k GitHub stars~3k tokensUpdated 8 days ago
DevelopmentAuto-check passed
Codex
skills-directory/skill-codex
A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
1.5k GitHub starsUsed in 3 repos~1.8k tokens
DevelopmentAuto-check passed
Ponytail
DavidObando/gsharp
Forces the laziest solution that actually works, simplest, shortest, most minimal.
565 GitHub starsUsed in 8 repos~1.7k tokens
DevelopmentAuto-check passed

More from corvus-dotnet/Corvus.JsonSchema

All 26 skills in this repo

Corvus Benchmarks
corvus-dotnet/Corvus.JsonSchema
Run, interpret, and maintain BenchmarkDotNet benchmarks for JSON Schema validation and query languages.
199 GitHub stars~1.2k tokensUpdated today
Auto-check passed
Corvus Bowtie Testing
corvus-dotnet/Corvus.JsonSchema
Test Corvus.JsonSchema against the JSON Schema Test Suite using Bowtie, the cross-implementation meta-validator.
199 GitHub stars~1.4k tokensUpdated today
Auto-check passed
Corvus Buffer And Pooling
corvus-dotnet/Corvus.JsonSchema
Write allocation-efficient buffer code in Corvus.JsonSchema using the codebase's established three-tier pooling pattern: stackalloc → ArrayPool → ThreadStatic caches.
199 GitHub stars~2.9k tokensUpdated today
Auto-check passed
Corvus Bytes To Bytes
corvus-dotnet/Corvus.JsonSchema
Eliminate hand-rolled POCO record<-document string seams — types/paths that materialize a managed string (or List<string/Dictionary) between a bytes SOURCE (a parsed UTF-8 body, a DB column, a…
199 GitHub stars~3k tokensUpdated today
Auto-check passed
Corvus Codegen
corvus-dotnet/Corvus.JsonSchema
Generate strongly-typed C from JSON Schema using the Roslyn source generator or the corvusjson CLI tool.
199 GitHub stars~2.1k tokensUpdated today
Auto-check passed
Corvus Ctj Handler Implementation
corvus-dotnet/Corvus.JsonSchema
Implement OpenAPI server handlers using Corvus.Text.Json generated types.
199 GitHub stars~4.4k tokensUpdated today
Auto-check passed

Questions about Corvus Analyzers

What does Corvus Analyzers do?

Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json. JsonSchema.Json.

When should I use Corvus Analyzers?

Corvus Analyzers fits situations like: : understanding what each analyzer checks; writing code that passes analyzer checks; packaging analyzer DLLs; : the 25 migration analyzers (use corvus-v4-migration for the workflow and CVJ001-CVJ025 reference).

How do I install Corvus Analyzers in Claude Code?

Run `npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -a claude-code`. Or copy the skill folder (.github/skills/corvus-analyzers in corvus-dotnet/Corvus.JsonSchema) into .claude/skills/corvus-analyzers in your project. Claude Code loads it when a task matches its description.

How do I install Corvus Analyzers in Codex?

Run `npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-analyzers -a codex`. Or copy the skill folder (.github/skills/corvus-analyzers in corvus-dotnet/Corvus.JsonSchema) into .agents/skills/corvus-analyzers in your project. Codex loads it when a task matches its description.

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

What does Corvus Analyzers need to run?

SKILL.md names no scripts, command-line tools or credentials: Corvus Analyzers is instructions for the agent only.

Does Corvus Analyzers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Corvus Analyzers 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 Corvus Analyzers use?

Corvus Analyzers is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Corvus Analyzers use?

About 876 tokens (SKILL.md is roughly 3.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 Corvus Analyzers?

Skills that share tags, products or a category with Corvus Analyzers: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars) and Systematic Code Refactoring (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Corvus Analyzers?

corvus-dotnet (a GitHub organization) maintains it in corvus-dotnet/Corvus.JsonSchema, which has 199 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Corvus Analyzers

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Corvus.Text.Json Analyzers

Production Analyzers (CTJ001-CTJ010)

Key Patterns

CTJ-NAV Refactoring

Migration Analyzers (CVJ001-CVJ025)

Analyzer Packaging Convention

Suppressed Warnings

Cross-References

Files

Compare with similar skills

Similar skills

More from corvus-dotnet/Corvus.JsonSchema

Related

Questions about Corvus Analyzers