skills.rest
gusgad
gusgadCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agent-skills

Guides authoring and maintaining discoverable SKILL.md skill files for AI agents.

1|Updated Jul 18, 2025
Search Tags:#documentation#agent skills#ai agents#skill authoring#discoverability#frontmatter#skill.md
One-click install
npx skills add https://github.com/gusgad/service-agent-by-sap --skill agent-skills-gusgad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-skills
Source: https://github.com/gusgad/service-agent-by-sap/tree/main/.agents/skills/agent-skills
Command: npx skills add https://github.com/gusgad/service-agent-by-sap --skill agent-skills-gusgad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams accumulate reusable techniques that get lost or re-derived from scratch because there is no consistent standard for writing, naming, and structuring agent skills that future sessions can actually find and apply. ## Core Features & Use Cases - Authoring Standard: Defines the required SKILL.md frontmatter (name and description) and a recommended body structure covering overview, when to use, core pattern, and common mistakes. - Discoverability Guidance: Explains how to write trigger-only descriptions, choose searchable names, and use keywords so agents can find the skill. - Quality Checklist: Provides a completion checklist and criteria for deciding whether a technique deserves to become a skill at all. - Use Case: After solving a tricky debugging workflow, a contributor uses this skill to write a new SKILL.md under .agents/skills/ with a proper description field so future agent sessions can discover and reuse the technique. ## Quick Start Ask the agent to help you write a new skill under .agents/skills/ following the agent-skills authoring guidelines.

Frequently Asked Questions about agent-skills

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

FAQPage Schema
How do I write a SKILL.md file for an AI agent?▼

Create a SKILL.md with YAML frontmatter containing a hyphenated name and a description stating only when to use the skill. Follow with a Markdown body covering overview, when to use, the core pattern, and common mistakes.

What should go in the description field of a skill?▼

The description should state only the triggering conditions for using the skill, written in third person. Never summarize the workflow or process, because agents may act on the summary and skip reading the actual skill body.

When should I create a new agent skill?▼

Create a skill when a technique took real effort to work out, will plausibly be needed again, and applies broadly. Skip one-off fixes, things already documented upstream, or conventions better enforced by linting or CI checks.

How do I make an agent skill discoverable?▼

Use keywords an agent would actually search for, including real error messages and tool names. Name the skill by what it does using verb-first phrasing, keep the content lean, and cross-reference other skills by name rather than inlining them.

When should a skill use separate reference or script files?▼

Most skills need only SKILL.md. Add a reference file only for heavy material like a long API reference, and a scripts directory only for reusable executable tooling that is meant to be run rather than read.

Related Skills

Explore More Software Engineering Skills→
kk20300113-pngkk20300113-png

continuous-learning

Extract reusable problem-solving patterns from Claude Code session transcripts.

Community
Intermediate
cabeznocabezno

bmb-skills-hub

Generate index, embedding, skill-tree, and MCP manifest files from a skills directory.

Community
Intermediate
bcwgamesbcwgames

skill-creator

Create reusable skills with SKILL.md and metadata for future sessions.

Community
Intermediate
A-HazzardA-Hazzard

Code Style & ESLint

Enforce ESLint rules and strict TypeScript checks on codebases.

Community
Intermediate