Skill

setup

Install, build, and configure the Forge agent job runner. Verify the binary, start the daemon, and validate everything works.

npx claudepluginhub zate/cc-plugins --plugin forge

Tool Access

This skill is limited to using the following tools:

BashReadAskUserQuestion

Preview

Build, install, and verify the Forge agent job runner.

SKILL.md

Similar Skills

skf-setup

Initializes forge environment, detects tools, and sets capability tier (Quick/Forge/Forge+/Deep). Useful when users request forge setup or initialization.

7 files

skill-forge

Agent Bootstrap: Declarative Environment Setup

Bootstraps agentic dev environment from agent.toml: validates required env vars/commands/runtimes, configures Claude Code plugins/MCP servers. Use for new repos, misconfigs, or new machines.

jwynia-agent-skills-1

agenticflow-agent

Create, run, and iterate on single AgenticFlow AI agents via `af agent create/update/run/delete` CLI, --patch updates, schema inspection for fields like mcp_clients/response_format, model/code configs. For support bots or task agents without orchestration.

agenticflow-plugin

Stats

Parent Repo Stars6

Parent Repo Forks1

Last CommitApr 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Forge Setup

Build, install, and verify the Forge agent job runner.

Step 1: Check if forge is already installed

command -v forge && forge version

If found and working, skip to Step 4.

Step 2: Build from source

The forge source lives at ~/projects/forge.

cd ~/projects/forge && go build -o forge ./cmd/forge

Step 3: Install the binary

Ask the user where to install. Common options:

~/.local/bin/forge (user-local, usually on PATH)
/usr/local/bin/forge (system-wide, needs sudo)
Leave in ~/projects/forge/ and add to PATH

cp ~/projects/forge/forge ~/.local/bin/forge

Verify:

forge version

Step 4: Check daemon status

if [[ -f ~/.forge/forge.pid ]]; then
    PID=$(cat ~/.forge/forge.pid | tr -d '[:space:]')
    if kill -0 "$PID" 2>/dev/null; then
        echo "Daemon running (pid $PID)"
    else
        echo "Stale PID file - daemon not running"
    fi
else
    echo "Daemon not running"
fi

Step 5: Start daemon if needed

nohup forge daemon > ~/.forge/daemon.log 2>&1 &
sleep 1
forge list

Step 6: Verify config

cat ~/.forge/config.yaml 2>/dev/null || echo "No config - using defaults (agent: claude, model: sonnet, timeout: 10m)"

Step 7: Test with a quick job

forge run --agent claude --model haiku "Say hello in one sentence"

Report to user

Summarize:

Binary location and version
Daemon status and PID
Config file location and key settings
Available agents: claude, gemini, local (Ollama), lmstudio
MCP tools are now available: forge_submit, forge_status, forge_output, forge_list