Agent skill

Scaffolding

by OdradekAI in OdradekAI/bundles-forge

A skill your agent uses when generating project structure for new bundle-plugins, adding or removing platform support (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, OpenClaw), updating platform…

Apache-2.0Auto-check passedDevelopment

Install Scaffolding

skills CLI
$ npx skills add OdradekAI/bundles-forge --skill scaffolding -a claude-code

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

GitHub CLI
$ gh skill install OdradekAI/bundles-forge scaffolding --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/OdradekAI/bundles-forge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scaffolding .claude/skills/scaffolding && 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
scaffolding
GitHub stars
229
Used in
1 other repo
Token cost
~3.1k tokens
SKILL.md length
1,282 words
Files
34 (incl. references, assets)
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when generating project structure for new bundle-plugins, adding or removing platform support (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, OpenClaw), updating platform…

  • Works in 3 steps: Design document provided (from… → User request + no existing project → New… → User request + existing project →…
  • Generating project structure for new bundle-plugins
  • SKILL.md covers Overview, Entry Detection, New Project: Scaffold Layers and New Project: Generation Process, plus 6 more sections
  • Runs Batch scripts from its folder; calls git

What it does

Scaffolding is an agent skill from OdradekAI/bundles-forge. Use when generating project structure for new bundle-plugins, adding or removing platform support (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, OpenClaw), updating platform manifests, or migrating hooks and configuration between platforms

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 42 other files, including reference files and assets (for example `assets/.github/workflows/validate-plugin.yml`, `assets/mcp-json.md` and `assets/platforms/claude-code/hooks.json`).

It sits in Development, covering Project scaffolding. The repository describes itself as: An agentic skills framework & bundle-plugin engineering toolkit that works. The licence is Apache-2.0.

When your agent uses it

  • Generating project structure for new bundle-plugins
  • Removing platform support (Claude Code
  • Updating platform manifests
  • Migrating hooks and configuration between platforms

Example prompts

  • “/scaffolding”

Requirements

  • Pre-approved tools (allowed-tools): Bash(bundles-forge bump-version *)

Workflow steps

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

  1. Design document provided (from bundles-forge:blueprinting) → New Project flow
  2. User request + no existing project → New Project flow
  3. User request + existing project → Platform Adaptation flow (add / fix / migrate / remove)

What it can do on your machine

Read from SKILL.md and the folder at commit c1b0e10. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(bundles-forge bump-version *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Batch, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • git

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

  • Network

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

Scaffolding loads about 3.1k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 1,282 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
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~20k

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 OdradekAI/bundles-forge at commit c1b0e10, republished under its Apache-2.0 licence (© OdradekAI). 1,282 words, ~3,081 tokens.

Download SKILL.mdSave it as .claude/skills/scaffolding/SKILL.md (or your agent's skills folder). This skill also uses 33 other files; get the full folder from GitHub.
name
scaffolding
description
Use when generating project structure for new bundle-plugins, adding or removing platform support (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, OpenClaw), updating platform manifests, or migrating hooks and configuration between platforms
allowed-tools
Bash(bundles-forge bump-version *)

Scaffolding Bundle-Plugins

Overview

Generate new bundle-plugin projects and manage platform support across their lifecycle. Handles initial project generation (greenfield) and ongoing platform adaptation (add, fix, migrate, remove).

Core principle: Generate only what's needed. Every platform, every file has a reason to exist. This skill generates structure only — it does not run its own scripts. Validation is delegated to bundles-forge:auditing; version checks to bundles-forge bump-version.

Skill type: Hybrid — follow the generation/adaptation process rigidly, but mode selection and component choices are flexible based on user context.

Announce at start: "I'm using the scaffolding skill to [generate your project / add <platform> support / remove <platform> support / add <component> / remove <component>]."

Entry Detection

Determine the operation based on context:

  1. Design document provided (from bundles-forge:blueprinting) → New Project flow
  2. User request + no existing project → New Project flow
  3. User request + existing project → Platform Adaptation flow (add / fix / migrate / remove)

New Project: Scaffold Layers

For new projects, first select a mode:

  • Design document specifies the mode (minimal or intelligent)
  • Direct invocation — choose between:
    • intelligent — recommend architecture based on user description, avoid unnecessary components
    • custom — present the full architecture option set, ask the user about each component
Minimal Mode (quick packaging)

Lean plugin for marketplace distribution:

FilePurpose
.claude-plugin/plugin.jsonPlugin identity and metadata
skills/<skill-name>/SKILL.mdOne directory per skill
README.mdInstallation instructions and skill catalog
LICENSEDefault MIT unless specified

No hooks, no bootstrap, no version infrastructure. Add these later by re-running scaffolding in platform adaptation mode.

Intelligent Mode
Core

Generated for all intelligent-mode projects regardless of platform selection:

FilePurpose
package.jsonProject identity and version
README.mdInstallation per platform, skill catalog
LICENSEDefault MIT unless specified
.gitignorenode_modules, .worktrees, OS files
.version-bump.jsonVersion sync manifest
skills/<skill-name>/SKILL.mdOne directory per skill
Platform Adapters (selected platforms only)
PlatformFiles
Claude Code.claude-plugin/plugin.json, hooks/hooks.json, hooks/run-hook.cmd, hooks/session-start
Cursor.cursor-plugin/plugin.json, hooks/hooks-cursor.json, hooks/session-start
Codex.codex/INSTALL.md, AGENTS.md
OpenCode.opencode/plugins/<name>.js, .opencode/INSTALL.md
Gemini CLIgemini-extension.json, GEMINI.md

For platform-specific wiring details, read references/platform-adapters.md.

Bootstrap (if requested)
FilePurpose
skills/using-<project>/SKILL.mdMeta-skill: instruction priority, skill routing table
skills/using-<project>/references/Per-platform tool mappings
Optional Components (only if specified)
ComponentFilesWhen to Include
Executablesbin/<tool-name>Skills reference CLI tools (see references/external-integration.md decision tree)
MCP servers.mcp.jsonSkills need external service integration (see references/external-integration.md decision tree)
LSP servers.lsp.jsonSkills involve language-specific code intelligence (see references/external-integration.md LSP section)
Output stylesoutput-styles/<style>.mdCustom output formatting (see references/external-integration.md Output Styles section)
Default settingssettings.jsonDefault agent activation (see references/external-integration.md Default Settings section)
User configurationuserConfig in plugin.jsonSkills need user-provided API keys, endpoints, or tokens — Claude Code only (see references/external-integration.md userConfig section)
Marketplace entry.claude-plugin/marketplace.jsonPlugin targets marketplace distribution — declares plugin metadata for the marketplace index

New Project: Generation Process

Minimal mode:

  1. Create plugin manifest from assets/platforms/claude-code/plugin.json template
  2. Generate skill directories — one per skill
  3. Generate README + LICENSE
  4. git init + initial commit; validate manifest JSON

Intelligent mode:

Phase 1 — Load context:

  1. Read template index — load references/scaffold-templates.md
  2. Read templates — load from assets/ (infrastructure, docs, bootstrap)
  3. Read platform templates — load from assets/platforms/<platform>/
  4. Read anatomy — load references/project-anatomy.md

Phase 2 — Generate: 5. Replace placeholders — substitute <project-name>, <author-name>, etc. 6. Generate per-platform — only create files for target platforms 7. Generate skill stubs — one directory per skill 8. Generate bootstrap — if requested, create meta-skill with routing table 10. Generate optional components — only what the design specifies. For MCP servers, use assets/mcp-json.md template and consult references/external-integration.md for transport selection and platform differences. When userConfig is specified, add the userConfig field to plugin.json with appropriate sensitive flags. When marketplace distribution is specified, generate .claude-plugin/marketplace.json with plugin metadata. When CI validation is specified, generate .github/workflows/validate-plugin.yml from template

Phase 3 — Finalize: 11. git init + initial commit; run bundles-forge bump-version --check

Platform Adaptation: Existing Projects

Adding a Platform
  1. Detect current platforms — scan for existing manifests (see detection table in references/platform-adapters.md)
  2. Identify target — read references/platform-adapters.md for wiring details
  3. Generate adapter files — from assets/platforms/<platform>/, replace <project-name> placeholders
  4. Update version sync — add version-bearing manifests to .version-bump.json
  5. Update hooks — if platform uses session hooks, ensure session-start (Bash) handles its JSON format via run-hook.cmd. For custom hooks beyond SessionStart, read references/hooks-configuration.md
  6. Update documentation — add install section to README; create platform-specific docs if needed
  7. Verify — validate manifests, bundles-forge bump-version --check, test hooks
Removing a Platform
  1. Delete manifest files — remove the platform's manifest directory or file
  2. Update .version-bump.json — remove entries for deleted manifests
  3. Clean hooks — delete platform-specific hook files; simplify session-start if branches removed
  4. Update documentation — remove install section from README and platform-specific docs
  5. Verify — bundles-forge bump-version --check; run inspector validation
Show full SKILL.md (534 more words)Show less
Adding Optional Components

Add MCP servers, CLI executables, LSP servers, userConfig, output styles, or default settings to an existing project:

  1. Determine component type — read references/external-integration.md decision tree to choose the right integration level
  2. Generate component files — create the corresponding file(s) at their default location (.mcp.json, .lsp.json, output-styles/, settings.json, or userConfig in plugin.json)
  3. Update plugin manifests — add component declarations to plugin.json for platforms that require explicit paths (Cursor). For Claude Code, convention-based discovery handles most components automatically
  4. Update skill references — add allowed-tools frontmatter for new CLI/MCP tools, add ${user_config.KEY} references where skills need user-provided values
  5. Update README — add setup instructions for the new component (especially MCP server config for non-Claude Code platforms, LSP binary installation)
  6. Verify — run inspector validation to confirm structural integrity
Removing Optional Components

Remove MCP servers, CLI executables, or LSP servers from an existing project. Read references/external-integration.md "Optional Component Removal" section for step-by-step instructions covering:

  • Removing MCP servers (.mcp.json, plugin.json mcpServers, skill references, README)
  • Removing CLI executables (bin/, allowed-tools, skill body)
  • Removing LSP servers (.lsp.json, README)
  • Downgrading MCP to CLI (replace MCP with lighter CLI alternative)

Post-Action Validation

Step 1 — Deterministic checks (script): Run bundles-forge audit-skill <target-dir> to verify structure, manifests, version sync, and frontmatter. Review any critical or warning findings before proceeding.

Step 2 — Semantic inspection (agent): Dispatch the inspector agent (agents/inspector.md) for semantic validation that scripts cannot cover (template quality, hook logic coherence, design alignment). The inspector adjusts scope based on context:

  • New project → full inspection (template quality, optional components, hook semantics, design coherence)
  • Platform adaptation → focused inspection (hook semantics and template quality for affected platforms)

If subagent dispatch is unavailable: Ask — "Subagents are not available. Run validation inline?" If confirmed, read agents/inspector.md and follow its instructions within this conversation, then report PASS/FAIL.

Common Mistakes

MistakeFix
Generating all platforms regardless of designOnly create files for selected platforms
Forgetting .version-bump.json entriesEvery version-bearing manifest needs an entry
Hardcoding author in templatesPull from git config or ask
Missing session-start or run-hook.cmd in hook configClaude Code uses run-hook.cmd session-start; Cursor runs ./hooks/session-start directly; both require bash
Bootstrap skill > 200 linesKeep lean — extract to references/
Wrong hook format (PascalCase vs camelCase)Claude Code: SessionStart, Cursor: sessionStart
Copying template without customizingReplace every <project-name> placeholder
Using intelligent mode infrastructure for minimalMinimal mode avoids over-engineering
Using MCP when CLI sufficesConsult references/external-integration.md decision tree — prefer CLI for stateless, single-shot tools
Using ../ paths to reference files outside the pluginAfter marketplace install, plugins are cached — ../ paths break. Keep all files within the plugin root
Writing persistent data to ${CLAUDE_PLUGIN_ROOT}PLUGIN_ROOT changes on each update. Use ${CLAUDE_PLUGIN_DATA} for caches, installed dependencies, and generated state

Inputs

  • design-document (optional) — from bundles-forge:blueprinting with project mode, name, platforms, skill inventory, bootstrap strategy, and components
  • project-directory (optional) — existing bundle-plugin project root for platform adaptation
  • target-platform (optional) — platform to add or remove

Outputs

  • scaffold-output — generated project structure or adapted platform files. Consumed by the orchestrating skill (blueprinting or optimizing) for subsequent phases
  • inspector-report (optional) — validation report in .bundles-forge/blueprints/

Integration

Called by:

  • bundles-forge:blueprinting — Phase 1 of the new-project pipeline
  • bundles-forge:optimizing — Platform Coverage routing for adding new platforms
  • User directly — for platform adaptation or ad-hoc project generation

Pairs with:

  • bundles-forge:releasing — version infrastructure and sync

© OdradekAI, 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

SKILL.md and 33 other files (references, assets) in skills/scaffolding of OdradekAI/bundles-forge.

  • SKILL.md
  • assets/.github/workflows/validate-plugin.yml
  • assets/hooks/run-hook.cmd
  • assets/hooks/session-start
  • assets/mcp-json.md
  • assets/platforms/claude-code/hooks.json
  • assets/platforms/claude-code/plugin.json
  • assets/platforms/codex/AGENTS.md
  • assets/platforms/codex/INSTALL.md
  • assets/platforms/cursor/hooks-cursor.json
  • assets/platforms/cursor/plugin.json
  • assets/platforms/gemini/GEMINI.md
  • … and 22 more

Open the folder on GitHubat commit c1b0e10

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in OdradekAI/bundles-forge, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Scaffolding 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.

Scaffolding compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scaffolding this skillOdradekAI/bundles-forge2291 repos~3.1kAutomated safety check: PassApache-2.0
Nx Generatenomcopter/react-mosaic4.8k7 repos~1.9kAutomated safety check: PassCustom licence
PonytailDavidObando/gsharp5658 repos~1.7kAutomated safety check: PassMIT
Run Nx Generatornrwl/nx29k2 repos~592Automated safety check: NotesMIT
Conductor Setupgemini-cli-extensions/conductor3.8k—~4.2kAutomated safety check: PassApache-2.0
Mirage VFS Adapter Authoringstrukto-ai/mirage3.7k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Nx Generate

    nomcopter/react-mosaic

    Generate code using nx generators. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 7 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    565 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    DevelopmentAuto-check: notes
  • Conductor Setup

    gemini-cli-extensions/conductor

    Scaffolds the project and sets up the Conductor environment.

    3.8k GitHub stars~4.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.

    3.7k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.

    14k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from OdradekAI/bundles-forge

All 8 skills in this repo
  • Releasing

    OdradekAI/bundles-forge

    A skill your agent uses when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to…

    229 GitHub stars~3.3k tokensUpdated 5 mo ago
    Auto-check passed
  • Testing

    OdradekAI/bundles-forge

    A skill your agent uses when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating…

    229 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Auditing

    OdradekAI/bundles-forge

    A skill your agent uses when reviewing a bundle-plugin for structural issues, version drift, skill quality, workflow integration, or security risks — before releasing, after changes, or after adding…

    229 GitHub stars~5.4k tokensUpdated 5 mo ago
    Auto-check passed
  • Using Bundles Forge

    OdradekAI/bundles-forge

    A skill your agent uses when starting any conversation involving bundle-plugins — blueprinting, scaffolding, authoring, auditing, testing, optimizing, or releasing.

    229 GitHub stars~1.4k tokensUpdated 5 mo ago
    Auto-check passed
  • Optimizing

    OdradekAI/bundles-forge

    A skill your agent uses when optimizing a bundle-plugin or single skill — improving descriptions, reducing tokens, fixing audit findings, restructuring workflows, adding skills to fill gaps, or…

    229 GitHub stars~5.2k tokensUpdated 5 mo ago
    Auto-check passed
  • Authoring

    OdradekAI/bundles-forge

    A skill your agent uses when writing, completing, improving, or adapting SKILL.md and agents/.md in a bundle-plugin — integrating external skills, filling scaffolded stubs, or rewriting for better…

    229 GitHub stars~3k tokensUpdated 5 mo ago
    Auto-check passed

Categories

Questions about Scaffolding

What does Scaffolding do?

A skill your agent uses when generating project structure for new bundle-plugins, adding or removing platform support (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, OpenClaw), updating platform…. Scaffolding is an agent skill from OdradekAI/bundles-forge.

When should I use Scaffolding?

Scaffolding fits situations like: generating project structure for new bundle-plugins; removing platform support (Claude Code; updating platform manifests; migrating hooks and configuration between platforms.

How do I install Scaffolding in Claude Code?

Run `npx skills add OdradekAI/bundles-forge --skill scaffolding -a claude-code`. Or copy the skill folder (skills/scaffolding in OdradekAI/bundles-forge) into .claude/skills/scaffolding in your project. Claude Code loads it when a task matches its description.

How do I install Scaffolding in Codex?

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

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

What does Scaffolding need to run?

Going by SKILL.md and its folder, Scaffolding needs Windows cmd for the scripts in its folder and the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash(bundles-forge bump-version *).

Does Scaffolding access the network?

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

Is Scaffolding 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 Scaffolding use?

Scaffolding 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 Scaffolding use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.

What are the alternatives to Scaffolding?

Skills that share tags, products or a category with Scaffolding: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 565 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scaffolding?

OdradekAI (a GitHub organization) maintains it in OdradekAI/bundles-forge, which has 229 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on April 27, 2026.

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