Nx Generate
nomcopter/react-mosaic
Generate code using nx generators. An agent skill from nomcopter/react-mosaic.
Implement and extend JSON Schema keywords in the Corvus code generation system and the runtime evaluator.
Install Corvus Keywords And Validation
$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-keywords-and-validation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-keywords-and-validation .claude/skills/corvus-keywords-and-validation && rm -rf skills-srcUse ~/.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/
Install the "corvus-keywords-and-validation" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-keywords-and-validation into .claude/skills/corvus-keywords-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-keywords-and-validation", 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 install https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-keywords-and-validationType 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.
$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-keywords-and-validation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-keywords-and-validation .agents/skills/corvus-keywords-and-validation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "corvus-keywords-and-validation" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-keywords-and-validation into .agents/skills/corvus-keywords-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-keywords-and-validation", 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.
$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-keywords-and-validation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-keywords-and-validation .cursor/skills/corvus-keywords-and-validation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "corvus-keywords-and-validation" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-keywords-and-validation into .cursor/skills/corvus-keywords-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-keywords-and-validation", 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 https://github.com/corvus-dotnet/Corvus.JsonSchema.git --path .github/skills/corvus-keywords-and-validation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-keywords-and-validation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-keywords-and-validation .gemini/skills/corvus-keywords-and-validation && rm -rf skills-srcUse ~/.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/
Install the "corvus-keywords-and-validation" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-keywords-and-validation into .gemini/skills/corvus-keywords-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-keywords-and-validation", 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.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-keywords-and-validationInstalls 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).
$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ 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-keywords-and-validation .github/skills/corvus-keywords-and-validation && rm -rf skills-srcUse ~/.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/
Install the "corvus-keywords-and-validation" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-keywords-and-validation into .github/skills/corvus-keywords-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-keywords-and-validation", 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.
$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-keywords-and-validation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-keywords-and-validation .opencode/skills/corvus-keywords-and-validation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "corvus-keywords-and-validation" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-keywords-and-validation into .opencode/skills/corvus-keywords-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-keywords-and-validation", 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-keywords-and-validation- GitHub stars
- 199
- Token cost
- ~1.7k tokens
- SKILL.md length
- 618 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implement and extend JSON Schema keywords in the Corvus code generation system and the runtime evaluator.
- Works in 4 steps: Schema structure — type shape:… → Validation — runtime checks:… → Annotation & documentation —… → …
- : adding new JSON Schema keywords
- SKILL.md covers Keyword Architecture, Vocabularies, Validation Handler Priorities and Draft-Specific Keyword…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Corvus Keywords And Validation is an agent skill from corvus-dotnet/Corvus.JsonSchema. Implement and extend JSON Schema keywords in the Corvus code generation system and the runtime evaluator. Covers the IKeyword interface, behavioral marker interfaces, vocabulary registration, draft-specific keyword variations (Draft 4 through 2020-12), where assertions are implemented (SchemaCompiler/Evaluator), custom keyword extension points, and the TypeDeclaration data structure. USE FOR: adding new JSON Schema keywords, modifying validation behavior, understanding keyword evolution across drafts, extending…
Its SKILL.md is about 1.7k 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 Project scaffolding. The repository describes itself as: Support for Json Schema validation and entity generation. The licence is Apache-2.0.
When your agent uses it
- : adding new JSON Schema keywords
- Modifying validation behavior
- Understanding keyword evolution across drafts
- Extending the code generation engine
Example prompts
- “/corvus-keywords-and-validation”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Schema structure — type shape: ISubschemaTypeBuilderKeyword, ILocalSubschemaRegistrationKeyword, IPropertySubchemaProviderKeyword
- Validation — runtime checks: IObjectPropertyValidationKeyword, IValueKindValidationKeyword, INumericValidationKeyword…
- Annotation & documentation — IAnnotationProducingKeyword, IShortDocumentationProviderKeyword, ILongDocumentationProviderKeyword…
- References & identity — IRefKeyword, IDynamicRefKeyword, IIdKeyword, IAnchorKeyword, ISchemaKeyword
What it can do on your machine
Read from SKILL.md and the folder at commit 973097f. 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.
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 Keywords And Validation loads about 1.7k tokens when it runs. Until then it costs about 182 tokens; SKILL.md has 618 words of instructions outside code blocks.
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 973097f, republished under its Apache-2.0 licence (© corvus-dotnet). 618 words, ~1,714 tokens.
Download SKILL.mdSave it as
.claude/skills/corvus-keywords-and-validation/SKILL.md (or your agent's skills folder).- name
- corvus-keywords-and-validation
- description
- Implement and extend JSON Schema keywords in the Corvus code generation system and the runtime evaluator. Covers the IKeyword interface, behavioral marker interfaces, vocabulary registration, draft-specific keyword variations (Draft 4 through 2020-12), where assertions are implemented (SchemaCompiler/Evaluator), custom keyword extension points, and the TypeDeclaration data structure. USE FOR: adding new JSON Schema keywords, modifying validation behavior, understanding keyword evolution across drafts, extending the code generation engine, understanding vocabularies. DO NOT USE FOR: using generated types (use corvus-codegen), standalone evaluator internals (use corvus-standalone-evaluator).
Keywords and Validation Handlers
Keyword Architecture
Keywords are stateless singletons implementing IKeyword plus behavioral marker interfaces.
IKeyword Interface
Every keyword implements:
Keywordproperty — the JSON property name (e.g.,"type","maxLength")- Behavioral marker interfaces that declare how the keyword participates in schema processing
Behavioural Marker Interface Categories (25+)
- Schema structure — type shape:
ISubschemaTypeBuilderKeyword,ILocalSubschemaRegistrationKeyword,IPropertySubchemaProviderKeyword - Validation — runtime checks:
IObjectPropertyValidationKeyword,IValueKindValidationKeyword,INumericValidationKeyword,IStringValidationKeyword,IArrayValidationKeyword - Annotation & documentation —
IAnnotationProducingKeyword,IShortDocumentationProviderKeyword,ILongDocumentationProviderKeyword,IDefaultValueProviderKeyword,IExamplesProviderKeyword,INonStructuralKeyword,IDeprecatedKeyword - References & identity —
IRefKeyword,IDynamicRefKeyword,IIdKeyword,IAnchorKeyword,ISchemaKeyword
Vocabularies
Vocabularies are modular sets of keywords (introduced formally in Draft 2019-09):
- Core —
$id,$schema,$ref,$defs - Applicator —
allOf,anyOf,oneOf,if/then/else,properties,items - Validation —
type,minimum,maximum,pattern,required - MetaData —
title,description,default,examples - Format —
formatkeyword (annotation in 2019-09+, assertion in earlier drafts) - Content —
contentEncoding,contentMediaType,contentSchema - Unevaluated —
unevaluatedProperties,unevaluatedItems(2019-09+)
Validation Handler Priorities
Handlers execute in strict priority order (defined in ValidationPriorities static class in src-v4/Corvus.Json.CodeGeneration/.../Validation/ValidationPriorities.cs, shared by both V4 and V5):
| Priority | Name | Value | Purpose |
|---|---|---|---|
| First | First | 0 | Must run before everything |
| CoreType | CoreType | 1,000 | Basic type checking (type keyword) |
| Default | Default | ~2.1 billion (uint.MaxValue / 2) | Standard validation (min/max, pattern, etc.) |
| Composition | Composition | Default + 1,000 | allOf, anyOf, oneOf, not |
| AfterComposition | AfterComposition | Composition + 1,000 | Keywords that depend on composition results (arrays, objects) |
| Last | Last | uint.MaxValue | Final cleanup, unevaluated properties/items |
The large gap between CoreType (1,000) and Default (~2.1B) leaves room for future priorities without redefining existing values.
Draft-Specific Keyword Variations
Keywords change behavior across JSON Schema drafts:
| Keyword | Draft 4 | Draft 6+ |
|---|---|---|
exclusiveMaximum | Boolean modifier on maximum | Standalone number |
exclusiveMinimum | Boolean modifier on minimum | Standalone number |
items | Single schema or array | Single schema only in 2020-12 (prefixItems for array) |
additionalItems | Used with array items | Removed in 2020-12 |
$ref | Replaces all siblings | Coexists with siblings in 2019-09+ |
Custom Keyword Extension Points (8)
The code generation engine exposes extension points at different phases:
- Schema discovery — register custom schema locations
- Type declaration building — modify type declarations during construction
- Type reduction — control how trivial subschemas are collapsed
- Validation handler registration — add custom validation code emitters
- Property handler — customize how object properties are processed
- Array handler — customize array item processing
- Format handler — add custom format validators
- Composition handler — customize allOf/anyOf/oneOf/not processing
Show full SKILL.md (249 more words)Show less
Where Validation Lives
Validation handlers no longer exist. Keywords are declared for the type builder (so generated types
reflect them), but every assertion is implemented once in the runtime evaluator
(src/Corvus.Text.Json/Corvus/Text/Json/RuntimeEvaluator, namespace Corvus.Text.Json.RuntimeEvaluator, in the
Corvus.Text.Json assembly), which generated types, standalone evaluators, the Validator and
the CLI all use:
Compilation/SchemaCompiler.cs—CompileNodereads each keyword into aSchemaNode(dispatch by keyword name length, then bytes), then whole-graph passes (dynamic refs, tracking, marking,$refelision, discriminators, plans, flags).Evaluation/Evaluator.cs— the assertions, generic overFastMode/CollectingModeand the document access type; report results with the keyword name through the collector.- Tests:
tests/Corvus.Text.Json.RuntimeEvaluator.Tests(unit + JSON Schema Test Suite), plus the generated suite projects, which now run the same engine through generated types.
The generator emits one CorvusJsonSchemaProgram per compilation (RuntimeProgramGenerator.cs) with an
entry point per type: pre-compiled as an image when the host supplies Options.ProgramCompiler (the CLI),
else holding the schema documents for compilation on first use; see docs/StandaloneEvaluatorInternals.md.
TypeDeclaration
The central data structure representing a resolved JSON Schema as a C# type:
- Holds the schema keywords, their values, and resolved references
- Tracks the type's place in the inheritance/composition hierarchy
- Type reduction collapses trivial subschemas for leaner generated code
Common Pitfalls
- Draft awareness: Always check which draft(s) your keyword applies to. A keyword may have different semantics or not exist in certain drafts.
- Stateless keywords: Keywords must be stateless singletons. State lives in
TypeDeclaration.
Cross-References
- For code generation, see
corvus-codegen - For the evaluation program and evaluator-only generation, see
corvus-standalone-evaluator - Full guide:
docs/AddingKeywords.md,docs/ValidationHandlerGuide.md,docs/RuntimeEvaluator.md
© corvus-dotnet, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/corvus-keywords-and-validation of corvus-dotnet/Corvus.JsonSchema.
Open the folder on GitHubat commit 973097f
Compare with similar skills
Corvus Keywords And Validation 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Corvus Keywords And Validation this skillcorvus-dotnet/Corvus.JsonSchema | 199 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Nx Generatenomcopter/react-mosaic | 4.8k | 7 repos | ~1.9k | Automated safety check: Pass | Custom licence | |
| PonytailDavidObando/gsharp | 564 | 8 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Run Nx Generatornrwl/nx | 29k | 2 repos | ~592 | Automated safety check: Notes | MIT | |
| Conductor Setupgemini-cli-extensions/conductor | 3.8k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Mirage VFS Adapter Authoringstrukto-ai/mirage | 3.7k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Ponytail
DavidObando/gsharp
Forces the laziest solution that actually works, simplest, shortest, most minimal.
Run Nx Generator
nrwl/nx
Run Nx generators with prioritization for workspace-plugin generators.
Conductor Setup
gemini-cli-extensions/conductor
Scaffolds the project and sets up the Conductor environment.
Mirage VFS Adapter Authoring
strukto-ai/mirage
Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.
Siteboon Backend Module Standards
siteboon/claudecodeui
Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.
More from corvus-dotnet/Corvus.JsonSchema
All 28 skills in this repoCorvus Analyzers
corvus-dotnet/Corvus.JsonSchema
Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json.
Corvus Benchmarks
corvus-dotnet/Corvus.JsonSchema
Run, interpret, and maintain BenchmarkDotNet benchmarks for JSON Schema validation and query languages.
Corvus Bowtie Testing
corvus-dotnet/Corvus.JsonSchema
Test Corvus.JsonSchema against the JSON Schema Test Suite using Bowtie, the cross-implementation meta-validator.
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.
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…
Corvus Codegen
corvus-dotnet/Corvus.JsonSchema
Generate strongly-typed C from JSON Schema using the Roslyn source generator or the corvusjson CLI tool.
Related
Categories
Questions about Corvus Keywords And Validation
What does Corvus Keywords And Validation do?
Implement and extend JSON Schema keywords in the Corvus code generation system and the runtime evaluator. JsonSchema. Implement and extend JSON Schema keywords in the Corvus code generation system and the runtime evaluator.
When should I use Corvus Keywords And Validation?
Corvus Keywords And Validation fits situations like: : adding new JSON Schema keywords; modifying validation behavior; understanding keyword evolution across drafts; extending the code generation engine.
How do I install Corvus Keywords And Validation in Claude Code?
Run `npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a claude-code`. Or copy the skill folder (.github/skills/corvus-keywords-and-validation in corvus-dotnet/Corvus.JsonSchema) into .claude/skills/corvus-keywords-and-validation in your project. Claude Code loads it when a task matches its description.
How do I install Corvus Keywords And Validation in Codex?
Run `npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-keywords-and-validation -a codex`. Or copy the skill folder (.github/skills/corvus-keywords-and-validation in corvus-dotnet/Corvus.JsonSchema) into .agents/skills/corvus-keywords-and-validation in your project. Codex loads it when a task matches its description.
Can I use Corvus Keywords And Validation 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-keywords-and-validation -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-keywords-and-validation, .gemini/skills/corvus-keywords-and-validation, .github/skills/corvus-keywords-and-validation and .opencode/skills/corvus-keywords-and-validation in your project.
What does Corvus Keywords And Validation need to run?
SKILL.md names no scripts, command-line tools or credentials: Corvus Keywords And Validation is instructions for the agent only.
Does Corvus Keywords And Validation 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 Keywords And Validation 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 Keywords And Validation use?
Corvus Keywords And Validation 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 Keywords And Validation use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Keywords And Validation?
Skills that share tags, products or a category with Corvus Keywords And Validation: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 564 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Corvus Keywords And Validation?
corvus-dotnet (a GitHub organization) maintains it in corvus-dotnet/Corvus.JsonSchema, which has 199 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 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.