cratis-components-schema-editor

cratis-components-schema-editor is a skill for Claude Code, Codex from Cratis/AI. It costs 112 tokens per session (2,429 once invoked), scanned A, original, MIT.

Two React editors for schema-shaped JSON data: one edits the schema itself, and the other edits an object using that schema. A schema describes the fields, types, and formats that data may contain.

In plain words
What is it for?
Use it to edit property names, types, and formats in a schema, or to view and change an object according to a schema.
Why use it?
It prevents confusing a data definition with an instance of that data. The guide also explains the limited schema format these editors accept.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to edit property names, types, and formats in a schema, or to view and change an object according to a schema.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cratis/ai/cratis-components-schema-editor
View source ↗ Cratis/AI
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Cratis/AI --skill cratis-components-schema-editor
Clone the repo
git clone --depth 1 https://github.com/Cratis/AI

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for cratis-components-schema-editor

README.md
[![agentmods](https://agentmods.dev/badge/skills/cratis/ai/cratis-components-schema-editor.svg)](https://agentmods.dev/skills/cratis/ai/cratis-components-schema-editor)
Your own site
<a href="https://agentmods.dev/skills/cratis/ai/cratis-components-schema-editor"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-components-schema-editor.svg" alt="Measured on agentmods" height="20"></a>
Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,429 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00112 $0.02429
Opus 5 $0.00056 $0.01215
Sonnet 5 $0.00022 $0.00486
Haiku 4.5 $0.00011 $0.00243

Measured today against content hash 688ad02d6d38, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

cratis-components-schema-editor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/cratis-components-schema-editor/SKILL.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cratis Components schema editors

Two components edit schema-shaped data. They are not interchangeable:

Component Edits Subpath
SchemaEditor the schema — property names, types, and formats @cratis/components/SchemaEditor
ObjectContentEditor an object instance, interpreted through a schema @cratis/components/ObjectContentEditor

For a form bound to a generated Arc command, use CommandForm and its fields instead — see the cratis-arc-react-page skill. These editors are for the case where the shape itself is data.

Verified product sources

Package Version Verified from
@cratis/components 3.0.0 its package manifest and the SchemaEditor / ObjectContentEditor sources
primereact ^11.0.0 peer of @cratis/[email protected]
react ^19.0.0 peer of @cratis/[email protected]

The schema type these editors consume

This is a deliberately narrow, hand-rolled subset — not a JSON Schema draft type. Import it from either editor's subpath.

interface JsonSchema {
    title?: string; name?: string; $id?: string; $ref?: string;
    type?: string; format?: string; description?: string;
    properties?: Record<string, JsonSchemaProperty>;
    items?: JsonSchema;
    required?: string[];
    definitions?: Record<string, JsonSchema>;
}

interface JsonSchemaProperty {
    id?: string; name?: string; type?: string; format?: string; description?: string;
    items?: JsonSchema; properties?: Record<string, JsonSchemaProperty>;
    required?: boolean; $ref?: string;
}

type Json = string | number | boolean | null | Json[] | { [key: string]: Json };

Three limits to design around:

  • $ref and definitions are declared but never resolved. Nested navigation walks properties and items literally. A schema that relies on references will not render its referenced shapes.
  • type is a plain string, not a union — there is no exhaustiveness check.
  • required is read but never rendered or edited by SchemaEditor. Its table has two columns, Property and Type. Do not promise a required toggle.

Read the full file on GitHub · 239 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 239 lines · 112 tokens per session scan A 688ad02d6d38

Subscribe to this mod's changes

cratis-components-schema-editor is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 2,429 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.

Related

Other skills, from other repositories

wpf

Build and modernize WPF applications on .NET with correct XAML, data binding, commands, threading, styling, and Windows desktop migration decisions. USE FOR: working on WPF UI, MVVM, binding, commands, or desktop modernization; migrating WPF from .NET Framework to .NET; integrating newer Windows capabilities into a…

managedcode/dotnet-skills · 122 tokens

sharpconsoleui

Use SharpConsoleUI to build full terminal (TUI) applications in .NET — equally suited to full-screen single-window apps and multi-window desktops with overlapping draggable windows — using a compositor, a DOM layout engine, and 40+ reactive controls (data tables, tree views, forms, an embedded PTY terminal, markdown…

managedcode/dotnet-skills · 190 tokens

mvvm

Implement the Model-View-ViewModel pattern in .NET applications with proper separation of concerns, data binding, commands, and testable ViewModels using MVVM Toolkit. USE FOR: implementing UI separation with Model-View-ViewModel; using MVVM Toolkit (CommunityToolkit.Mvvm) for ViewModels; designing testable UI…

managedcode/dotnet-skills · 120 tokens

astro-developer

Comprehensive guide for developing in the Astro monorepo. Covers architecture, debugging, testing, and critical constraints. Use when working on features, fixes, tests, or understanding the codebase structure.

managedcode/dotnet-skills · 44 tokens

winui

Build or review WinUI 3 applications with the Windows App SDK, including MVVM patterns, packaging decisions, navigation, theming, windowing, and interop boundaries with other .NET stacks. USE FOR: building native modern Windows desktop UI on WinUI 3; integrating Windows App SDK features into a .NET app; deciding…

managedcode/dotnet-skills · 134 tokens

sonarjs

Use SonarJS-derived rules in .NET repositories that ship JavaScript or TypeScript frontends and need deeper bug-risk, code-smell, or cognitive-complexity checks than a minimal ESLint baseline. USE FOR: SonarQube, SonarCloud, or eslint-plugin-sonarjs setups; frontend code smells; cognitive complexity and deeper…

managedcode/dotnet-skills · 132 tokens