Skills

Skill Factory

Run a full build-and-ship pipeline from a spec, use for hands-off project generation

Install

npx skills add nyldn/claude-octopus --skill skill-factory -g -a claude-code -y
Repository
nyldn/claude-octopus4.4k
Category
Engineering
Updated
3d ago
License
MIT
Context cost
Mediumabout 1,876 tokens
Runs scripts
No, instructions only

What it does

Run a full build-and-ship pipeline from a spec, use for hands-off project generation

STOP - SKILL ALREADY LOADED

DO NOT call Skill() again. Execute directly.

EXECUTION CONTRACT (MANDATORY, 8-step sequence, CANNOT SKIP)

STEP 1: Clarifying Questions (MANDATORY)

Ask via AskUserQuestion BEFORE any other action:

  1. Spec location, path to NLSpec file, or paste inline
  2. Satisfaction target override (Use spec default / Custom 0.80-0.99)
  3. Cost approval, ~0.50-2.00 USD for ~20-30 agent calls (Approve / Approve --ci / Decline)

If spec path provided inline with the command, use it but still ask remaining questions. If user says "skip", use defaults and proceed. DO NOT proceed to Step 2 until answered.

STEP 2: Display Visual Indicators (MANDATORY, BLOCKING)

Check providers:

command -v codex &> /dev/null && codex_status="Available" || codex_status="Not installed"
command -v agy &> /dev/null && agy_status="Available" || agy_status="Not installed"

Display banner:

🐙 CLAUDE OCTOPUS ACTIVATED - Dark Factory Mode
Pipeline: Parse → Scenarios → Embrace → Holdout → Score → Report

Providers:
  Codex CLI - <status>, Scenario generation + holdout evaluation
  Antigravity CLI - <status>, Additional external-model challenge
  Claude - Orchestration + satisfaction scoring

Spec: <path>
Estimated: 0.50-2.00 USD / 15-45 min

Validation: All external providers unavailable → continue with Claude-only (warn user about reduced diversity). At least one available → proceed normally.

STEP 3: Validate Spec File (MANDATORY, Validation Gate)

if [[ ! -f "<spec_path>" ]]; then
    echo "ERROR: Spec file not found at <spec_path>"
    exit 1
fi
# Check minimum content
word_count=$(wc -w < "<spec_path>")
if [[ $word_count -lt 20 ]]; then
    echo "WARNING: Spec is very thin ($word_count words). Results may be limited."
fi

If spec file missing → STOP, ask user for correct path. If spec is thin (< 50 words) → WARN but proceed. DO NOT proceed past this gate if file does not exist.

Read the whole SKILL.md on GitHub

More in Engineering