skill-creator

Create, audit, repair, and validate Mixdog Agent Skills and their SKILL.md files.

6|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/tribgames/mixdog --skill skill-creator-tribgames
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/tribgames/mixdog/tree/main/src/defaults/skills/skill-creator
Command: npx skills add https://github.com/tribgames/mixdog --skill skill-creator-tribgames

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Writing a reliable Agent Skill requires correct frontmatter, a tight activation trigger, well-structured instructions, and validated resource paths; this Skill guides that entire lifecycle so skills activate and behave as intended. ## Core Features & Use Cases - Skill authoring workflow: Recover the real workflow, choose scope (machine-global, plugin, or built-in), and draft the smallest complete SKILL.md with proper field separation. - Structural validation: Run the bundled validate-skill.mjs script to check frontmatter fields, folder-name matching, listing-line budgets, and referenced resource paths. - Auditing and repair: Diagnose whether a defect is routing, instructions, resources, or integration, and audit entire skill sets against a checklist before editing. - Use Case: A user says their custom skill never activates. This Skill inspects the when_to_use trigger, checks the 250-character listing budget, validates the directory, and fixes the routing boundary. ## Quick Start Ask the agent to create a new Mixdog skill for a recurring workflow, or to audit and repair an existing skill that fails to activate.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Mixdog Agent Skill?▼

Create a directory containing a SKILL.md file with YAML frontmatter defining name and description, plus a when_to_use trigger line. The directory name must match the frontmatter name, and the body holds the operating instructions loaded after activation.

Why is my skill not activating or being selected?▼

Selection depends only on the listing line built from name and when_to_use, which is cut at 250 characters. If when_to_use is missing or weak, the model sees only the name; the UI description is never sent to the model for routing.

How do I validate a SKILL.md file structure?▼

Run the bundled validate-skill.mjs script with Node.js, passing the skill directory path. It checks frontmatter fields, folder-name matching, description and trigger budgets, and whether referenced resources exist, reporting errors and warnings.

What is the difference between description and when_to_use in skill frontmatter?▼

The description is a UI-only summary capped at 100 characters and never sent to the model. The when_to_use field is the model-facing selection trigger capped at 250 characters and should contain user intents plus a not-for boundary.

Where should a Mixdog skill be placed to be discovered?▼

Discovery precedence is machine-global skills in the Mixdog data directory, then enabled plugin skills, then built-ins under src/defaults/skills. Project-local .mixdog/skills directories are not discovered by Mixdog.