skill-authoring

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeatedly re-explaining the same workflows to an AI agent wastes time and produces inconsistent results. This Skill lets you capture reusable knowledge, procedures, and workflows as persistent skill files that future agent sessions can discover and follow. ## Core Features & Use Cases - Skill Creation Workflow: Guides naming conventions (lowercase, hyphens), file placement in .agents/skills/, and the required SKILL.md frontmatter format with name and description fields. - Discovery-Focused Writing Guidance: Explains how to write descriptions that trigger the skill at the right time, with concrete good and bad examples. - Authoring Best Practices: Covers conciseness, matching specificity to fragility, using examples, splitting large content into reference files, and composing skills that reference other skills. - Use Case: After walking an agent through your team's PR review process, ask it to save that workflow as a pr-review skill so every future session applies the same checklist automatically. ## Quick Start Create a skill that teaches you how to review pull requests using our 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, then place it in `.agents/skills/SKILLNAME/SKILL.md`. The body holds the instructions, examples, and workflows the agent follows when the skill activates.

What should a skill description include for discovery?▼

A skill description must state what the skill does and when to use it, in under 1024 characters. Vague descriptions like "Processes documents" fail; specific triggers like "Extracts text from PDF files. Use when the user asks to parse PDFs" work.

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

User-created skills live in `.agents/skills/` and are fully editable and deletable. Platform-provided skills in `~/.local/skills/` are read-only and managed by the platform.

What are the naming rules for a SKILL.md file?▼

The skill name must be at most 64 characters using only lowercase letters, numbers, and hyphens, such as `code-review` or `pr-review`. The file itself must be named SKILL.md inside a directory matching the skill name.

How do I handle a skill that is too long for one file?▼

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.