Agent Skills Framework

No Change
adopt
First Added:April 20, 2026 Updated: July 7, 2026

Agent Skills Framework packages repeatable agent know-how as a folder with a required SKILL.md (YAML frontmatter plus markdown instructions). We adopt it as the only realistic way to make agent behavior portable across models and providers.

Summary

WhenAction
Building portable ops for coding agentsUse the layout: one folder per skill, SKILL.md with strong name and description
One-off prompts in a single toolSkip; inline rules or tool-native config may be enough
Importing community skillsVet each repo; use Agent Skills - Sources; run in sandbox first

Portability: Tool-native rules, system prompts, and vendor config do not travel. A SKILL.md folder ports across Claude Code, Cursor, Codex, Gemini, and other runtimes with path changes at most. That is the practical baseline for shared agent behavior in a multi-model estate.

Layout: skills/<skill-name>/SKILL.md plus optional scripts/, references/, assets/. The description field is the primary trigger signal. Keep the body under ~500 lines. Push detail into reference files.

In this vault: agent-skills/skills/ mirrors the pattern. gbrain two-layer pages and identity files in AGENTS.md / CLAUDE.md sit alongside skills.

Details

Required Frontmatter

1
2
3
4
---
name: my-skill          # lowercase, hyphens; matches folder name
description: "What it does and when to use it (trigger keywords live here)."
---

Skill Types (Informal)

TypePurposeExample
CapabilityTeach a concrete tool or APIapple-reminders, proofread
BehavioralLayer policy on other skillsreminders-gtd, proofread-blog
DomainYour outcome-specific workflowmorning-briefing, company-research

Runtimes in the Garden

See Agent Skills - Sources for official docs, awesome lists, and marketplaces.