use
How to use Forge to submit headless agent jobs, check status, and retrieve output via MCP tools. Use when the user wants to delegate work to a background agent, run a task on another LLM, or interact with forge.
Best use case
use is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
How to use Forge to submit headless agent jobs, check status, and retrieve output via MCP tools. Use when the user wants to delegate work to a background agent, run a task on another LLM, or interact with forge.
Teams using use should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/use/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How use Compares
| Feature / Agent | use | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
How to use Forge to submit headless agent jobs, check status, and retrieve output via MCP tools. Use when the user wants to delegate work to a background agent, run a task on another LLM, or interact with forge.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Forge: Headless Agent Job Runner Forge runs tasks on LLM agents in the background via a daemon. Interact through MCP tools. ## MCP Tools ### forge_submit Submit a job. Returns a job ID. **Required:** `task` (string) - the prompt/task description. **Optional:** | Parameter | Type | Description | |-----------|------|-------------| | `agent` | string | `claude` (default), `gemini`, `local`, `lmstudio` | | `model` | string | Agent-specific: `sonnet`, `haiku`, `opus`, `gemini-2.5-pro`, etc. | | `timeout` | string | Duration: `30s`, `10m` (default), `1h` | | `input_files` | string[] | File paths to include as context | | `output_format` | string | `markdown` (default), `json`, `yaml`, `code`, `raw` | | `constraints` | string[] | Output validation constraints | | `tags` | string[] | Tags for filtering/organization | ### forge_status Check job status. **Required:** `job_id` (string). ### forge_output Get completed job result. **Required:** `job_id` (string). Returns: output content, metadata (agent, model, duration, tokens, cost). ### forge_list List jobs. **Optional:** `status` filter (`pending`, `running`, `completed`, `failed`), `limit` (default 20). ## Workflow ``` 1. forge_submit → returns job_id 2. forge_status → poll until "completed" or "failed" 3. forge_output → retrieve the result ``` ## Job States `pending` → `claimed` → `dispatched` → `running` → `validating` → `delivering` → `completed` Any state can transition to `failed`. ## Tips - **Daemon must be running** for jobs to process. If jobs stay `pending`, check with `forge_status` or run `/forge:setup`. - **Jobs are async** - submit returns immediately. Poll status or use `forge_list` to monitor. - **Claude agent** uses Claude CLI with full tool use (file editing, bash). Other agents are completion-only. - **Input files** let you pass context files to the job agent. - **Constraints** validate output (e.g., `["non-empty", "min-length:100"]`). ## When NOT to Use - For tasks that should happen in the current session (just do them directly). - When you need interactive back-and-forth with the user during the task. - Forge is for fire-and-forget background work.
Related Skills
Example Skill
Brief description of what this skill does and the domain expertise it provides.
vulnerability-patterns
Index of vulnerability detection pattern skills. Routes to core patterns (universal) and language-specific patterns for security scanning.
vuln-patterns-languages
Language-specific vulnerability detection patterns for JavaScript/TypeScript, Python, Go, Java, Ruby, and PHP. Provides regex patterns and grep commands for common security vulnerabilities.
vuln-patterns-core
Universal vulnerability detection patterns applicable across all programming languages. Includes hardcoded secrets, SQL/command injection, path traversal, and configuration file patterns.
scan
Run a security assessment using deterministic static analysis tools with LLM-powered triage
results
View the most recent security scan results without re-running the scan
remediation-library
Index of security remediation skills. Routes to specialized skills for injection, cryptography, authentication, and configuration vulnerabilities.
remediation-injection
Security fix patterns for injection vulnerabilities (SQL, Command, XSS). Provides language-specific code examples showing vulnerable and secure implementations.
remediation-crypto
Security fix patterns for cryptographic vulnerabilities (weak algorithms, insecure randomness, TLS issues). Provides language-specific secure implementations.
remediation-config
Security fix patterns for configuration and deployment vulnerabilities (path traversal, debug mode, security headers). Provides language-specific secure implementations.
remediation-auth
Security fix patterns for authentication and authorization vulnerabilities (credentials, JWT, deserialization, access control). Provides language-specific secure implementations.
fix
Fix or guide remediation for a specific security finding from the latest scan report