CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-mule-run-config

Call use_skill as your FIRST and ONLY action when the user asks to CREATE a NEW run configuration for Mule applications. Use this ONLY for creating new configurations from scratch, NOT for editing existing ones. Trigger phrases include "create config", "new run config", "set up config", "add config". When you call use_skill, it must be the only tool call in that response.

57

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mule-development/create-mule-run-config/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with a clear decision branch and verification checkpoint, but it suffers from significant repetition and an inconsistent tool name that together hurt conciseness and actionability. Progressive disclosure is middling because everything lives in one large inline file with no references.

Suggestions

Consolidate the repeated rules (EXACT name, numbered-not-bulleted, scope required) into a single "Important Notes" section and reference it instead of restating throughout.

Reconcile the tool name — pick one of "create_run_configuration" or "manage_run_configuration" (operation "create") and use it consistently across the intro and Step 4.

Move the five example conversations and scenario walkthroughs into a separate references/EXAMPLES.md to reduce inline length and improve progressive disclosure.

DimensionReasoningScore

Conciseness

Noticeably verbose: the "use EXACT name from the create response", "numbered list not bullets", and "scope required" rules are each restated 3–4 times, and the "Handling Common Scenarios" section overlaps heavily with the five "Example Conversations".

2 / 5

Actionability

Provides concrete tool-call code blocks, parameter structures, and five worked examples, but the tool is named inconsistently ("create_run_configuration" in the intro vs "manage_run_configuration" with operation "create" in Step 4), which would break copy-paste execution.

4 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced with an upfront specific-vs-vague decision branch and an explicit "use the EXACT name from the create response" verification checkpoint; validation is appropriately deferred to the tool for this non-destructive task.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but no bundle files exist and all ~340 lines (including five examples and scenario walkthroughs that could be split out) are inlined in SKILL.md with no external references.

3 / 5

Total

13

/

20

Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly conveys what the skill does and when to use it, with strong trigger phrases and an explicit scope boundary against editing. Its main weakness is the second-person imperative voice and a focus on invocation mechanics over capability breadth, which caps specificity.

Suggestions

Rewrite in third person (e.g., "Creates new run configurations for Mule applications") to lift the specificity score and avoid the voice penalty.

Lead with the capability rather than invocation mechanics — state the concrete actions before the use_skill calling rules.

Add a couple more natural trigger variants (e.g., "launch config", "run configuration") to push trigger-term coverage toward 5.

DimensionReasoningScore

Specificity

States one concrete capability ("CREATE a NEW run configuration for Mule applications") but is dominated by invocation mechanics; base 3 reduced by 1 per the rubric's second-person voice penalty ("Call use_skill as your...", "Use this ONLY", "When you call...").

2 / 5

Completeness

Explicitly answers both "what" (create new Mule run configurations) and "when" (with concrete trigger phrases and an explicit invocation trigger), satisfying the top anchor.

5 / 5

Trigger Term Quality

Lists natural phrases a user would say ("create config", "new run config", "set up config", "add config") with good synonym coverage, though a few natural variants like "launch config" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Mule run configs) with an explicit "NOT for editing existing ones" boundary; minor residual overlap risk with sibling edit/execute skills keeps it just below 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mulesoft/mulesoft-dx

Path

skills/mule-development/create-mule-run-config/SKILL.md

Revision

b8cef7d

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill