@W-22578499 : Update Template Skill #113
Open
shivam-sf wants to merge 15 commits into
Open
Conversation
…ll (#1) After successful project creation, always run `code --add <projectPath>` to add the project to the current VS Code workspace. Failures are silently ignored so the workflow continues regardless.
…create CLI (#3) Replace all references to the `create_mule_project` MCP tool with the Anypoint CLI command `dx:mule:project:create`. The skill now instructs the agent to run CLI commands directly via Bash instead of calling an MCP server tool. - Update frontmatter description and compatibility - Replace all `create_mule_project` references with `dx:mule:project:create` - Remove `mule-mcp-server` dependency - Add concrete CLI invocation examples for Exchange, Local, and Scratch flows - Update schema reference with actual CLI flags and usage patterns
…late skill (#4) Before calling dx:mule:project:create, the agent must resolve the latest runtime version and compatible JDK by running dx:mule:runtime:list. This ensures projects are created with the current supported runtime instead of a hardcoded default.
Add Step 1b to build-mule-integration that asks the project source question (Exchange/Local/Scratch) when creating a new project. If user picks a template, the agent reads references/template-project-creation.md which contains the full Exchange (E1-E4) and Local (L1-L4) template flows. Scratch projects continue to Step 8 as before. - Create references/template-project-creation.md with full template workflow (Exchange + Local flows, confirmation gates, validation) - Copy search_templates.sh to build-mule-integration/scripts/ - Add Step 1b decision gate to SKILL.md - Add search_templates.sh to bundled scripts table - Bump version to 1.2.0
Scratch projects don't need environment resolution, so pass --skip-environment to avoid an unnecessary API call.
Its workflow now lives in build-mule-integration/references/template-project-creation.md as a conditional sub-file. Bumps package version to 1.1.0.
shivam-sf
changed the title
Master added PDK skills as 1.1.0. Our template removal is now 1.2.0.
leandrogilcarrano
previously approved these changes
Jun 10, 2026
Master added [1.1.1] (v12.0.0 sync). Our template sub-skill work becomes [1.2.1] sitting above it. Skill metadata version bumped from 1.2.0 to 1.2.1; package.json + package-lock.json aligned.
…gent-evaluation lab Pulls forward the skill content tested via mule-dx-agent-evaluation (template-eval-only pilot run) where it scored well across the realistic template-creation paths. Skill changes: - Step 1b options reordered so 'I want to generate from scratch without a template.' is the first option (default-safe). - Steps E5 / L5 continue-or-stop checkpoints added at the end of the Exchange and Local sub-flows. Agent always asks the user whether to proceed to connector discovery + flow generation or stop after template setup. - Local template format relaxed from .jar-only to .jar or .zip (the CLI already accepts both via --template-file). - Absolute-path / 'no relative ../scripts/...' rule for invoking bundled scripts, plus a 'why scripts instead of inline bash' rationale based on production-run failure analysis (resolved GAVs lost across Bash tool calls). - Phase 2 step ranges renumbered (Steps 8-17 from 8-18); flow XML generation cross-references corrected (Steps 10/12 instead of 11/13); pre-mvn validation script reference added to the troubleshooting cheatsheet. Versioning: - skill metadata: 1.2.1 -> 1.3.0 - package.json + package-lock.json: 1.2.1 -> 1.3.0 - CHANGELOG entry added.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Folds the standalone
create-project-templateskill intobuild-mule-integrationas a conditional sub-skill loaded viareferences/template-project-creation.md. Template-based project creation (Exchange template, local.jar) is now a branch withinbuild-mule-integrationat Step 1b instead of a separate top-level skill.Why
create-project-templateandbuild-mule-integration.Changes
build-mule-integration/SKILL.md— added Step 1b (Project Source Decision) between Steps 1 and 2; addedscripts/search_templates.shto the bundled-scripts table; added--skip-environmentto the Step 8dx mule project createexample for scratch projects.references/template-project-creation.md(new) — sub-skill with the full Exchange (E1–E4) and Local (L1–L4) flows, decision matrix, flow-switching rules,dx:mule:project:createschema,search_templates.shreference, success-report format, error-handling guide.scripts/search_templates.sh(moved fromcreate-project-template/scripts/) — Exchange template search (parallel public + private, dedup, rank, top-10 enrichment).create-project-template/build-mule-integration/references/template-project-creation.md.Versioning
SKILL.mdmetadata version:1.1.0→1.2.1.package.json/package-lock.json: bumped to1.2.1.CHANGELOG.md: new[1.2.1]entry above master's[1.1.1].Verification
template-project-creation.mdandsearch_templates.shpresent underbuild-mule-integration/;create-project-template/removed.npm pack --dry-runfromskills/mule-development/includes both new files; nocreate-project-template/paths.grep -r "create-project-template" skills/mule-development/returns zero matches.[1.1.1]resolved cleanly; both changelog entries preserved.