skill-factory

Featured

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

AI & Automation 3,887 stars 365 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 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: ```bash command -v codex &> /dev/null && codex_status="Available" || codex_status="Not installed" command -v gemini &> /dev/null && gemini_status="Available" || gemini_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 Gemini CLI - <status> — Cross-provider diversity Antigravity CLI - <status> — Additional external-model challenge Claude - Orchestration + satisfaction scoring Spec: <path> Estimated: $0.50-2.00 / 15-45 min ``` Validation: All external providers unavailable → continue with Claude-only (warn us...

Details

Author
nyldn
Repository
nyldn/claude-octopus
Created
6 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

flow-spec

NLSpec authoring — use when you need a structured specification from multi-AI research and consensus

3,887 Updated today
nyldn
AI & Automation Listed

skill-maker

Create new Claude Code skills (or slash-commands) in a clean, consistent house style — XML phases, rolling-window state files, saved rules, checkpoint resumption, attribution conventions, and 14 compaction-with-preservation patterns. Use when the user asks to "make a skill", "create a skill", "build a skill", "scaffold a skill", "new skill", "skill for X", "make this a skill", "turn this into a skill", "make a slash command", "create a command", "wrap this workflow", "automate this", "add to my library", "another skill like X", or any phrasing implying turning a workflow into a reusable, well-structured skill. Single point of entry — loads the full style guide + all 14 compaction patterns + canonical scaffold.

1 Updated 1 weeks ago
adamjali
AI & Automation Listed

skill-authoring

How to write skills, CLAUDE.md/AGENTS.md, fix logs, and handoff documents that a weaker or zero-context model can actually execute. Load when authoring or updating any instruction file, SKILL.md, project memory, or institutional-knowledge document — including when converting lessons from a session into durable files — and when about to act on a recorded capability-negative ("no such flag", "the API can't do X") found in one. Not for writing user-facing docs or code comments.

2 Updated today
F-e-u-e-r