delete-mule-run-config
Call use_skill as your FIRST and ONLY action when the user asks to DELETE, REMOVE, or GET RID OF an existing run configuration for Mule applications. Use this ONLY for deleting/removing configurations, NOT for creating or editing. Trigger phrases include "delete config", "remove config", "get rid of config", "delete all configs", "remove all my run configs", "clean up configs". When you call use_skill, it must be the only tool call in that response.
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/mule-development/delete-mule-run-config/SKILL.mdQuality
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 a strong skill description that clearly defines its scope (deleting run configurations for Mule applications), provides abundant natural trigger phrases, and explicitly excludes adjacent operations (creating/editing) to minimize conflict risk. The only minor note is the inclusion of implementation details about tool calling behavior ('call use_skill as your FIRST and ONLY action', 'it must be the only tool call'), which are instructions to Claude rather than description content, but they don't detract from the description's effectiveness for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: DELETE, REMOVE, or GET RID OF run configurations for Mule applications. It also explicitly distinguishes itself from creating or editing configurations, which adds clarity. | 3 / 3 |
Completeness | Clearly answers both 'what' (delete/remove existing run configurations for Mule applications) and 'when' (explicit trigger phrases and a clear 'Use this ONLY for...' clause). Also includes negative scoping (NOT for creating or editing). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases: 'delete config', 'remove config', 'get rid of config', 'delete all configs', 'remove all my run configs', 'clean up configs'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: deleting Mule application run configurations. The explicit exclusion of create/edit operations and the domain-specific 'Mule applications' context make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent workflow clarity, providing concrete tool schemas, explicit confirmation steps, and thorough coverage of edge cases. However, it is severely over-engineered for a deletion task—the extreme verbosity (especially five full example conversations and fuzzy matching algorithm descriptions) wastes token budget, and the monolithic structure with no progressive disclosure makes it unnecessarily heavy for the context window.
Suggestions
Reduce the five example conversations to one or two representative examples, and move the rest to a separate EXAMPLES.md file referenced from the main skill.
Remove explanations of concepts Claude already knows (e.g., Levenshtein distance, what similarity matching means) and replace with concise directives like 'Use fuzzy matching for typos; suggest best match if >80% similar.'
Extract the detailed Smart Config Matching logic (Step 2) into a separate MATCHING.md reference file, keeping only a brief summary in the main skill.
Consolidate the repeated confirmation format (shown in instructions AND in every example) into a single template definition referenced throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Extensively explains conversational flows, matching algorithms (Levenshtein distance), and UI patterns that Claude already understands. The five detailed example conversations alone consume massive token budget repeating the same confirmation pattern. Much of this could be condensed to a decision table and one example. | 1 / 3 |
Actionability | Provides concrete TypeScript tool call schemas with exact parameter names, specific output formats, and detailed examples covering every scenario (exact match, fuzzy match, delete all, vague request, project-based search). The guidance is copy-paste ready with explicit tool invocation patterns. | 3 / 3 |
Workflow Clarity | Clear numbered step-by-step process with explicit validation checkpoints: mandatory first step (get_workspace_info), confirmation before deletion, error recovery for fuzzy matches, and explicit 'STOP and wait' instructions. The destructive operation (deletion) has a required confirmation step with exact format specified. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—including five lengthy example conversations, matching algorithm details, and edge case handling—is inlined in a single file. The examples and matching logic could easily be split into separate reference files. | 1 / 3 |
Total | 8 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | 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.