Creating-Skills

Creating a custom skill involves defining its purpose in markdown, writing a SKILL.md checklist, and optionally bundling scripts. The Skill guides you through requirements gathering, directory setup, and template variable configuration so your automation works across different environments and persists across sessions.

Yes, the Skill supports integrating deterministic scripts callable from Bash alongside your skill definition. Scripts are bundled with portable template variables for paths, enabling self-contained automation that runs consistently regardless of environment.

Ask the Skill to create a new skill with your workflow name and describe what you want to automate. It enforces a required SKILL.md checklist, guides requirements gathering, and generates a ready-to-install skill with directory structure and optional script integration built in.

No; the Skill provides a repeatable method focused on markdown instructions and checklists. Script bundling is optional—you can create skills with written instructions alone. The guided process handles requirements gathering and directory setup for you.

Custom skills use portable template variables for cross-environment paths instead of hardcoded values. This ensures your skill definition and bundled scripts function consistently whether you're on different machines, workspaces, or configurations.

A ready-to-install skill must complete the required SKILL.md checklist, include a proper directory structure, and optionally contain self-contained scripts. The creation process enforces these requirements and produces a skill you can immediately add to your profile.