Agent skill

Skill Forge Build

by AgriciDaniel in AgriciDaniel/skill-forge

Scaffold and build Claude Code skills from plans or descriptions.

Install Skill Forge Build

skills CLI

$ npx skills add AgriciDaniel/skill-forge --skill skill-forge-build -a claude-code

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

GitHub CLI

$ gh skill install AgriciDaniel/skill-forge skill-forge-build --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/AgriciDaniel/skill-forge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-forge-build .claude/skills/skill-forge-build && 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/

Paste into Claude Code

Install the "skill-forge-build" agent skill from https://github.com/AgriciDaniel/skill-forge/tree/main/skills/skill-forge-build into .claude/skills/skill-forge-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-forge-build", 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

$skill-installer install https://github.com/AgriciDaniel/skill-forge/tree/main/skills/skill-forge-build

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

skills CLI

$ npx skills add AgriciDaniel/skill-forge --skill skill-forge-build -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install AgriciDaniel/skill-forge skill-forge-build --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgriciDaniel/skill-forge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-forge-build .agents/skills/skill-forge-build && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "skill-forge-build" agent skill from https://github.com/AgriciDaniel/skill-forge/tree/main/skills/skill-forge-build into .agents/skills/skill-forge-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-forge-build", 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.

skills CLI

$ npx skills add AgriciDaniel/skill-forge --skill skill-forge-build -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install AgriciDaniel/skill-forge skill-forge-build --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgriciDaniel/skill-forge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-forge-build .cursor/skills/skill-forge-build && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "skill-forge-build" agent skill from https://github.com/AgriciDaniel/skill-forge/tree/main/skills/skill-forge-build into .cursor/skills/skill-forge-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-forge-build", 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

$ gemini skills install https://github.com/AgriciDaniel/skill-forge.git --path skills/skill-forge-build

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add AgriciDaniel/skill-forge --skill skill-forge-build -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install AgriciDaniel/skill-forge skill-forge-build --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgriciDaniel/skill-forge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-forge-build .gemini/skills/skill-forge-build && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "skill-forge-build" agent skill from https://github.com/AgriciDaniel/skill-forge/tree/main/skills/skill-forge-build into .gemini/skills/skill-forge-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-forge-build", 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.

GitHub CLI

$ gh skill install AgriciDaniel/skill-forge skill-forge-build

Installs 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).

skills CLI

$ npx skills add AgriciDaniel/skill-forge --skill skill-forge-build -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/AgriciDaniel/skill-forge.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-forge-build .github/skills/skill-forge-build && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "skill-forge-build" agent skill from https://github.com/AgriciDaniel/skill-forge/tree/main/skills/skill-forge-build into .github/skills/skill-forge-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-forge-build", 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.

skills CLI

$ npx skills add AgriciDaniel/skill-forge --skill skill-forge-build -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install AgriciDaniel/skill-forge skill-forge-build --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AgriciDaniel/skill-forge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-forge-build .opencode/skills/skill-forge-build && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "skill-forge-build" agent skill from https://github.com/AgriciDaniel/skill-forge/tree/main/skills/skill-forge-build into .opencode/skills/skill-forge-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-forge-build", 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.

Facts

Skill name: skill-forge-build
GitHub stars: 179
Token cost: ~1.3k tokens
SKILL.md length: 395 words
Files: 1
Skills in repo: 9
Repo updated: Apr 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Scaffold and build Claude Code skills from plans or descriptions.

Works in 10 steps: Gather Inputs → Generate Frontmatter → Write Main SKILL.md → …
User says build skill
SKILL.md covers Process and Scaffolding Command
Calls python

What it does

Skill Forge Build is an agent skill from AgriciDaniel/skill-forge. Scaffold and build Claude Code skills from plans or descriptions. Generates SKILL.md files, sub-skills, scripts, references, agents, and templates following the Agent Skills standard. Use when user says "build skill", "scaffold skill", "generate skill", "create SKILL.md", or "implement skill".

Its SKILL.md is about 1.3k 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 Agent Workflows, covering Skill authoring and Project scaffolding. The repository describes itself as: Ultimate Claude Code skill creator — design, scaffold, build, review, evolve, and publish production-grade AI agent skills. The licence is MIT.

When your agent uses it

User says build skill
Create SKILL.md
Implement skill

Example prompts

“build skill”
“scaffold skill”
“generate skill”
“/skill-forge-build”

Requirements

Python 3

Workflow steps

10 steps, taken from the step headings in SKILL.md.

Gather Inputs
Generate Frontmatter
Write Main SKILL.md
Generate Sub-Skills (Tier 3-4)
Generate Scripts (Tier 2-4)
Generate Reference Files
Generate Agent Definitions (Tier 4)
Generate Install Script
Validate
Output Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 2872ee9. 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:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Skill Forge Build loads about 1.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 395 words of instructions outside code blocks.

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

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 AgriciDaniel/skill-forge at commit 2872ee9, republished under its MIT licence (© AgriciDaniel). 395 words, ~1,343 tokens.

Download SKILL.mdSave it as .claude/skills/skill-forge-build/SKILL.md (or your agent's skills folder).

name: skill-forge-build
description: Scaffold and build Claude Code skills from plans or descriptions. Generates SKILL.md files, sub-skills, scripts, references, agents, and templates following the Agent Skills standard. Use when user says "build skill", "scaffold skill", "generate skill", "create SKILL.md", or "implement skill".

Skill Builder — Scaffold & Generate

Process

Step 1: Gather Inputs

Determine what we're building from:

Plan document: Output from /skill-forge plan (preferred)
Description: Natural language description of the skill
Existing skill: Path to a skill to use as foundation

If no plan exists, run a quick planning pass (ask 3 key questions):

What does the skill do? (1-2 sentences)
What commands should it have? (list)
Does it need scripts or external tools? (yes/no)

Step 2: Generate Frontmatter

The most critical step. The description field determines activation.

Framework for writing descriptions:

[Capability statement] + [Detailed capabilities] + [Trigger phrases]

Rules:

Under 1024 characters total
No XML angle brackets (< >)
Include 5-10 trigger phrases users would say
Mention file types if relevant
Add negative triggers if risk of over-triggering

Use references/description-guide.md for the full framework.

Step 3: Write Main SKILL.md

Structure the body following this template:

markdown

# [Skill Name] -- [Tagline]

[1-2 sentence overview]

## Quick Reference

| Command | What it does |
|---------|-------------|
| /name cmd1 | Description |
| /name cmd2 | Description |

## Orchestration Logic

[How commands route to sub-skills]
[Decision trees for conditional routing]

## [Domain-Specific Section]

[Core rules, thresholds, quality gates]

## Reference Files

[List of on-demand reference files]

## Sub-Skills

[List of sub-skills with one-line descriptions]

Critical SKILL.md rules:

Under 500 lines
Under 5000 tokens
Actionable instructions (not vague)
Include error handling
Link references, don't inline them

Step 4: Generate Sub-Skills (Tier 3-4)

For each sub-skill, generate a SKILL.md with:

yaml

---
name: parent-child
description: >
  [What it does]. Use when user says "[trigger 1]", "[trigger 2]",
  "[trigger 3]", or "[trigger 4]".
---

Sub-skill body guidelines:

Self-contained instructions for ONE workflow
Cross-reference other sub-skills by name (not inline their content)
Reference shared files in the parent skill's references/ directory
Include explicit input/output definitions

Step 5: Generate Scripts (Tier 2-4)

For each script:

python

#!/usr/bin/env python3
"""
Purpose: [What this script does]
Input: [Expected input format]
Output: [Expected output format]
Usage: python scripts/script_name.py [args]
"""

import argparse
import json
import sys
from typing import Any


def main(args: argparse.Namespace) -> dict[str, Any]:
    """Main execution function."""
    # Validate inputs
    # Do the work
    # Return structured output
    pass


if __name__ == "__main__":
    parser = argparse.ArgumentParser(description="[Script description]")
    parser.add_argument("input", help="[Input description]")
    parser.add_argument("--output", "-o", help="Output file path")
    args = parser.parse_args()

    try:
        result = main(args)
        print(json.dumps(result, indent=2))
    except Exception as e:
        print(json.dumps({"error": str(e)}), file=sys.stderr)
        sys.exit(1)

Script rules:

One script, one responsibility
CLI interface with argparse
Structured JSON output
Clear error messages
No dependencies beyond stdlib when possible

Show full SKILL.md (163 more words)Show less

Step 6: Generate Reference Files

For each reference file:

Focus on ONE topic
Under 200 lines
Include concrete examples
Use tables for thresholds and specifications
Mark with "Load on-demand" in parent SKILL.md

Step 7: Generate Agent Definitions (Tier 4)

Agent files use YAML frontmatter (different from skills):

markdown

---
name: [skill-name]-[role]
description: >
  [What this agent analyzes].
  <example>User says: "[trigger]"</example>
model: inherit
color: blue
tools:
  - Read
  - Grep
  - Glob
---

You are a [role] specialist.

## Your Role
[What this agent does]

## Process
1. [Steps...]

## Output Format
Return structured markdown with findings and recommendations.

Key differences from skills: Agent name is 3-50 chars, descriptions CAN use <example> blocks, agent-only fields include tools, color, permissionMode, maxTurns, memory. Body becomes the system prompt (second person).

Step 8: Generate Install Script

Create install.sh that copies files to ~/.claude/skills/ and ~/.claude/agents/.

Step 9: Validate

Run python scripts/validate_skill.py <path> on the generated skill. Check all quality gates from the main SKILL.md.

Step 10: Output Summary

Present the user with:

Generated file tree
Key files and their purposes
Installation instructions
Suggested test queries (3 that should trigger, 3 that should NOT)
Next steps (test, iterate, publish)

Scaffolding Command

For quick scaffolding, use:

bash

python scripts/init_skill.py <skill-name> --tier <1-4> --path <output-path>

This creates the full directory structure with placeholder content.

Files

Just SKILL.md in skills/skill-forge-build of AgriciDaniel/skill-forge.

Open the folder on GitHubat commit 2872ee9

Compare with similar skills

Skill Forge Build 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 Forge Build compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Skill Forge Build this skillAgriciDaniel/skill-forge	179	—	~1.3k	Automated safety check: Pass	MIT	6 mo ago
Claude Code Plugin Structureanthropics/claude-plugins-official	38k	10 repos	~3.4k	Automated safety check: Pass	Apache-2.0	yesterday
Skill Creatorluongnv89/asm	954	—	~5.3k	Automated safety check: Pass	MIT	3 days ago
CLI-Anything for CodexHKUDS/CLI-Anything	52k	—	~1.5k	Automated safety check: Pass	Apache-2.0	18 days ago
Create Skillmp-web3/claude-starter-kit	109	—	~985	Automated safety check: Notes	MIT	6 mo ago
Bmad Builderaj-geddes/claude-code-bmad-skills	488	—	~1.9k	Automated safety check: Notes	Custom licence	3 mo ago

Similar skills

Claude Code Plugin Structure
anthropics/claude-plugins-official
Official
Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.
38k GitHub starsUsed in 10 repos~3.4k tokens
Agent WorkflowsAuto-check passed
Skill Creator
luongnv89/asm
Create a skill or bring an existing one up to the same standard (validate + asm eval fix loop); run evals, tune triggering.
954 GitHub stars~5.3k tokensUpdated 3 days ago
Agent WorkflowsAuto-check passed
CLI-Anything for Codex
HKUDS/CLI-Anything
Lets Codex build, refine, test, validate and list CLI-Anything harnesses for GUI applications or source repositories, following the project's full methodology.
52k GitHub stars~1.5k tokensUpdated 18 days ago
DevelopmentAuto-check passed
Create Skill
mp-web3/claude-starter-kit
Walks through building a new Claude Code skill: asks what it should do, scaffolds it with an init script, writes SKILL.md and LEARNINGS.md and validates the result.
109 GitHub stars~985 tokensUpdated 6 mo ago
Agent WorkflowsAuto-check: notes
Bmad Builder
aj-geddes/claude-code-bmad-skills
Meta-skill for scaffolding and validating custom PLANNING/ORCHESTRATION skills within the BMAD Planning & Orchestrator plugin.
488 GitHub stars~1.9k tokensUpdated 3 mo ago
DevelopmentAuto-check: notes
Sciagent Skill Creator
jaechang-hits/SciAgent-Skills
Scaffold a new SciAgent-Skills entry. An agent skill from jaechang-hits/SciAgent-Skills.
371 GitHub stars~2.3k tokensUpdated 11 days ago
Agent WorkflowsAuto-check passed

Questions about Skill Forge Build

What does Skill Forge Build do?

Scaffold and build Claude Code skills from plans or descriptions. Skill Forge Build is an agent skill from AgriciDaniel/skill-forge. Scaffold and build Claude Code skills from plans or descriptions.

When should I use Skill Forge Build?

Skill Forge Build fits situations like: user says build skill; create SKILL.md; implement skill.

How do I install Skill Forge Build in Claude Code?

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

How do I install Skill Forge Build in Codex?

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

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

What does Skill Forge Build need to run?

Going by SKILL.md and its folder, Skill Forge Build needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Skill Forge Build access the network?

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.

Is Skill Forge Build 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 Skill Forge Build use?

Skill Forge Build is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Skill Forge Build use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Skill Forge Build?

Skills that share tags, products or a category with Skill Forge Build: Claude Code Plugin Structure (anthropics/claude-plugins-official, 38k stars), Skill Creator (luongnv89/asm, 954 stars), CLI-Anything for Codex (HKUDS/CLI-Anything, 52k stars) and Create Skill (mp-web3/claude-starter-kit, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Forge Build?

AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/skill-forge, which has 179 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on April 10, 2026.

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

Install Skill Forge Build

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill Builder — Scaffold & Generate

Process

Step 1: Gather Inputs

Step 2: Generate Frontmatter

Step 3: Write Main SKILL.md

Step 4: Generate Sub-Skills (Tier 3-4)

Step 5: Generate Scripts (Tier 2-4)

Step 6: Generate Reference Files

Step 7: Generate Agent Definitions (Tier 4)

Step 8: Generate Install Script

Step 9: Validate

Step 10: Output Summary

Scaffolding Command

Files

Compare with similar skills

Similar skills

More from AgriciDaniel/skill-forge

Related

Questions about Skill Forge Build