Chroma Vector Database
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
Construct instances of generated Corvus strongly-typed models (DTOs, request/response bodies, discriminated-union variants) allocation-free, without composing or parsing JSON.
$ npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-typed-model-construction -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-typed-model-construction --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-typed-model-construction .claude/skills/corvus-typed-model-construction && 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-typed-model-construction" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-typed-model-construction into .claude/skills/corvus-typed-model-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-typed-model-construction", 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-typed-model-constructionType 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-typed-model-construction -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-typed-model-construction --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-typed-model-construction .agents/skills/corvus-typed-model-construction && 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-typed-model-construction" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-typed-model-construction into .agents/skills/corvus-typed-model-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-typed-model-construction", 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-typed-model-construction -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-typed-model-construction --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-typed-model-construction .cursor/skills/corvus-typed-model-construction && 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-typed-model-construction" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-typed-model-construction into .cursor/skills/corvus-typed-model-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-typed-model-construction", 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-typed-model-construction--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-typed-model-construction -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install corvus-dotnet/Corvus.JsonSchema corvus-typed-model-construction --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-typed-model-construction .gemini/skills/corvus-typed-model-construction && 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-typed-model-construction" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-typed-model-construction into .gemini/skills/corvus-typed-model-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-typed-model-construction", 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-typed-model-constructionInstalls 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-typed-model-construction -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-typed-model-construction .github/skills/corvus-typed-model-construction && 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-typed-model-construction" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-typed-model-construction into .github/skills/corvus-typed-model-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-typed-model-construction", 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-typed-model-construction -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-typed-model-construction --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-typed-model-construction .opencode/skills/corvus-typed-model-construction && 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-typed-model-construction" agent skill from https://github.com/corvus-dotnet/Corvus.JsonSchema/tree/main/.github/skills/corvus-typed-model-construction into .opencode/skills/corvus-typed-model-construction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corvus-typed-model-construction", 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.
corvus-typed-model-constructionConstruct instances of generated Corvus strongly-typed models (DTOs, request/response bodies, discriminated-union variants) allocation-free, without composing or parsing JSON.
Corvus Typed Model Construction is an agent skill from corvus-dotnet/Corvus.JsonSchema. Construct instances of generated Corvus strongly-typed models (DTOs, request/response bodies, discriminated-union variants) allocation-free, without composing or parsing JSON. Covers the Create() / Build() / CreateBuilder() / CreateBuilder<TContext() factories, threading state through a context tuple with STATIC lambdas to avoid closures, the JsonElement.Source ref-safety trap and its fix, avoiding interim materializations, and building discriminated-union bodies. USE FOR: building a generated model from native…
Its SKILL.md is about 2.4k 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 AI & LLM Engineering, covering Embeddings. The repository describes itself as: Support for Json Schema validation and entity generation. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 973097f. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are csharp).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Corvus Typed Model Construction loads about 2.4k tokens when it runs. Until then it costs about 234 tokens; SKILL.md has 839 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.
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.
The full file from corvus-dotnet/Corvus.JsonSchema at commit 973097f, republished under its Apache-2.0 licence (© corvus-dotnet). 839 words, ~2,440 tokens.
.claude/skills/corvus-typed-model-construction/SKILL.md (or your agent's skills folder).Generated Corvus types ([JsonSchemaTypeGenerator] / openapi-client / openapi-server
models) are built through value-typed factories that write once into a pooled arena. The
goal is to go from native values (int, string, a JsonElement) straight into the model
with no interim string/JSON, no ParseValue, and no closure allocation.
// ❌ interim string + parse + re-validate. Do not build request/response bodies this way.
var body = $$"""{"mode":"Rewind","targetCursor":{{n}}}""";
Models.ResumeRequest req = JsonElement.ParseValue(body);Use the generated factories instead.
| Factory | Returns | Use when |
|---|---|---|
T.Build(field: v, …) | T.Source (lazy) | The default. Native values — including a JsonElement/array — passed straight in. Hand the Source to a consumer that materializes it once (a generated client/handler method). No workspace, no closure. |
T.Build(static (ref T.Builder b) => b.Create(…)) | T.Source (lazy) | No fields to set (e.g. a const-only union variant), or you need imperative logic. Lambda MUST be static. |
T.CreateBuilder(ws, field: v, …) then .RootElement | T (immutable, in ws) | Only when you actually need a materialized value (e.g. to read it back, or store it). Not needed just to pass to a consumer. |
T.CreateBuilder<TContext>(ws, ctx, static (in TContext ctx, ref T.Builder b) => …) then .RootElement | T | Materializing while threading runtime values into a builder loop/conditional. The form the JMESPath/Jsonata/OpenApi generators emit. |
T.CreateBuilder<TContext>(ws, in T.Source<TContext> body) then .RootElement | T | Materializing a body you already assembled closure-free as a Source<TContext>. Usually you don't call this directly — the generated …Result.Ok<TContext>(T.Source<TContext> body, ws) does, in a single pass. See corvus-builder-context-threading. |
Default to T.Build(field: v, …) — it is lazy and the consumer materializes it directly
into its own buffer (one pass, no interim document). You almost never need CreateBuilder +
.RootElement; reach for it only when you genuinely need a materialized value in hand.
Reaching a server result factory closure-free: build the body as a context-threaded T.Source<TContext>
(T.Build<TContext>(in ctx, …), the context a RefTuple) and hand it to the generic …Result.Ok<TContext>(body, ws)
overload — one closure-free materialization. Do not CreateBuilder<TContext>(…).RootElement then pass the immutable
to the non-generic Ok (that re-materializes). Full detail: corvus-builder-context-threading.
// ✅ lazy, no workspace, no materialization — pass the builder straight to the client
await client.ResumeRunAsync(runId, RewindResume.Build(targetCursor), ct); // int
await client.CancelRunAsync(runId, CancelRequest.Build(reason), ct); // string
using var doc = ParsedJsonDocument<JsonElement>.Parse(File.ReadAllBytes(path));
await client.ResumeRunAsync(runId, SkipResume.Build(skipOutputs: doc.RootElement), ct); // JsonElement, passed directlyDon't hand-roll the Source constructor when Build covers it. A plain field set is
T.Build(field: v, …). Reach for the raw new T.Source((ref T.Builder b) => b.Create(…))
constructor only for genuine imperative logic — not to set a couple of fields. (Older code in the
tree uses the constructor form for simple bodies; prefer Build.)
// ❌ hand-rolled constructor for a plain field set
var body = new Models.MemberWrite.Source((ref Models.MemberWrite.Builder b) => b.Create(value: v, dimension: d));
// ✅ the Build factory
var body = Models.MemberWrite.Build(value: v, dimension: d);Build takes its fields by in, so consume its result in place — don't return it from a
helper. Because Build(in field, …) holds a ref to each argument, its Source cannot escape
the method that built it: pass it directly to the consumer in the same expression (the common
case). Wrapping Build in a method that returns the Source fails with CS8347 / CS8156 ("may
expose variables … outside their declaration scope" / "cannot be … returned by reference"). If you
want a named local, build and consume it in the same scope.
// ✅ consumed in place
await client.AddAdministratorAsync(baseId, Models.MemberWrite.Build(value: v, dimension: d), ct);
// ❌ returning Build's result escapes the in-ref (CS8347/CS8156)
static Models.MemberWrite.Source Member(string d, string v) => Models.MemberWrite.Build(value: v, dimension: d);JsonElement.Source is a ref struct created from in JsonElement — it holds a ref to the
element. Passing a JsonElement directly as an argument to a Build(in …)/CreateBuilder(in …)
factory is fine (the factory call's scope keeps the source document alive). What fails is
capturing a JsonElement in a (non-static) builder lambda — the captured ref escapes into
the closure and the compiler rejects it:
// ❌ CS8168 / CS8347 / CS8350 — outputs is captured; its ref escapes the closure
JsonElement outputs = doc.RootElement;
var src = new SkipResume.Source((ref SkipResume.Builder b) => b.Create(skipOutputs: outputs));
// ✅ pass it to the native-field factory instead — no lambda, no capture
var src = SkipResume.Build(skipOutputs: doc.RootElement);If you genuinely need imperative building and a threaded JsonElement, use the TContext
form so the value flows through scoped in rather than a closure:
var value = T.CreateBuilder(
workspace,
(src: someElement, ws: workspace),
static (in (JsonElement src, JsonWorkspace ws) ctx, ref T.Builder b) => { /* use ctx.src */ }).RootElement;Always make builder lambdas static and thread state via the context tuple — a non-static
lambda allocates a closure and reintroduces the capture/escape problem.
Build the variant, not the union; the variant Source implicitly converts to the union's
(non-generic) Source, so you pass the builder straight to the consumer — no materialization:
// RewindResume.Source / StatePatchResume.Source --> ResumeRequest.Source (implicit) --> client
await client.ResumeRunAsync(runId, RewindResume.Build(targetCursor), ct);
await client.ResumeRunAsync(runId, StatePatchResume.Build(patchArray), ct);const-discriminated variants set their own discriminator inside Build/Create, so you never
set mode (etc.) yourself.
Caveat (rare): a variant's Source<TContext> does NOT implicitly convert to the union's
non-generic Source. So if you must use the TContext threading form for a union body,
materialize that variant via CreateBuilder<TContext>(ws, …).RootElement and pass the immutable
(which converts via the Source(Variant instance) operator). The native-field Build(field: v)
factory avoids this entirely, so prefer it.
The immutable returned by .RootElement is a view over the workspace (and .Source lazies
reference whatever they were built from). Keep the JsonWorkspace / source ParsedJsonDocument
alive until the consumer has finished writing the value (e.g. across the await on a client
call). All of JsonWorkspace, JsonDocumentBuilder<T>, ParsedJsonDocument<T> are using-disposable.
string → JsonString.Source, int → JsonInt32.Source, int/long → JsonInteger/Schema.Source, DateTimeOffset/ISO string → JsonDateTime.Source — all implicit.JsonElement → JsonElement.Source (implicit, by-ref — the trap above).T → its containing union's Source (implicit). Chained two-hop user
conversions are NOT allowed at an argument — introduce an intermediate local for the first hop.corvus-builder-context-threading — building from UTF-8 spans in a loop with no closure (the Build<TContext> / CreateBuilder<TContext> form and its ref-safety gotchas); reach for it when the values are spans, not native string/int.corvus-bytes-to-bytes — when to thread spans at all (the record<->document string-seam anti-pattern + the genuine-leaf proof).corvus-mutable-documents — JsonWorkspace / JsonDocumentBuilder and mutating arbitrary JsonElement documents.ref-struct-delegates — why builder callbacks use named Build delegates (ref struct params) not Func<>/Action<>.corvus-buffer-and-pooling — the pooling that backs the workspace arena.corvus-codegen — how these factories are generated.© 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
Just SKILL.md in .github/skills/corvus-typed-model-construction of corvus-dotnet/Corvus.JsonSchema.
Open the folder on GitHubat commit 973097f
Corvus Typed Model Construction 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 Typed Model Construction this skillcorvus-dotnet/Corvus.JsonSchema | 199 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Chroma Vector DatabaseOrchestra-Research/AI-Research-SKILLs | 13k | 7 repos | ~2.3k | Automated safety check: Pass | MIT | |
| SageMaker Serving Image Selectionhuggingface/skills | 11k | 1 repos | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Codebase Managementgiancarloerra/SocratiCode | 3.3k | 1 repos | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| CLIP Image-Text MatchingOrchestra-Research/AI-Research-SKILLs | 13k | 7 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Sentence-Transformers Training Routerhuggingface/skills | 11k | 1 repos | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
huggingface/skills
Chooses the right serving container and current image URI for deploying a Hugging Face model to a SageMaker endpoint, preferring Hugging Face images over generic ones.
giancarloerra/SocratiCode
Set up, index, and manage SocratiCode codebase indexing. An agent skill from giancarloerra/SocratiCode.
Orchestra-Research/AI-Research-SKILLs
Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.
huggingface/skills
Routes a sentence-transformers training task to the right model type and required reference docs and example scripts, covering bi-encoders, rerankers, sparse and multi-vector models.
rehan-remade/universal-modder
Build cross-game mashups and total conversions, the "Minecraft inside Elden Ring" or "skateboarding in MW2" kind.
corvus-dotnet/Corvus.JsonSchema
Understand and work with the Roslyn analyzers shipped with Corvus.Text.Json.
corvus-dotnet/Corvus.JsonSchema
Run, interpret, and maintain BenchmarkDotNet benchmarks for JSON Schema validation and query languages.
corvus-dotnet/Corvus.JsonSchema
Test Corvus.JsonSchema against the JSON Schema Test Suite using Bowtie, the cross-implementation meta-validator.
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-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-dotnet/Corvus.JsonSchema
Generate strongly-typed C from JSON Schema using the Roslyn source generator or the corvusjson CLI tool.
Categories
Construct instances of generated Corvus strongly-typed models (DTOs, request/response bodies, discriminated-union variants) allocation-free, without composing or parsing JSON. JsonSchema. Construct instances of generated Corvus strongly-typed models (DTOs, request/response bodies, discriminated-union variants) allocation-free, without composing or parsing JSON.
Corvus Typed Model Construction fits situations like: : building a generated model from native values to pass to a generated client/handler; embedding a JsonElement/array value into a generated object; building union variants; fixing CS8168/CS8347/CS8350 around builders.
Run `npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-typed-model-construction -a claude-code`. Or copy the skill folder (.github/skills/corvus-typed-model-construction in corvus-dotnet/Corvus.JsonSchema) into .claude/skills/corvus-typed-model-construction in your project. Claude Code loads it when a task matches its description.
Run `npx skills add corvus-dotnet/Corvus.JsonSchema --skill corvus-typed-model-construction -a codex`. Or copy the skill folder (.github/skills/corvus-typed-model-construction in corvus-dotnet/Corvus.JsonSchema) into .agents/skills/corvus-typed-model-construction in your project. Codex loads it when a task matches its description.
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-typed-model-construction -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-typed-model-construction, .gemini/skills/corvus-typed-model-construction, .github/skills/corvus-typed-model-construction and .opencode/skills/corvus-typed-model-construction in your project.
SKILL.md names no scripts, command-line tools or credentials: Corvus Typed Model Construction is instructions for the agent only.
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.
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.
Corvus Typed Model Construction 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.
About 2.4k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Corvus Typed Model Construction: Chroma Vector Database (Orchestra-Research/AI-Research-SKILLs, 13k stars), SageMaker Serving Image Selection (huggingface/skills, 11k stars), Codebase Management (giancarloerra/SocratiCode, 3.3k stars) and CLIP Image-Text Matching (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.