skill-creator

Skill Creator

Help the user turn a repeatable task into a skill that works in Kelivo. Write instructions and explain the result in the user's language.

Understand the task

Use the current conversation first: extract the goal, inputs, expected output, important corrections, and tools that actually worked. Ask only for missing details that would change the skill. A clear request is enough to start drafting.

For an update, read the existing SKILL.md and the resources affected by the change. Preserve the user's workflow and unrelated content. Treat examples as examples; only turn a preference into a general rule when the user wants it.

Write the skill

A skill is a directory with a UTF-8 file named exactly SKILL.md. Begin with YAML frontmatter containing name and description, followed by Markdown:

---
name: meeting-actions
description: Turn meeting notes into decisions, action items, and open questions. Use when the user asks to summarize a meeting or extract follow-up tasks.
---

# Meeting Actions

Read the provided notes and separate decisions, action items, and open questions.
For each action, include the owner and deadline when given; mark missing values
as unspecified. Keep tentative proposals distinct from agreed decisions.

Choose a short lowercase name using letters, digits, and hyphens, at most 64 characters. Use the same name for its directory. Write a concise description that says what the skill does and when to use it; Kelivo shows only the first 200 characters in the model's skill list. Put detailed instructions in the body.

Include the task-specific decisions, output shape, and completion criteria that improve the result. Keep the entrypoint focused. Add these directories only when the task needs them:

• references/: detailed guidance consulted for a particular case. Link each reference from SKILL.md and say when to read it.
• scripts/: reusable, deterministic operations. Check the required runtime is available and execute new or changed scripts against a small example.
• assets/: templates or other files used in the output.

Use relative paths for resources. Avoid private absolute paths, credentials, and instructions that assume a particular developer's computer. Refer to configured environment variables by name when credentials are needed. Dependencies belong in the instructions only if the workflow needs them; a Markdown-only skill requires neither Python nor Node.js.

Deliver in Kelivo