Nx Generate
nomcopter/react-mosaic
Generate code using nx generators. An agent skill from nomcopter/react-mosaic.
Meta-skill for creating new Claude Code skills with configurable execution modes.
$ npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install catlog22/Claude-Code-Workflow skill-generator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/skill-generator .claude/skills/skill-generator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-generator" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-generator into .claude/skills/skill-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-generator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-generatorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install catlog22/Claude-Code-Workflow skill-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/skill-generator .agents/skills/skill-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-generator" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-generator into .agents/skills/skill-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-generator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install catlog22/Claude-Code-Workflow skill-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/skill-generator .cursor/skills/skill-generator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-generator" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-generator into .cursor/skills/skill-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-generator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/catlog22/Claude-Code-Workflow.git --path .claude/skills/skill-generator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install catlog22/Claude-Code-Workflow skill-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/skill-generator .gemini/skills/skill-generator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-generator" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-generator into .gemini/skills/skill-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-generator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install catlog22/Claude-Code-Workflow skill-generatorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/skill-generator .github/skills/skill-generator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-generator" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-generator into .github/skills/skill-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-generator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install catlog22/Claude-Code-Workflow skill-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/skill-generator .opencode/skills/skill-generator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-generator" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-generator into .opencode/skills/skill-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-generator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skill-generatorMeta-skill for creating new Claude Code skills with configurable execution modes.
Skill Generator is an agent skill from catlog22/Claude-Code-Workflow. Meta-skill for creating new Claude Code skills with configurable execution modes. Supports sequential (fixed order) and autonomous (stateless) phase patterns. Use for skill scaffolding, skill creation, or building new workflows. Triggers on "create skill", "new skill", "skill generator".
Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files (for example `phases/01-requirements-discovery.md`, `phases/02-structure-generation.md` and `phases/03-phase-generation.md`).
It sits in Development, covering Project scaffolding. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
AgentAskUserQuestionReadBashGlobGrepWriteFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Skill Generator loads about 5.2k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 1,004 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Agent, AskUserQuestion, Read, Bash, Glob, Grep, WriteAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 1,004 words, ~5,239 tokens.
.claude/skills/skill-generator/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.Meta-skill for creating new Claude Code skills with configurable execution modes.
┌─────────────────────────────────────────────────────────────────┐
│ Skill Generator │
│ │
│ Input: User Request (skill name, purpose, mode) │
│ ↓ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Phase 0-5: Sequential Pipeline │ │
│ │ ┌────┐ ┌────┐ ┌────┐ ┌────┐ ┌────┐ ┌────┐ │ │
│ │ │ P0 │→│ P1 │→│ P2 │→│ P3 │→│ P4 │→│ P5 │ │ │
│ │ │Spec│ │Req │ │Dir │ │Gen │ │Spec│ │Val │ │ │
│ │ └────┘ └────┘ └────┘ └─┬──┘ └────┘ └────┘ │ │
│ │ │ │ │
│ │ ┌────┴────┐ │ │
│ │ ↓ ↓ │ │
│ │ Sequential Autonomous │ │
│ │ (phases/) (actions/) │ │
│ └─────────────────────────────────────────────────────────┘ │
│ ↓ │
│ Output: .claude/skills/{skill-name}/ (complete package) │
│ │
└─────────────────────────────────────────────────────────────────┘Traditional linear execution model, phases execute in numeric prefix order.
Phase 01 -> Phase 02 -> Phase 03 -> ... -> Phase NUse Cases:
Examples: software-manual, copyright-docs
Intelligent routing model, dynamically selects execution path based on context.
---------------------------------------------------
Orchestrator Agent
(Read state -> Select Phase -> Execute -> Update)
---------------------------------------------------
|
---------+----------+----------
| | |
Phase A Phase B Phase C
(standalone) (standalone) (standalone)Use Cases:
Examples: issue-manage, workflow-debug
_shared/SKILL-DESIGN-SPEC.mdIMPORTANT: Before any generation operation, read the following specification documents. Generating without understanding these standards will result in non-conforming output.
| Document | Purpose | Priority |
|---|---|---|
| ../_shared/SKILL-DESIGN-SPEC.md | Universal design spec - defines structure, naming, quality standards for all Skills | P0 - Critical |
| specs/reference-docs-spec.md | Reference document generation spec - ensures generated Skills have proper phase-based Reference Documents with usage timing guidance | P0 - Critical |
| Document | Purpose |
|---|---|
| templates/skill-md.md | SKILL.md entry file template |
| templates/sequential-phase.md | Sequential Phase template |
| templates/autonomous-orchestrator.md | Autonomous Orchestrator template |
| templates/autonomous-action.md | Autonomous Action template |
| templates/code-analysis-action.md | Code Analysis Action template |
| templates/llm-action.md | LLM Action template |
| templates/script-template.md | Unified Script Template (Bash + Python) |
| Document | Purpose |
|---|---|
| specs/execution-modes.md | Execution Modes Specification |
| specs/skill-requirements.md | Skill Requirements Specification |
| specs/cli-integration.md | CLI Integration Specification |
| specs/scripting-integration.md | Script Integration Specification |
| Document | Purpose |
|---|---|
| phases/01-requirements-discovery.md | Collect Skill Requirements |
| phases/02-structure-generation.md | Generate Directory Structure |
| phases/03-phase-generation.md | Generate Phase Files |
| phases/04-specs-templates.md | Generate Specs and Templates |
| phases/05-validation.md | Validation and Documentation |
Input Parsing:
└─ Convert user request to structured format (skill-name/purpose/mode)
Phase 0: Specification Study (MANDATORY - Must complete before proceeding)
- Read specification documents
- Load: ../_shared/SKILL-DESIGN-SPEC.md
- Load: All templates/*.md files
- Understand: Structure rules, naming conventions, quality standards
- Output: Internalized requirements (in-memory, no file output)
- Validation: MUST complete before Phase 1
Phase 1: Requirements Discovery
- Gather skill requirements via user interaction
- Tool: AskUserQuestion
- Collect: Skill name, purpose, execution mode
- Collect: Phase/Action definition
- Collect: Tool dependencies, output format
- Process: Generate configuration object
- Output: skill-config.json
- Contains: skill_name, execution_mode, phases/actions, allowed_tools
Phase 2: Structure Generation
- Create directory structure and entry file
- Input: skill-config.json (from Phase 1)
- Tool: Bash
- Execute: mkdir -p .claude/skills/{skill-name}/{phases,specs,templates,scripts}
- Tool: Write
- Generate: SKILL.md (entry point with architecture diagram)
- Output: Complete directory structure
Phase 3: Phase/Action Generation
- Decision (execution_mode check):
- IF execution_mode === "sequential": Generate Sequential Phases
- Read template: templates/sequential-phase.md
- Loop: For each phase in config.sequential_config.phases
- Generate: phases/{phase-id}.md
- Link: Previous phase output -> Current phase input
- Write: phases/_orchestrator.md
- Write: workflow.json
- Output: phases/01-{name}.md, phases/02-{name}.md, ...
- ELSE IF execution_mode === "autonomous": Generate Orchestrator + Actions
- Read template: templates/autonomous-orchestrator.md
- Write: phases/state-schema.md
- Write: phases/orchestrator.md
- Write: specs/action-catalog.md
- Loop: For each action in config.autonomous_config.actions
- Read template: templates/autonomous-action.md
- Generate: phases/actions/{action-id}.md
- Output: phases/orchestrator.md, phases/actions/*.md
Phase 4: Specs & Templates
- Generate domain specifications and templates
- Input: skill-config.json (domain context)
- Reference: [specs/reference-docs-spec.md](specs/reference-docs-spec.md) for document organization
- Tool: Write
- Generate: specs/{domain}-requirements.md
- Generate: specs/quality-standards.md
- Generate: templates/agent-base.md (if needed)
- Output: Domain-specific documentation
Phase 5: Validation & Documentation
- Verify completeness and generate usage guide
- Input: All generated files from previous phases
- Tool: Glob + Read
- Check: Required files exist and contain proper structure
- Tool: Write
- Generate: README.md (usage instructions)
- Generate: validation-report.json (completeness check)
- Output: Final documentationExecution Protocol:
// Phase 0: Read specifications (in-memory)
Read('.claude/skills/_shared/SKILL-DESIGN-SPEC.md');
Read('.claude/skills/skill-generator/templates/*.md'); // All templates
// Phase 1: Gather requirements
const answers = AskUserQuestion({
questions: [
{ question: "Skill name?", header: "Name", options: [...] },
{ question: "Execution mode?", header: "Mode", options: ["Sequential", "Autonomous"] }
]
});
const config = generateConfig(answers);
const workDir = `.workflow/.scratchpad/skill-gen-${timestamp}`;
Write(`${workDir}/skill-config.json`, JSON.stringify(config));
// Phase 2: Create structure
const skillDir = `.claude/skills/${config.skill_name}`;
Bash(`mkdir -p "${skillDir}/phases" "${skillDir}/specs" "${skillDir}/templates"`);
Write(`${skillDir}/SKILL.md`, generateSkillEntry(config));
// Phase 3: Generate phases (mode-dependent)
if (config.execution_mode === 'sequential') {
Write(`${skillDir}/phases/_orchestrator.md`, generateOrchestrator(config));
Write(`${skillDir}/workflow.json`, generateWorkflowDef(config));
config.sequential_config.phases.forEach(phase => {
Write(`${skillDir}/phases/${phase.id}.md`, generatePhase(phase, config));
});
} else {
Write(`${skillDir}/phases/orchestrator.md`, generateAutonomousOrchestrator(config));
Write(`${skillDir}/phases/state-schema.md`, generateStateSchema(config));
config.autonomous_config.actions.forEach(action => {
Write(`${skillDir}/phases/actions/${action.id}.md`, generateAction(action, config));
});
}
// Phase 4: Generate specs
Write(`${skillDir}/specs/${config.skill_name}-requirements.md`, generateRequirements(config));
Write(`${skillDir}/specs/quality-standards.md`, generateQualityStandards(config));
// Phase 5: Validate & Document
const validation = validateStructure(skillDir);
Write(`${skillDir}/validation-report.json`, JSON.stringify(validation));
Write(`${skillDir}/README.md`, generateReadme(config, validation));IMPORTANT: This section demonstrates how skill-generator organizes its own reference documentation. This is the pattern that all generated Skills should emulate. See specs/reference-docs-spec.md for details.
Specification documents that must be read before any generation operation
| Document | Purpose | When to Use |
|---|---|---|
| ../_shared/SKILL-DESIGN-SPEC.md | Universal Skill design specification | Understand Skill structure and naming conventions - REQUIRED |
| specs/reference-docs-spec.md | Reference document generation specification | Ensure Reference Documents have proper phase-based organization - REQUIRED |
Collect Skill requirements and configuration
| Document | Purpose | When to Use |
|---|---|---|
| phases/01-requirements-discovery.md | Phase 1 execution guide | Understand how to collect user requirements and generate configuration |
| specs/skill-requirements.md | Skill requirements specification | Understand what information a Skill should contain |
Generate directory structure and entry file
| Document | Purpose | When to Use |
|---|---|---|
| phases/02-structure-generation.md | Phase 2 execution guide | Understand how to generate directory structure |
| templates/skill-md.md | SKILL.md template | Learn how to generate the entry file |
Generate specific phase or action files based on execution mode
| Document | Purpose | When to Use |
|---|---|---|
| phases/03-phase-generation.md | Phase 3 execution guide | Understand Sequential vs Autonomous generation logic |
| templates/sequential-phase.md | Sequential Phase template | Generate phase files for Sequential mode |
| templates/autonomous-orchestrator.md | Orchestrator template | Generate orchestrator for Autonomous mode |
| templates/autonomous-action.md | Action template | Generate action files for Autonomous mode |
Generate domain-specific specifications and templates
| Document | Purpose | When to Use |
|---|---|---|
| phases/04-specs-templates.md | Phase 4 execution guide | Understand how to generate domain-specific documentation |
| specs/reference-docs-spec.md | Reference document specification | IMPORTANT: Follow this spec when generating Specs |
Verify results and generate final documentation
| Document | Purpose | When to Use |
|---|---|---|
| phases/05-validation.md | Phase 5 execution guide | Understand how to verify generated Skill completeness |
Reference documents when encountering issues
| Issue | Solution Document |
|---|---|
| Generated Skill missing Reference Documents | specs/reference-docs-spec.md - verify phase-based organization is followed |
| Reference document organization unclear | specs/reference-docs-spec.md - Core Principles section |
| Generated documentation does not meet quality standards | ../_shared/SKILL-DESIGN-SPEC.md |
Documents for deep learning and design decisions
| Document | Purpose | Notes |
|---|---|---|
| specs/execution-modes.md | Detailed execution modes specification | Comparison and use cases for Sequential vs Autonomous |
| specs/cli-integration.md | CLI integration specification | How generated Skills integrate with CLI |
| specs/scripting-integration.md | Script integration specification | How to use scripts in Phases |
| templates/script-template.md | Script template | Unified Bash + Python template |
.claude/skills/{skill-name}/
├── SKILL.md # Entry file
├── phases/
│ ├── _orchestrator.md # Declarative orchestrator
│ ├── workflow.json # Workflow definition
│ ├── 01-{step-one}.md # Phase 1
│ ├── 02-{step-two}.md # Phase 2
│ └── 03-{step-three}.md # Phase 3
├── specs/
│ ├── {skill-name}-requirements.md
│ └── quality-standards.md
├── templates/
│ └── agent-base.md
├── scripts/
└── README.md.claude/skills/{skill-name}/
├── SKILL.md # Entry file
├── phases/
│ ├── orchestrator.md # Orchestrator (state-driven)
│ ├── state-schema.md # State schema definition
│ └── actions/
│ ├── action-init.md
│ ├── action-create.md
│ └── action-list.md
├── specs/
│ ├── {skill-name}-requirements.md
│ ├── action-catalog.md
│ └── quality-standards.md
├── templates/
│ ├── orchestrator-base.md
│ └── action-base.md
├── scripts/
└── README.mdIMPORTANT: This section demonstrates how skill-generator organizes its own reference documentation. This is the pattern that all generated Skills should emulate. See specs/reference-docs-spec.md for details.
Specification documents that must be read before any generation operation
| Document | Purpose | When to Use |
|---|---|---|
| ../_shared/SKILL-DESIGN-SPEC.md | Universal Skill design specification | Understand Skill structure and naming conventions - REQUIRED |
| specs/reference-docs-spec.md | Reference document generation specification | Ensure Reference Documents have proper phase-based organization - REQUIRED |
Collect Skill requirements and configuration
| Document | Purpose | When to Use |
|---|---|---|
| phases/01-requirements-discovery.md | Phase 1 execution guide | Understand how to collect user requirements and generate configuration |
| specs/skill-requirements.md | Skill requirements specification | Understand what information a Skill should contain |
Generate directory structure and entry file
| Document | Purpose | When to Use |
|---|---|---|
| phases/02-structure-generation.md | Phase 2 execution guide | Understand how to generate directory structure |
| templates/skill-md.md | SKILL.md template | Learn how to generate the entry file |
Generate specific phase or action files based on execution mode
| Document | Purpose | When to Use |
|---|---|---|
| phases/03-phase-generation.md | Phase 3 execution guide | Understand Sequential vs Autonomous generation logic |
| templates/sequential-phase.md | Sequential Phase template | Generate phase files for Sequential mode |
| templates/autonomous-orchestrator.md | Orchestrator template | Generate orchestrator for Autonomous mode |
| templates/autonomous-action.md | Action template | Generate action files for Autonomous mode |
Generate domain-specific specifications and templates
| Document | Purpose | When to Use |
|---|---|---|
| phases/04-specs-templates.md | Phase 4 execution guide | Understand how to generate domain-specific documentation |
| specs/reference-docs-spec.md | Reference document specification | IMPORTANT: Follow this spec when generating Specs |
Verify results and generate final documentation
| Document | Purpose | When to Use |
|---|---|---|
| phases/05-validation.md | Phase 5 execution guide | Understand how to verify generated Skill completeness |
Reference documents when encountering issues
| Issue | Solution Document |
|---|---|
| Generated Skill missing Reference Documents | specs/reference-docs-spec.md - verify phase-based organization is followed |
| Reference document organization unclear | specs/reference-docs-spec.md - Core Principles section |
| Generated documentation does not meet quality standards | ../_shared/SKILL-DESIGN-SPEC.md |
Documents for deep learning and design decisions
| Document | Purpose | Notes |
|---|---|---|
| specs/execution-modes.md | Detailed execution modes specification | Comparison and use cases for Sequential vs Autonomous |
| specs/cli-integration.md | CLI integration specification | How generated Skills integrate with CLI |
| specs/scripting-integration.md | Script integration specification | How to use scripts in Phases |
| templates/script-template.md | Script template | Unified Bash + Python template |
© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 17 other files in .claude/skills/skill-generator of catlog22/Claude-Code-Workflow.
Open the folder on GitHubat commit 07491b0
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in catlog22/Claude-Code-Workflow, which our catalogue first saw on October 7, 2026.
Skill Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Generator this skillcatlog22/Claude-Code-Workflow | 2.1k | — | ~5.2k | Automated safety check: Notes | MIT | |
| Nx Generatenomcopter/react-mosaic | 4.8k | 7 repos | ~1.9k | Automated safety check: Pass | Custom licence | |
| PonytailDavidObando/gsharp | 565 | 8 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Run Nx Generatornrwl/nx | 29k | 2 repos | ~592 | Automated safety check: Notes | MIT | |
| Conductor Setupgemini-cli-extensions/conductor | 3.8k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Mirage VFS Adapter Authoringstrukto-ai/mirage | 3.7k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
nomcopter/react-mosaic
Generate code using nx generators. An agent skill from nomcopter/react-mosaic.
DavidObando/gsharp
Forces the laziest solution that actually works, simplest, shortest, most minimal.
nrwl/nx
Run Nx generators with prioritization for workspace-plugin generators.
gemini-cli-extensions/conductor
Scaffolds the project and sets up the Conductor environment.
strukto-ai/mirage
Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.
siteboon/claudecodeui
Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.
catlog22/Claude-Code-Workflow
Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.
catlog22/Claude-Code-Workflow
CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.
catlog22/Claude-Code-Workflow
Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Check workflow delegation prompts against agent role definitions for content separation violations.
Categories
Meta-skill for creating new Claude Code skills with configurable execution modes. Skill Generator is an agent skill from catlog22/Claude-Code-Workflow. Meta-skill for creating new Claude Code skills with configurable execution modes.
Skill Generator fits situations like: skill scaffolding; building new workflows; skill generator.
Run `npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a claude-code`. Or copy the skill folder (.claude/skills/skill-generator in catlog22/Claude-Code-Workflow) into .claude/skills/skill-generator in your project. Claude Code loads it when a task matches its description.
Run `npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a codex`. Or copy the skill folder (.claude/skills/skill-generator in catlog22/Claude-Code-Workflow) into .agents/skills/skill-generator in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill skill-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-generator, .gemini/skills/skill-generator, .github/skills/skill-generator and .opencode/skills/skill-generator in your project.
SKILL.md names no scripts, command-line tools or credentials: Skill Generator is instructions for the agent only. Its frontmatter pre-approves these tools: Agent, AskUserQuestion, Read, Bash, Glob, Grep, Write.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Skill Generator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Skill Generator: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 565 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.
Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.