skill-creator

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/SaberAloui/agri-hub --skill skill-creator-saberaloui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/SaberAloui/agri-hub/tree/main/.local/secondary_skills/skill-creator
Command: npx skills add https://github.com/SaberAloui/agri-hub --skill skill-creator-saberaloui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable workflows, conventions, and task procedures discovered during a conversation are lost when the session ends. This Skill captures them as persistent, reusable skill files so future agent instances can repeat the same process without re-explanation. ## Core Features & Use Cases - Guided Skill Authoring: Walks through intent capture, naming rules, frontmatter requirements, 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 usage efficient. - Writing Standards: Provides rules for trigger-focused descriptions, imperative style, specificity matching, and a pre-flight checklist. - Use Case: After working through a deployment checklist with an agent, ask it to turn that process into a skill so the next session triggers it automatically whenever you mention deploying. ## Quick Start Turn the workflow we just completed 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 agent 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.

What naming rules apply to skill directories?▼

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

When should I split skill content into reference files?▼

Split content when SKILL.md approaches 500 lines or when the skill covers multiple domains or frameworks. Move overflow into a references/ directory and point to each file from SKILL.md with guidance on when to read it.

Where are user-created skills stored versus platform skills?▼

User-created skills go 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.