skill-creator

Create reusable SKILL.md files that capture workflows and instructions for future agent sessions.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/AmirEmad11/instabot --skill skill-creator-amiremad11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/AmirEmad11/instabot/tree/main/.local/secondary_skills/skill-creator
Command: npx skills add https://github.com/AmirEmad11/instabot --skill skill-creator-amiremad11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable workflows and conventions discovered during a session are lost when the conversation ends. This Skill captures those patterns as persistent, reusable skills so future agent instances can repeat the same task without re-explanation. ## Core Features & Use Cases - Guided Skill Authoring: Walks through intent capture, naming, frontmatter rules, and directory structure for new skills. - Progressive Disclosure Design: Enforces a three-level loading model (metadata, SKILL.md body, bundled references/scripts/assets) to keep context efficient. - Quality Checklist: Validates that descriptions include both what and when, names follow lowercase-hyphen rules, and files land in .agents/skills/. - Use Case: After refining a deployment checklist in conversation, ask to turn it into a skill so every future session triggers the same checklist automatically. ## Quick Start Turn the workflow we just used into a reusable skill saved under .agents/skills.

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 reusable skill for an AI agent?

Define a SKILL.md file with YAML frontmatter containing a name and description, then write step-by-step instructions in the body. Save it to .agents/skills/<skill-name>/SKILL.md so future sessions can discover and trigger it.

What should a skill description include to trigger reliably?

A skill description should state both what the skill does and when to use it, including explicit trigger phrases and scenarios. Vague descriptions under-trigger, so lean toward being specific and slightly pushy about activation contexts.

Where are custom skills stored and can platform skills be edited?

User-created skills live in .agents/skills/<skill-name>/SKILL.md and can be freely modified or deleted. Platform-provided skills live in .local/skills/ and are read-only.

How do I keep a large SKILL.md file manageable?

Keep SKILL.md under 500 lines and move overflow content into references/ subdirectories loaded on demand. For reference files over 300 lines, include a table of contents and point to them clearly from SKILL.md.

What are the naming rules for a new skill?

Skill names must be lowercase letters, numbers, and hyphens only, with a maximum of 64 characters. Examples include deploy-checklist and api-conventions.