skill-authoring

Create reusable SKILL.md instruction files that extend agent capabilities across sessions.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/BotchaVarun/EduBot --skill skill-authoring-botchavarun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/BotchaVarun/EduBot/tree/main/.local/skills/skill-authoring
Command: npx skills add https://github.com/BotchaVarun/EduBot --skill skill-authoring-botchavarun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeatedly explaining the same workflows to an AI agent wastes time and produces inconsistent results. This Skill provides a structured process for capturing reusable knowledge, procedures, and workflows as persistent skill files that future agent sessions can discover and follow. ## Core Features & Use Cases - Skill File Creation: Guides the creation of SKILL.md files with proper YAML frontmatter (name and description) and instruction bodies written to .agents/skills/SKILLNAME/. - Discovery Optimization: Enforces naming rules (lowercase, hyphens, max 64 chars) and description best practices so skills trigger correctly in future sessions. - Authoring Guidance: Provides writing tips on conciseness, specificity, examples, and organizing large content into separate reference files. - Use Case: A user repeatedly asks the agent to review pull requests a certain way. Use this Skill to create a pr-review skill that codifies the review checklist and output format once, so every future PR review follows the same process. ## Quick Start Create a skill that teaches you how to review pull requests using my team's checklist and save it for future sessions.

Frequently Asked Questions about skill-authoring

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?▼

Write a SKILL.md file with YAML frontmatter containing a name and description, followed by Markdown instructions, and save it to .agents/skills/SKILLNAME/SKILL.md. The description determines when the agent will discover and use the skill.

What should a skill description include for discovery?▼

A skill description should state what the skill does and when to use it, within 1024 characters. Vague descriptions like 'Processes documents' fail to trigger; specific ones like 'Extracts text from PDF files when the user asks to parse PDFs' work reliably.

What are the naming rules for SKILL.md frontmatter?▼

The name field must be at most 64 characters and contain only lowercase letters, numbers, and hyphens, such as code-review or pr-review. The description field can be up to 1024 characters.

Where are agent skills stored and can I edit them?▼

User-created skills live in .agents/skills/ and are fully editable and deletable. Skills in ~/.local/skills/ are platform-provided and read-only, so they cannot be modified.

How do I handle a skill with too much content?▼

Keep SKILL.md under 500 lines and move large reference material into separate files, such as .agents/skills/SKILLNAME/reference/api.md. Link to those files from the main SKILL.md so they load only when needed.