create-project-template
Workflow for generating MuleSoft projects from Anypoint Exchange templates, local .jar templates, or from scratch via the `mule-mcp-server`. Use when users ask to "create a project", "generate project", "build integration", "create API", "use template", or "from template". Performs template discovery and calls create_mule_project only after explicit user confirmation; delegates flow generation to the `build-mule-integration` skill.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope, provides abundant natural trigger terms, explicitly states when to use it, and carefully delineates its boundaries from related skills. It uses proper third-person voice throughout and avoids vague language. The mention of requiring explicit user confirmation before project creation adds useful behavioral detail.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generating MuleSoft projects from Anypoint Exchange templates, local .jar templates, or from scratch; template discovery; calling create_mule_project; delegating flow generation. Very concrete and detailed. | 3 / 3 |
Completeness | Clearly answers both 'what' (generating MuleSoft projects from various template sources, template discovery, calling create_mule_project) and 'when' (explicit 'Use when' clause with specific trigger phrases). Also clarifies boundaries by noting delegation to another skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create a project', 'generate project', 'build integration', 'create API', 'use template', 'from template'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (MuleSoft project generation from templates via mule-mcp-server). Explicitly delineates its boundary from the 'build-mule-integration' skill, reducing conflict risk. The domain-specific terms like 'Anypoint Exchange', 'MuleSoft', and '.jar templates' make it very distinguishable. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionability and workflow clarity with concrete commands, parameter schemas, confirmation checkpoints, validation gates, and comprehensive error handling. However, it is severely undermined by extreme verbosity — the same rules and patterns are repeated many times across the three parallel flows, and identical XML prompt templates appear in full multiple times. Factoring shared patterns and splitting per-flow details into separate files would dramatically improve token efficiency without sacrificing clarity.
Suggestions
Factor the three parallel flows (Exchange, Scratch, Local) to eliminate duplicated confirmation/handoff steps — extract shared patterns (e.g., flow generation confirmation + handoff to build-mule-integration) into a single reusable section referenced by all three flows.
Remove redundant restatements of core rules — the 'do not call create_mule_project directly' instruction, confirmation checkpoints, validation standard, and delegation to build-mule-integration are each stated 4-10 times. State each rule once in Core Rules and reference it by name.
Consider splitting per-flow detailed steps (Exchange E1-E5, Scratch S1-S3, Local L1-L5) into separate referenced files, keeping only the decision logic, shared rules, and reference tables in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~450+ lines with massive repetition. The same rules (confirmation checkpoints, validation standard, delegation to build-mule-integration, local template format) are restated 5-10 times each. The three flows (Exchange, Scratch, Local) share nearly identical confirmation and handoff steps that are fully duplicated rather than factored out. XML template blocks for ask_followup_question are repeated verbatim across flows. Claude doesn't need to be told 'do not call create_mule_project directly' in 4+ separate places. | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance: exact bash commands for search_templates.sh, complete XML templates for user prompts, specific parameter schemas for create_mule_project with per-flow requirements, and a full worked example walkthrough. Every step has clear inputs and outputs. | 3 / 3 |
Workflow Clarity | The multi-step workflows are clearly sequenced (E1→E2→E3→E4→E5, S1→S2→S3, L1→L2→L3→L4→L5) with explicit confirmation checkpoints at template selection, project creation, and flow generation. Pre-flight checklists before create_mule_project, validation via mvn clean compile, error recovery paths, and flow-switching rules are all well-defined. The decision matrix and flow switching table provide excellent navigation. | 3 / 3 |
Progressive Disclosure | The skill references external resources (build-mule-integration skill, scripts/search_templates.sh) appropriately, and the Reference section at the end is well-organized. However, the main body is monolithic — the three nearly-parallel flows (Exchange, Scratch, Local) could be split into separate files with only the decision logic and shared rules in SKILL.md. No bundle files were provided to confirm script existence, but references are one-level deep and clearly signaled. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (701 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- mulesoft/mulesoft-dx
- Commit
32e2b58
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.