Automated summary
A trigger-based workflow dispatcher for AXEL core operations that matches an explicit trigger to the registered workflow, falling back to on-demand loading of reference documentation when nothing matches.
Strengths
- Enforces a strict loading order with AXEL-Bootstrap.md read first, before any other document
- Lazy reference loading: documents are read only when the request's keywords hit their 'ask' attributes
- Creator workflows (create:*) must apply AXEL-Checklist.md step by step, which structures document production
- Cleanly separates two modes: workflow execution by trigger, and documentation-answering fallback
Limitations
- Only works where the AXEL plugin is installed and ${CLAUDE_PLUGIN_ROOT} resolves
- Reference matching is keyword-based, so an ambiguous request may load the wrong document or none at all
- No error handling is described if AXEL-Bootstrap.md is missing or unreadable
Use it when an AXEL command passes an explicit trigger, or when a user asks about AXEL concepts, agents, workflows, and conventions.
Avoid it outside the AXEL plugin ecosystem or for general coding tasks unrelated to AXEL artifacts.
Security analysis
CautionThe skill is a workflow dispatcher. No curl|sh, rm -rf, secret exfiltration, base64 payloads, or safety-disabling instructions appear. However, it declares Bash/Write/Edit/Task and pulls in numerous external files resolved at runtime by environment path, so actual behavior depends on unseen documents. This is a legitimate use of powerful tools, warranting 'caution' rather than 'safe'.
- •Declares Bash, Write, Edit, and Task tools, granting broad filesystem/execution capability (though no destructive command is actually specified)
- •Loads many external reference/workflow files via ${CLAUDE_PLUGIN_ROOT} paths, so behavior depends on files not included in this SKILL.md
- •Instructs the agent to auto-load and dispatch documents based on keyword matching to user prompts, which widens the scope of what gets read into context
Examples
Explain how AXEL workflows differ from AXEL agents, and when I should use each one in my project.Create a new AXEL command for running the test suite, and make sure it follows the AXEL checklist and conventions.Run the AXEL workflow triggered by 'create:skill' to scaffold a new skill document.name: skill-axel-core description: | Trigger-based workflow dispatcher for AXEL core operations. Receives explicit trigger from command and dispatches to matching workflow. type: skill model: inherit allowed-tools:
- Read
- Write
- Edit
- Glob
- Bash
- Task
- AskUserQuestion
AXEL Skill: Core
<document type="skill">
<enforcement>
<![CDATA[
DOCUMENT LOADING ORDER:
- AXEL-Bootstrap.md MUST be loaded FIRST before processing this skill
- Bootstrap provides core AXEL rules and understanding guidelines
- All other documents depend on Bootstrap being in context
PATH RESOLUTION:
- Read the `src`, `ref`, or `target` attribute from the document XML to locate referenced files
- ${CLAUDE_PLUGIN_ROOT} resolves to plugin installation directory
DOCUMENT REFERENCES:
- CLAUDE.md is automatically loaded by Claude Code - DO NOT add to <documents> block
- Use Read tool to access CLAUDE.md content during execution
TRIGGER-BASED DISPATCH:
- Command sends explicit trigger parameter
- Skill matches trigger against workflows registry
- Matching workflow is loaded and executed
DOCUMENT CREATION VALIDATION:
- Creator workflows (create:*) MUST load and apply AXEL-Checklist.md step-by-step
- Location: ${CLAUDE_PLUGIN_ROOT}/references/AXEL-Checklist.md
DOCUMENT RESOLUTION:
- When trigger doesn't match workflows, resolve reference documents
- Analyze prompt keywords against documents:references "ask" attributes
- Load relevant reference documents on-demand
- Use loaded references to answer user request
]]>
</enforcement>
<objective>
Trigger-based workflow dispatcher for AXEL core operations.
Matches incoming trigger to workflow registry and executes.
When no workflow matches, resolves and loads reference documentation
to answer user requests about AXEL concepts and patterns.
</objective>
<documents name="bootstrap" load="always" mode="context">
<read src="${CLAUDE_PLUGIN_ROOT}/AXEL-Bootstrap.md"/>
<understanding>
!! MANDATORY: READ → UNDERSTAND → APPLY !!
Bootstrap provides AXEL core, enforcement rules, and understanding guidelines.
</understanding>
</documents>
<documents name="references" load="on-demand" mode="context">
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Standards.md" ask="standard, pattern, element"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Conventions.md" ask="convention, style, format"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Agent.md" ask="agent, autonomous, executor"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Workflow.md" ask="workflow, process, step"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Skill.md" ask="skill, expertise, capability"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Command.md" ask="command, slash, invoke"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Brainstorm.md" ask="brainstorm, discovery, ideation"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Memory.md" ask="memory, context, persistence"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/references/AXEL-Claude.md" ask="claude, configuration, project"/>
<understanding>
!! LOAD ON-DEMAND: Trigger Mismatch Fallback !!
When to Load:
- ONLY when resolved trigger doesn't match workflows:operations registry
- User request doesn't map to any workflow trigger
- User asking about AXEL concepts, patterns, or documentation
How to Load:
- Analyze prompt keywords from user request
- Match keywords against "ask" attributes of each reference document
- Load all matching reference documents into context
- Use loaded references to provide comprehensive answer
Examples:
- "what is an agent?" → load AXEL-Agent.md (ask: agent, autonomous, executor)
- "how to write workflow?" → load AXEL-Workflow.md (ask: workflow, process, step)
- "what are the standards?" → load AXEL-Standards.md (ask: standard, pattern, element)
Available References:
- Standards & Conventions (structural rules)
- All AXEL document types (Agent, Workflow, Skill, Command, Memory, Brainstorm, Claude)
</understanding>
</documents>
<role>
Workflow dispatcher that routes trigger-based requests
to appropriate AXEL core operation workflows.
</role>
<capabilities>
- Receive trigger parameter from command
- Match trigger against workflows registry
- Load and execute matching workflow
- Pass parameters to workflow
- Resolve reference documents when workflow not matched
- Answer user requests using loaded reference documentation
</capabilities>
<workflows name="operations" load="on-trigger">
<!-- brainstorm -->
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/brainstorm/AXEL-Brainstorm-Bootstrap.md" trigger="brainstorm"/>
<!-- creators -->
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/creators/AXEL-Agent-Creator-Workflow.md" trigger="create:agent"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/creators/AXEL-Brainstorm-Creator-Workflow.md" trigger="create:brainstorm"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/creators/AXEL-Workflow-Creator-Workflow.md" trigger="create:workflow"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/creators/AXEL-Skill-Creator-Workflow.md" trigger="create:skill"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/creators/AXEL-Command-Creator-Workflow.md" trigger="create:command"/>
<!-- utilities -->
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/utilities/AXEL-Fix-Workflow.md" trigger="fix"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/utilities/AXEL-Compact-Workflow.md" trigger="compact"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/utilities/AXEL-Bypass-Workflow.md" trigger="bypass"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/utilities/AXEL-Install-Workflow.md" trigger="install"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/workflows/utilities/AXEL-Commit-Workflow.md" trigger="commit"/>
<understanding>
!! MANDATORY: READ → UNDERSTAND → APPLY !!
Trigger-based workflow registry. Match resolved trigger to execute workflow.
</understanding>
</workflows>
<execution flow="linear"><![CDATA[
WORKFLOW DISPATCH:
Step 1 - Receive Parameters:
- trigger: ${param.trigger} (optional)
- prompt: ${param.prompt} (optional)
- Additional: topic, doc_type, target_path
Step 2 - Resolve Trigger:
- IF trigger provided → use directly
- IF trigger empty → detect from prompt:
Keyword Priority (first match):
1. "create" + "agent" → create:agent
2. "create" + "brainstorm" → create:brainstorm
3. "create" + "workflow" → create:workflow
4. "create" + "skill" → create:skill
5. "create" + "command" → create:command
6. "brainstorm" → brainstorm
7. "validate" | "fix" → validate
8. "compact" | "archive" → compact
9. "bypass" | "permissions"→ bypass
10. "install" | "init" → install
11. "commit" → commit
Step 3 - Match Workflow:
- Check if resolved trigger matches workflows:operations registry
- IF trigger matched → GO TO Step 4 (Execute workflow)
- IF trigger NOT matched → GO TO Step 3.1 (Resolve Documents)
Step 3.1 - Resolve Documents (fallback when no workflow match):
- Analyze prompt keywords
- Match keywords to documents:references "ask" attributes
- Load relevant reference documents from on-demand registry
→ Example: "agent" keyword → load AXEL-Agent.md
→ Example: "workflow" keyword → load AXEL-Workflow.md
→ Example: "standard" keyword → load AXEL-Standards.md
- Use loaded references to answer user request
- SKIP Step 4
Step 4 - Execute Workflow:
- IF trigger starts with "create:":
→ Load ${CLAUDE_PLUGIN_ROOT}/references/AXEL-Checklist.md
→ Execute matched workflow with parameters
→ Validate created document step-by-step against checklist (all phases)
- ELSE:
→ Execute matched workflow with parameters
]]></execution>
<understanding/>
</document>
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/axel-workflow-dispatcher-mmbizjtz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/axel-workflow-dispatcher-mmbizjtz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/axel-workflow-dispatcher-mmbizjtz/download' --output '.skill-downloads/axel-workflow-dispatcher-mmbizjtz/SKILL.md.part' && mv '.skill-downloads/axel-workflow-dispatcher-mmbizjtz/SKILL.md.part' '.skill-downloads/axel-workflow-dispatcher-mmbizjtz/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/axel-workflow-dispatcher-mmbizjtz/SKILL.md' && test -s '.skill-downloads/axel-workflow-dispatcher-mmbizjtz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/skill-axel-core' && cp -R '.skill-downloads/axel-workflow-dispatcher-mmbizjtz' '.claude/skills/skill-axel-core'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/axel-workflow-dispatcher-mmbizjtz'openskills read 'axel-workflow-dispatcher-mmbizjtz'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/axel-workflow-dispatcher-mmbizjtz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.