Agent skill

Corvus YAML

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

Convert between YAML 1.2 and JSON using the high-performance ref struct tokenizer.

Apache-2.0Auto-check passedTesting & QA

Install Corvus YAML

skills CLI

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

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

GitHub CLI

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

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-yaml -a codex

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

GitHub CLI

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

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

GitHub CLI

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

--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-yaml -a gemini-cli

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

GitHub CLI

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

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

At a glance

Convert between YAML 1.2 and JSON using the high-performance ref struct tokenizer.

: YAML-to-JSON conversion
SKILL.md covers Overview, Two Packages, Basic Usage and Schema Modes, plus 5 more sections
Calls dotnet
JSON-to-YAML conversion

What it does

Corvus YAML is an agent skill from corvus-dotnet/Corvus.JsonSchema. Convert between YAML 1.2 and JSON using the high-performance ref struct tokenizer. Covers the two packages (Corvus.Text.Json.Yaml for full integration, Corvus.Yaml.SystemTextJson for System.Text.Json-only), YAML→JSON and JSON→YAML conversion, schema modes, anchor/alias support, multi-document streams, Utf8YamlWriter, and 100% yaml-test-suite JSON-testable conformance (373 of 402 tests). USE FOR: YAML-to-JSON conversion, JSON-to-YAML conversion, understanding the tokenizer architecture, troubleshooting YAML…

Its SKILL.md is about 1.2k 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 Testing & QA, covering Test generation. The repository describes itself as: Support for Json Schema validation and entity generation. The licence is Apache-2.0.

When your agent uses it

: YAML-to-JSON conversion
JSON-to-YAML conversion
Understanding the tokenizer architecture
Troubleshooting YAML parsing issues

Example prompts

“/corvus-yaml”

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
Shell commands in SKILL.md call:
- dotnet
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 YAML loads about 1.2k tokens when it runs. Until then it costs about 150 tokens; SKILL.md has 337 words of instructions outside code blocks.

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

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). 337 words, ~1,172 tokens.

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

name: corvus-yaml
description: Convert between YAML 1.2 and JSON using the high-performance ref struct tokenizer. Covers the two packages (Corvus.Text.Json.Yaml for full integration, Corvus.Yaml.SystemTextJson for System.Text.Json-only), YAML→JSON and JSON→YAML conversion, schema modes, anchor/alias support, multi-document streams, Utf8YamlWriter, and 100% yaml-test-suite JSON-testable conformance (373 of 402 tests). USE FOR: YAML-to-JSON conversion, JSON-to-YAML conversion, understanding the tokenizer architecture, troubleshooting YAML parsing issues. DO NOT USE FOR: JSON-only workflows with no YAML involvement.

YAML 1.2 ↔ JSON Conversion

Overview

Conformance: 100% of JSON-testable cases — 373 of 402 total (279 valid + 94 error). The remaining 29 cases exercise YAML features with no JSON equivalent.

The YAML converter operates as a zero-allocation ref struct tokenizer on UTF-8 bytes, streaming tokens directly into a Utf8JsonWriter.

Two Packages

Package	Purpose
`Corvus.Text.Json.Yaml`	Full Corvus integration — returns `ParsedJsonDocument<T>`
`Corvus.Yaml.SystemTextJson`	System.Text.Json only — writes to `Utf8JsonWriter`

Basic Usage

YAML → JSON

csharp

// Full Corvus integration — returns ParsedJsonDocument<T>
using ParsedJsonDocument<JsonElement> doc = YamlDocument.Parse<JsonElement>(yamlBytes);
JsonElement root = doc.RootElement;

// System.Text.Json only — returns JsonDocument
JsonDocument doc = YamlDocument.Parse(yamlBytes);

// Get JSON string from YAML
string json = YamlDocument.ConvertToJsonString(yamlBytes);

JSON → YAML

csharp

// Convert a JSON element to a YAML string (static method on YamlDocument)
string yaml = YamlDocument.ConvertToYamlString(jsonElement);

// Convert to YAML, writing to an IBufferWriter<byte>
YamlDocument.ConvertToYaml(jsonElement, bufferWriter);

// Convert to YAML, writing to a Stream
YamlDocument.ConvertToYaml(jsonElement, utf8Stream);

KYAML output

KYAML (Kubernetes KEP-5295) is a strict subset of YAML 1.2: explicit { } / [ ] delimiters laid out across indented lines, string values always double-quoted, numbers/ booleans/null bare, keys quoted only when ambiguous, trailing comma after every element. Output is always valid YAML 1.2 (read it back with YamlDocument.Parse, no config needed).

Enable it on any ConvertToYaml* overload (or Utf8YamlWriter) via the options:

csharp

// Preset (easiest):
string kyaml = YamlDocument.ConvertToYamlString(json, YamlWriterOptions.Kyaml);

// Or set the format explicitly:
var options = new YamlWriterOptions { Format = YamlWriterFormat.Kyaml };

Implemented entirely in Utf8YamlWriter (gated on YamlWriterFormat.Kyaml); the JSON→YAML converter is format-agnostic. Output is canonical (non-"cuddled") KYAML.

Schema Modes

Four YAML schema modes control how scalar values are interpreted:

Mode	Description
Core	YAML 1.2 Core Schema (default)
JSON	JSON-compatible — strings, numbers, booleans, null only
Failsafe	All scalars as strings
Yaml11	YAML 1.1 compatibility (yes/no/on/off booleans, sexagesimal integers, merge keys)

Features

Anchors & aliases: Full support for &anchor and *alias references
Multi-document streams: Processes --- / ... document boundaries
Block & flow styles: All YAML block and flow collection styles
Tag resolution: %TAG directives, standard !! tags, custom tags

Running Tests

powershell

dotnet test --project tests\Corvus.Text.Json.Yaml.Tests --filter "TestCategory!=failing&TestCategory!=outerloop"

Key Implementation Details

These are important if you're modifying the YAML converter:

FinishAnchor: Must not clear _activeAnchorNameStart when hasAnchor=false
Block scalars: Must check for document markers (---/...) at column 0
%TAG !! redefinition: Makes !!name tags non-standard
Float normalization: Written via Utf8Parser + WriteNumberValue for consistent output

Common Pitfalls

Encoding: The tokenizer expects UTF-8 bytes. Pass ReadOnlySpan<byte> for best performance.
Multi-document: A YAML stream may contain multiple documents. The converter handles them, but the consumer must be aware.
Scalar resolution: In Core schema mode, strings like true, false, null, and numbers are auto-resolved. Use Failsafe mode to keep everything as strings.

Cross-References

For parsed document handling, see corvus-parsed-documents-and-memory
For building/testing, see corvus-build-and-test
Full guide: docs/Yaml.md

Files

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

Open the folder on GitHubat commit b9e3040

Compare with similar skills

Corvus YAML 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 YAML compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Corvus YAML this skillcorvus-dotnet/Corvus.JsonSchema	199	—	~1.2k	Automated safety check: Pass	Apache-2.0	yesterday
Emcaklofas/kicad-happy	1.4k	1 repos	~2.8k	Automated safety check: Pass	MIT	2 days ago
Swig Testswig/swig	6.3k	—	~2.3k	Automated safety check: Pass	Custom licence	2 days ago
Generate Test Cases342164796/generate-test-cases	119	1 repos	~2.9k	Automated safety check: Pass	None	6 mo ago
Verify Cc Safety Netkenryu42/cc-safety-net	1.6k	—	~2k	Automated safety check: Pass	MIT	yesterday
Wioworkersio/skills	190	—	~5.8k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Emc
aklofas/kicad-happy
EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…
1.4k GitHub starsUsed in 1 repo~2.8k tokens
Testing & QAAuto-check passed
Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
6.3k GitHub stars~2.3k tokensUpdated 2 days ago
Testing & QAAuto-check passed
Generate Test Cases
342164796/generate-test-cases
自主学习型测试文档生成器。从需求文档（Markdown）生成测试用例 XMind 文件，支持持久化记忆和持续学习。当用户提到"生成测试用例"、"根据需求生成测试"时触发。
119 GitHub starsUsed in 1 repo~2.9k tokens
Testing & QAAuto-check passed
Verify Cc Safety Net
kenryu42/cc-safety-net
Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence.
1.6k GitHub stars~2k tokensUpdated yesterday
Testing & QAAuto-check passed
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
190 GitHub stars~5.8k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
File Server
microsoft/WindowsProtocolTestSuites
Official
ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…
567 GitHub stars~4.1k tokensUpdated 23 days ago
Testing & QAAuto-check passed

More from corvus-dotnet/Corvus.JsonSchema

All 26 skills in this repo

Corvus Analyzers
corvus-dotnet/Corvus.JsonSchema
Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json.
199 GitHub stars~876 tokensUpdated yesterday
Auto-check passed
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 yesterday
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 yesterday
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 yesterday
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 yesterday
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 yesterday
Auto-check passed

Questions about Corvus YAML

What does Corvus YAML do?

Convert between YAML 1.2 and JSON using the high-performance ref struct tokenizer. JsonSchema.2 and JSON using the high-performance ref struct tokenizer.

When should I use Corvus YAML?

Corvus YAML fits situations like: : YAML-to-JSON conversion; JSON-to-YAML conversion; understanding the tokenizer architecture; troubleshooting YAML parsing issues.

How do I install Corvus YAML in Claude Code?

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

How do I install Corvus YAML in Codex?

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

Can I use Corvus YAML 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-yaml -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-yaml, .gemini/skills/corvus-yaml, .github/skills/corvus-yaml and .opencode/skills/corvus-yaml in your project.

What does Corvus YAML need to run?

Going by SKILL.md and its folder, Corvus YAML needs the command-line tools its instructions call (dotnet).

Does Corvus YAML 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 YAML 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 YAML use?

Corvus YAML 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 YAML use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 YAML?

Skills that share tags, products or a category with Corvus YAML: Emc (aklofas/kicad-happy, 1.4k stars), Swig Test (swig/swig, 6.3k stars), Generate Test Cases (342164796/generate-test-cases, 119 stars) and Verify Cc Safety Net (kenryu42/cc-safety-net, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Corvus YAML?

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 YAML

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

YAML 1.2 ↔ JSON Conversion

Overview

Two Packages

Basic Usage

YAML → JSON

JSON → YAML

KYAML output

Schema Modes

Features

Running Tests

Key Implementation Details

Common Pitfalls

Cross-References

Files

Compare with similar skills

Similar skills

More from corvus-dotnet/Corvus.JsonSchema

Related

Questions about Corvus YAML