New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Insforge Dev

by InsForge in InsForge/InsForge

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

Apache-2.0Auto-check passedDevelopment

Install Insforge Dev

skills CLI
$ npx skills add InsForge/InsForge --skill insforge-dev -a claude-code

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

GitHub CLI
$ gh skill install InsForge/InsForge insforge-dev --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 .claude/skills/insforge-dev && 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
insforge-dev
GitHub stars
13k
Token cost
~1.1k tokens
SKILL.md length
550 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 4 steps: Identify the package boundary before… → Put code in the narrowest correct layer. → Preserve repo conventions. → …
  • Tasks that involve Monorepo tooling
  • SKILL.md covers Core Rules, Finish Rules and Pre-PR Checklist (Mandatory…
  • Calls npx, npm and turbo

What it does

Insforge Dev is an agent skill from InsForge/InsForge. Use this skill set when contributing to the InsForge monorepo itself. This is for InsForge maintainers and contributors editing the platform, the shared dashboard package, the self-hosting shell, the UI library, shared schemas, tests, or docs.

Its SKILL.md is about 1.1k 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 Monorepo tooling. 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

  • Tasks that involve Monorepo tooling

Example prompts

  • “/insforge-dev”

Requirements

  • Node.js

Workflow steps

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

  1. Identify the package boundary before editing.
  2. Put code in the narrowest correct layer.
  3. Preserve repo conventions.
  4. Do not confuse repo development with app development on InsForge.

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:

    • npx
    • npm
    • turbo

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

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, 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

Insforge Dev loads about 1.1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 550 words of instructions outside code blocks.

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

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). 550 words, ~1,076 tokens.

Download SKILL.mdSave it as .claude/skills/insforge-dev/SKILL.md (or your agent's skills folder).
name
insforge-dev
description
Use this skill set when contributing to the InsForge monorepo itself. This is for InsForge maintainers and contributors editing the platform, the shared dashboard package, the self-hosting shell, the UI library, shared schemas, tests, or docs.

InsForge Dev

Use this skill set for work inside the InsForge repository.

Then use the narrowest package skill that matches the task:

  • backend
  • dashboard
  • ui
  • shared-schemas
  • docs

Use the cross-repo release workflow skill when preparing an OSS PR:

  • e2e-testing

Core Rules

  1. Identify the package boundary before editing.

    • backend/: API, auth, database, providers, realtime, schedules
    • packages/dashboard/: publishable dashboard package that supports self-hosting and cloud-hosting modes
    • frontend/: local React + Vite shell that mounts packages/dashboard/ in self-hosting mode
    • packages/shared-schemas/: cross-package contracts
    • packages/ui/: reusable design-system primitives
    • docs/: product and agent-facing documentation

  2. Put code in the narrowest correct layer.

    • Contract change: packages/shared-schemas/ first, then consumers.
    • Backend behavior: route -> service -> provider/infra.
    • Shared dashboard behavior, routes, features, exports, and host contracts: packages/dashboard/.
    • Self-hosting-only bootstrap, env wiring, and shell styling: frontend/.
    • Reusable primitive: packages/ui/ first.

  3. Preserve repo conventions.

    • Backend TS source uses ESM-style .js import specifiers.
    • Backend success responses usually return raw JSON, not { data }.
    • Backend validation commonly uses shared Zod schemas plus AppError.
    • Dashboard data access goes through apiClient and React Query.
    • Dashboard frontend tests are split into Vitest unit tests, Vitest component tests, and Playwright UI smoke tests.
    • Shared payloads belong in @insforge/shared-schemas.
    • Never use the TypeScript any type. Prefer precise types, schema-derived types, unknown, or generics.

  4. Do not confuse repo development with app development on InsForge.

    • This repo contains the platform, the publishable dashboard package, and a local shell for self-hosting mode.
    • Keep guidance focused on maintaining InsForge itself.

Finish Rules

  • Run the smallest validation that gives confidence for the change.
  • Use repo-level checks like npm run lint, npm run build, npm run typecheck, and npm test when the change crosses package boundaries — each is wired through Turborepo (turbo run <task>) and covers every workspace, including packages/dashboard/ and packages/shared-schemas/.
  • For dashboard UI behavior changes, choose the lowest useful frontend test layer from the dashboard skill and run that command before reporting back.
  • Use the package-specific validation steps in the child skill when the work is isolated to one package.
  • When reporting back, state what changed, what you validated, and what you could not validate.
Show full SKILL.md (207 more words)Show less

Pre-PR Checklist (Mandatory Before Pushing to a PR)

Before opening a PR or pushing new commits to an existing PR branch, run all of the following from the repo root and do not proceed while any of them fail on files your change touches:

  1. npx turbo run typecheck — must pass across all packages.
  2. npx turbo run lint — must pass. If the failure is pre-existing in main and unrelated to your change, scope it:
    • Run npx eslint <your-changed-files> and confirm your files are clean.
    • Call out the pre-existing debt in the PR body so reviewers know it is not yours.
    • Auto-fixable prettier/eslint errors in your own diff must be fixed (npx eslint --fix <file> or npm run format).
  3. npx turbo run test (or the package-specific test command) — all tests must pass, including any new tests you added for the change.
  4. npx turbo run build if routing, config, schemas, or cross-package exports changed.
  5. Use e2e-testing to run the deterministic cross-repo E2E gate before opening, updating, or submitting the InsForge OSS PR.

Never push with failing checks on files you touched, even if CI would catch them later. CI failures slow reviewers down and the lint fix almost always takes less than a minute locally.

© 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 of InsForge/InsForge.

Open the folder on GitHubat commit 2ec64b6

Compare with similar skills

Insforge Dev 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.

Insforge Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Insforge Dev this skillInsForge/InsForge13k—~1.1kAutomated safety check: PassApache-2.0
Fix CIgronxb/hot-updater1.8k—~572Automated safety check: PassCustom licence
Publishing A New PackageComfy-Org/ComfyUI_frontend2.1k—~1.8kAutomated safety check: PassGPL-3.0
Lineth QuickstartLFDT-Lineth/lineth-monorepo126—~1kAutomated safety check: NotesAGPL-3.0
Bug Hunteroctanejs/octane1.4k—~707Automated safety check: PassMIT
Angular Developerradix-ng/primitives274—~1.2kAutomated safety check: PassMIT

Similar skills

  • Fix CI

    gronxb/hot-updater

    Run a local pnpm monorepo CI loop, fix failures, and stop only when the full sequence is green.

    1.8k GitHub stars~572 tokensUpdated today
    DevelopmentAuto-check passed

  • Publishing A New Package

    Comfy-Org/ComfyUI_frontend

    Publishes a new package from this monorepo to npm under @comfyorg and proves it is consumable from another repo.

    2.1k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Lineth Quickstart

    LFDT-Lineth/lineth-monorepo

    Operating manual for the Lineth Stack quickstart — the Docker-Compose dev/demo stack at docs/getting-started/lineth-stack in the lineth-monorepo that boots a local Linea/Lineth L2 with Sepolia or…

    126 GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Bug Hunter

    octanejs/octane

    Find and fix a bug in the octane monorepo. An agent skill from octanejs/octane.

    1.4k GitHub stars~707 tokensUpdated today
    DevelopmentAuto-check passed

  • Angular Developer

    radix-ng/primitives

    Angular framework reference for building this signals-first, headless directive library.

    274 GitHub stars~1.2k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Angular Tooling

    Kilo-Org/kilo-marketplace

    Use Angular CLI and development tools effectively in Angular v20+ projects.

    189 GitHub stars~1.7k tokensUpdated 9 days ago
    DevelopmentAuto-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

  • Shared Schemas

    InsForge/InsForge

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

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

Categories

Questions about Insforge Dev

What does Insforge Dev do?

Use this skill set when contributing to the InsForge monorepo itself. Insforge Dev is an agent skill from InsForge/InsForge. Use this skill set when contributing to the InsForge monorepo itself.

When should I use Insforge Dev?

Insforge Dev fits situations like: tasks that involve Monorepo tooling.

How do I install Insforge Dev in Claude Code?

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

How do I install Insforge Dev in Codex?

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

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

What does Insforge Dev need to run?

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

Does Insforge Dev access the network?

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

Is Insforge Dev 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 Insforge Dev use?

Insforge Dev 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 Insforge Dev use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Insforge Dev?

Skills that share tags, products or a category with Insforge Dev: Fix CI (gronxb/hot-updater, 1.8k stars), Publishing A New Package (Comfy-Org/ComfyUI_frontend, 2.1k stars), Lineth Quickstart (LFDT-Lineth/lineth-monorepo, 126 stars) and Bug Hunter (octanejs/octane, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Insforge Dev?

InsForge (a GitHub organization) maintains it in InsForge/InsForge, which has 13,064 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.