Agent skill

Shared Schemas

by InsForge in InsForge/InsForge

A skill your agent uses when contributing to InsForge's shared schema package.

Apache-2.0Auto-check passedFrontend & Design

Install Shared Schemas

skills CLI
$ npx skills add InsForge/InsForge --skill shared-schemas -a claude-code

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

GitHub CLI
$ gh skill install InsForge/InsForge shared-schemas --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/InsForge/InsForge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/insforge-dev/shared-schemas .claude/skills/shared-schemas && 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/

Facts

Skill name
shared-schemas
GitHub stars
13k
Token cost
~628 tokens
SKILL.md length
298 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when contributing to InsForge's shared schema package.

  • Works in 3 steps: Treat packages/shared-schemas/ as the… → Keep schemas organized by domain. → Use schema changes as a synchronization…
  • Contributing to InsForges shared schema package
  • SKILL.md covers Scope, Working Rules and Validation
  • Calls npm and npx

What it does

Shared Schemas is an agent skill from InsForge/InsForge. Use this skill when contributing to InsForge's shared schema package. This is for maintainers editing published Zod contracts, exported types, and shared API payload definitions consumed by InsForge packages in this repo and other InsForge tooling.

Its SKILL.md is about 630 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 Frontend & Design, covering Forms and validation. It works with Zod. The repository describes itself as: The all-in-one, open-source backend platform for agentic coding. InsForge gives your coding agent database, auth, storage, compute, hosting, and AI gateway to ship full-stack… The licence is Apache-2.0.

When your agent uses it

  • Contributing to InsForges shared schema package
  • Tasks that involve Forms and validation

Example prompts

  • “/shared-schemas”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Treat packages/shared-schemas/ as the source of truth for cross-package payloads.
  2. Keep schemas organized by domain.
  3. Use schema changes as a synchronization trigger.

What it can do on your machine

Read from SKILL.md and the folder at commit 2ec64b6. 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:

    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.

    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

Shared Schemas loads about 628 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 298 words of instructions outside code blocks.

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

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 InsForge/InsForge at commit 2ec64b6, republished under its Apache-2.0 licence (© InsForge). 298 words, ~628 tokens.

Download SKILL.mdSave it as .claude/skills/shared-schemas/SKILL.md (or your agent's skills folder).
name
shared-schemas
description
Use this skill when contributing to InsForge's shared schema package. This is for maintainers editing published Zod contracts, exported types, and shared API payload definitions consumed by InsForge packages in this repo and other InsForge tooling.

InsForge Dev Shared Schemas

Use this skill for packages/shared-schemas/ work in the InsForge repository.

Scope

  • packages/shared-schemas/src/**
  • any code in this repo that consumes the changed contracts
  • downstream InsForge tooling that depends on the published @insforge/shared-schemas package, including consumers not present in this repository

Working Rules

  1. Treat packages/shared-schemas/ as the source of truth for cross-package payloads.

    • If a request, response, or domain shape is shared across InsForge surfaces, define it here.
    • Do not duplicate the same contract in package-local files.
    • Remember that this package is not only for the repo's backend and dashboard packages. It is also consumed by other InsForge tooling, including MCP and SDK code that may live outside this repository.
  2. Keep schemas organized by domain.

    • Follow the existing *.schema.ts and *-api.schema.ts split when it fits the current package pattern.
    • Keep packages/shared-schemas/src/index.ts aligned with the intended public API.
    • Treat exported names and schema shapes as a public contract surface, not just an internal refactor target.
  3. Use schema changes as a synchronization trigger.

    • Update backend validation and response usage.
    • Update shared dashboard services, hooks, and UI assumptions in packages/dashboard/.
    • Check for import sites across packages/*, frontend/, and backend/ before finishing.
    • Call out likely downstream impact on MCP, SDK, or other external InsForge consumers when a change alters exported names, schema semantics, or payload shape.
    • Be conservative with breaking changes. If a breaking contract change is necessary, make it explicit in the handoff.
    • Never use the TypeScript any type. Shared contracts should stay explicit and trustworthy across package boundaries.

Validation

  • cd packages/shared-schemas && npm run build
  • cd backend && npx tsc --noEmit
  • cd packages/dashboard && npm run typecheck

Run package-specific tests as needed where behavior changed. If external consumers such as MCP or SDK cannot be validated from this repo, say that clearly instead of implying they were covered.

© InsForge, 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 .codex/skills/insforge-dev/shared-schemas of InsForge/InsForge.

Open the folder on GitHubat commit 2ec64b6

Compare with similar skills

Shared Schemas 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.

Shared Schemas compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Shared Schemas this skillInsForge/InsForge13k—~628Automated safety check: PassApache-2.0
Nuxt Contentsecondsky/claude-skills227—~4.3kAutomated safety check: PassMIT
Data Validationaiskillstore/marketplace430—~4.5kAutomated safety check: PassNone
World Book Skillecho-xianyu/worldbook-skill211—~1.8kAutomated safety check: PassCustom licence
Reglevictorgarciaesgi/regle506—~840Automated safety check: PassMIT
Buzzformbuildnbuzz/buzzform101—~1.5kAutomated safety check: PassMIT

Similar skills

  • Nuxt Content

    secondsky/claude-skills

    Nuxt Content v3 Git-based CMS for Markdown/MDC content sites.

    227 GitHub stars~4.3k tokensUpdated 9 days ago
    Frontend & DesignAuto-check passed
  • Data Validation

    aiskillstore/marketplace

    A skill your agent uses when implementing data validation for API payloads, form inputs, or database writes.

    430 GitHub stars~4.5k tokensUpdated today
    Frontend & DesignAuto-check passed
  • World Book Skill

    echo-xianyu/worldbook-skill

    Create and manage SillyTavern Character Cards (角色卡) and World Books (世界书).

    211 GitHub stars~1.8k tokensUpdated 4 mo ago
    Frontend & DesignAuto-check passed
  • Regle

    victorgarciaesgi/regle

    Core Regle form validation in Vue 3 — setup with useRegle, the reactive r$ object, validation properties, displaying errors, and modifiers.

    506 GitHub stars~840 tokensUpdated 9 days ago
    Frontend & DesignAuto-check passed
  • Buzzform

    buildnbuzz/buzzform

    A skill your agent uses when working with BuzzForm schema-driven forms, @buildnbuzz/form-core, @buildnbuzz/form-react, or any related APIs like defineSchema, InferType, FormProvider, useDataField…

    101 GitHub stars~1.5k tokensUpdated 4 mo ago
    Frontend & DesignAuto-check passed
  • Regle Migrate Vuelidate

    victorgarciaesgi/regle

    Migrate Vuelidate form validation to Regle. An agent skill from victorgarciaesgi/regle.

    506 GitHub stars~752 tokensUpdated 9 days ago
    Frontend & DesignAuto-check passed

More from InsForge/InsForge

All 8 skills in this repo
  • Doc Author

    InsForge/InsForge

    Write, edit, and maintain documentation. An agent skill from InsForge/InsForge.

    13k GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • E2E Testing

    InsForge/InsForge

    A skill your agent uses when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR.

    13k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Backend

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's backend package.

    13k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Dashboard

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's shared dashboard package.

    13k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • Docs

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's product documentation in this repository.

    13k GitHub stars~761 tokensUpdated yesterday
    Auto-check passed
  • Insforge Dev

    InsForge/InsForge

    Use this skill set when contributing to the InsForge monorepo itself.

    13k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Shared Schemas

What does Shared Schemas do?

A skill your agent uses when contributing to InsForge's shared schema package. Shared Schemas is an agent skill from InsForge/InsForge. Use this skill when contributing to InsForge's shared schema package.

When should I use Shared Schemas?

Shared Schemas fits situations like: contributing to InsForges shared schema package; tasks that involve Forms and validation.

How do I install Shared Schemas in Claude Code?

Run `npx skills add InsForge/InsForge --skill shared-schemas -a claude-code`. Or copy the skill folder (.codex/skills/insforge-dev/shared-schemas in InsForge/InsForge) into .claude/skills/shared-schemas in your project. Claude Code loads it when a task matches its description.

How do I install Shared Schemas in Codex?

Run `npx skills add InsForge/InsForge --skill shared-schemas -a codex`. Or copy the skill folder (.codex/skills/insforge-dev/shared-schemas in InsForge/InsForge) into .agents/skills/shared-schemas in your project. Codex loads it when a task matches its description.

Can I use Shared Schemas 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 InsForge/InsForge --skill shared-schemas -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/shared-schemas, .gemini/skills/shared-schemas, .github/skills/shared-schemas and .opencode/skills/shared-schemas in your project.

What does Shared Schemas need to run?

Going by SKILL.md and its folder, Shared Schemas needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.

Does Shared Schemas access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Shared Schemas 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 Shared Schemas use?

Shared Schemas 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 Shared Schemas use?

About 628 tokens (SKILL.md is roughly 2.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 Shared Schemas?

Skills that share tags, products or a category with Shared Schemas: Nuxt Content (secondsky/claude-skills, 227 stars), Data Validation (aiskillstore/marketplace, 430 stars), World Book Skill (echo-xianyu/worldbook-skill, 211 stars) and Regle (victorgarciaesgi/regle, 506 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Shared Schemas?

InsForge (a GitHub organization) maintains it in InsForge/InsForge, which has 13,066 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

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