Ekko Skill creator

Use this Skill when the user wants to create a new reusable Skill or maintain an existing one in the current Ekko Profile.

Design the right Skill

A Skill should provide reusable, non-obvious guidance that changes how Ekko handles a recognizable class of requests. Do not turn a one-off answer, a temporary workaround, or an unrelated product preference into a permanent Skill.

• Preserve the user's requested scope, tools, and authorization boundaries.
• Assume the model already has general reasoning ability; include domain knowledge, decision criteria, fragile procedures, or reusable automation that materially improves results.
• Make the frontmatter description concise and discriminating for fallback discovery.
• Maintain a compact metadata.keywords list of specific English phrases for host-side exact matching. These keywords are not injected into the model; Ekko injects only available Skill names and lets the main model map requests in any language to a name before calling skill_view.
• Keep shared instructions in SKILL.md. Put substantial conditional detail in references and load it only when relevant.
• Add scripts only when deterministic repeated execution is more reliable than recreating the logic each time.
• Refer only to tools and Skills available in the target Ekko environment.

Ask a question only when missing information would materially change the Skill's purpose, location, side effects, or supported workflow.

Ekko Skill structure

Every Skill requires:

skill-name/
└── SKILL.md

Optional text resources supported by skill_manage:

references/   Detailed guidance needed only in particular modes
templates/    Reusable text templates
scripts/      Node.js, Python, or shell helpers
assets/       Text assets used in generated output