elite-skill-forge

Generates production-ready Claude SKILL.md files from domain, workflow, or intent descriptions.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/sabiscore/swarmxq --skill elite-skill-forge-sabiscore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elite-skill-forge
Source: https://github.com/sabiscore/swarmxq/tree/main/.ai/skills/elite-skill-forge
Command: npx skills add https://github.com/sabiscore/swarmxq --skill elite-skill-forge-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective Claude skills by hand is error-prone: descriptions undertrigger, bodies lack structure, and mega-prompts get crammed into single unfocused files. This Skill turns any domain, workflow, or pasted prompt into complete, copy-paste-ready SKILL.md files with trigger-optimized frontmatter and concrete instructions. ## Core Features & Use Cases - Skill Generation from Intent: Produces complete SKILL.md files with frontmatter, core protocol, output format, quality gates, and 8+ activation trigger phrases. - Mega-Prompt Decomposition: Ingests existing system prompts or documents, extracts discrete workflows, and splits multi-role prompts into focused single-job skills. - Suite Generation: Maps a domain into non-overlapping workflows and generates a coordinated skill suite with a Skill Map showing chaining relationships. - Use Case: Paste a 500-line system prompt for a customer-support agent and receive three focused skills (triage, escalation, resolution) each with explicit triggers and output formats. ## Quick Start Ask the AI to turn your described workflow or pasted prompt into a reusable Claude skill with a complete SKILL.md file.

Frequently Asked Questions about elite-skill-forge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude skill from an existing prompt?

Paste the existing system prompt or document and the Ingestion Protocol extracts discrete workflows, identifies the primary job, and decomposes multi-role mega-prompts into focused skills. Each output is a complete, copyable SKILL.md file.

What makes a good SKILL.md description for triggering?

A good description covers both when to trigger and what the skill does, including at least five concrete example trigger phrases. It should be explicit and slightly pushy, since Claude tends to undertrigger skills with vague descriptions.

Can I generate a suite of related skills for one domain?

Yes, the skill maps a domain into discrete non-overlapping workflows and generates one skill per workflow. It also produces a Skill Map showing how skills chain, where the output of one skill feeds the next.

What structure must a generated SKILL.md file contain?

Each generated skill includes YAML frontmatter with name and description, a behavioral role declaration, a core step-by-step protocol, an explicit output format, quality gates, edge case handling, and an Activation Triggers section with at least eight phrases.

When should a mega-prompt be split into multiple skills?

Split when a single prompt performs multiple distinct jobs or roles, since multi-role prompts undertrigger and dilute instructions. The skill flags scope creep and confirms the decomposition with you before generating the focused skills.