Skip to content
/

agentskills.io — Agent Skills Open Standard

asyncope-agentskills-io · agentskills/agentskills · ★ 19k · last commit 2026-05-20

Primitive shape 1 total
Hooks 1
00

Summary

agentskills/agentskills — Summary

agentskills.io is the official open standard specification repository for the Agent Skills format — a cross-platform, cross-vendor standard for giving AI agents portable, loadable capability packages. Originally developed by Anthropic and released as an open standard, the repo now functions as the specification governance hub with documentation at agentskills.io.

Problem it solves: AI agents from different vendors (Claude Code, Gemini CLI, Codex, etc.) have incompatible capability extension formats; Agent Skills defines a single portable format (a folder with a SKILL.md file) that works across all compliant agents via progressive disclosure (discovery → activation → execution).

Distinctive trait: The only framework in the corpus that is a standard specification rather than a framework implementation — its value is defining the format that every other skill repository (including anthropics/skills, google/agents-cli, MicrosoftDocs/mcp) implements. It ships a SessionStart hook for the reference implementation (agentskills/agentskills) plus skills-ref content as a Python library for development tooling.

Target audience: AI tool developers who want to implement skills support in their agent; skill authors who want to publish portable skills; enterprises building cross-platform AI workflows.

Scope: 19,405 GitHub stars, Apache-2.0 (code) + CC-BY-4.0 (docs), 30 contributors, 1,190 forks, active since early 2025.

Differs from seeds: Unlike superpowers (Archetype 1 — behavioral enforcement framework for Claude Code), agentskills.io is the open standard that superpowers and other skill packs implement. It is above the implementation layer — it defines what a skill is, not how to use skills to enforce behaviors. Closest to how the W3C or OpenAPI Spec relates to individual implementations.

01

Overview

agentskills/agentskills — Overview

Origin

The Agent Skills format was originally developed by Anthropic and shipped as the anthropics/skills repo. It was then extracted as an open standard and placed under the agentskills GitHub organization. The spec repo (this repo) hosts the specification, docs, and governance; anthropics/skills remains the reference gallery.

Philosophy

"A standardized way to give AI agents new capabilities and expertise." "Skills solve this by packaging procedural knowledge and company-, team-, and user-specific context into portable, version-controlled folders that agents load on demand."

Three core tenets:

  1. Portability: A skill built for Claude Code works in Gemini CLI, Codex, or any compliant agent
  2. Progressive disclosure: Agents load skill descriptions first (light), full instructions only when matched (heavy) — minimizing idle context cost
  3. Procedural knowledge packaging: Skills encode how to do something, not just what to do — they are repeatable, auditable procedures

The Three Stages of Skill Loading

1. DISCOVERY   → agent loads name + description only (low context cost)
2. ACTIVATION  → task matches skill description → full SKILL.md loaded
3. EXECUTION   → agent follows instructions, runs bundled scripts/references

Open Development

"The Agent Skills format was originally developed by Anthropic, released as an open standard, and has been adopted by a growing number of agent products."

The repo accepts external contributions via CONTRIBUTING.md. A Discord server (discord.gg/MKPE9g8aUy) serves as the community hub.

Adoption

The Client Showcase at agentskills.io/clients lists all compliant agent products. By 2026-05-26, adopters include Claude Code, Gemini CLI, Codex, Microsoft Learn MCP, and others.

02

Architecture

agentskills/agentskills — Architecture

Distribution

  • Type: methodology-doc + reference specification
  • Install: No install — spec consumed by reading docs at agentskills.io
  • Skills tooling (skills-ref/): Python package with pyproject.toml, installable via uv
  • License: Apache-2.0 (code), CC-BY-4.0 (docs)

Repository Structure

agentskills/agentskills/
├── .claude/
│   ├── hooks/
│   │   └── session-start.sh    # SessionStart hook for internal dev use
│   └── settings.json           # Registers SessionStart hook
├── skills-ref/                  # Python reference implementation library
│   ├── CLAUDE.md               # Development guidance
│   ├── src/                    # Python source
│   ├── tests/                  # Test suite
│   ├── pyproject.toml          # Package config
│   └── uv.lock
├── CONTRIBUTING.md
├── LICENSE
├── README.md
└── package.json               # Mintlify docs dev script

Skill Format Specification

The canonical skill format is:

my-skill/
├── SKILL.md          # REQUIRED: metadata (YAML front-matter) + instructions
├── scripts/          # OPTIONAL: executable code
├── references/       # OPTIONAL: documentation files
├── assets/           # OPTIONAL: templates, resources
└── ...               # Any additional files

SKILL.md Required Fields

---
name: my-skill-name           # lowercase, hyphens for spaces
description: "..."            # When to activate this skill (critical for discovery)
---

SKILL.md Optional Fields

metadata:
  author: ...
  license: ...
  version: ...
  requires:
    bins: [...]
    install: "..."
context: fork                 # Used by MicrosoftDocs/mcp to indicate context mode
compatibility: "..."          # Fallback instructions

Target AI Tools

Any skills-compatible agent. See agentskills.io/clients for the full list.

Required Runtime

  • uv (for skills-ref Python development)
  • node / mint (for Mintlify documentation)
  • No runtime for consuming/using skills — just a compatible agent
03

Components

agentskills/agentskills — Components

This Repo's Own Components

The repo ships minimal tooling for its own development:

Hooks (1)

Hook Event Path
session-start.sh SessionStart .claude/hooks/session-start.sh

Purpose: Checks if Mintlify CLI is installed (used for docs development, not for skill delivery).

#!/usr/bin/env bash
# Session start hook for agentskills documentation project
echo '{"async":true,"asyncTimeout":15000}'

# Check if Mintlify CLI is installed
if ! command -v mint &> /dev/null; then
  echo "Mintlify CLI not installed. Install with: npm i -g mint"
fi

Python Library (skills-ref/)

A Python reference library for skill-related tooling. The repo contains:

  • src/ — Python source code for skills reference implementation
  • tests/ — pytest test suite
  • pyproject.tomluv-based package config with ruff for formatting/linting

Documentation Site

  • package.json with "dev": "cd docs && npx mint dev" — Mintlify-powered documentation at agentskills.io

The Specification Itself

The spec lives at agentskills.io/specification and defines:

  • Required SKILL.md structure (name + description mandatory fields)
  • Progressive disclosure loading model (discovery → activation → execution)
  • Optional metadata fields (author, license, version, requires.bins)
  • Directory conventions (scripts/, references/, assets/)
  • Cross-compatibility expectations

The repo does NOT itself ship skill examples — it delegates to anthropics/skills for reference examples and links to them from the README.

05

Prompts

agentskills/agentskills — Prompts

Verbatim Excerpt 1: Skills Reference CLAUDE.md (Developer Guidance)

File: skills-ref/CLAUDE.md Technique: Project-scoped developer guidance (not a skill instruction — an agent behavior guide for working on the skills-ref library itself)

# Development

## Code Quality

Format and lint with ruff:

```bash
uv run ruff format .
uv run ruff check --fix .

Testing

Run tests with pytest:

uv run pytest

**Note**: This is a minimal CLAUDE.md — it only covers tooling commands. The `agentskills/agentskills` repo uses CLAUDE.md for its own development, not as a skill delivery vehicle.

## Verbatim Excerpt 2: Agent Skills README — Progressive Disclosure Model

**File**: `README.md` (conceptual specification)
**Technique**: Process specification as prose — defines agent behavior through description

```markdown
## How do Agent Skills work?

Agents load skills through **progressive disclosure**, in three stages:

1. **Discovery**: At startup, agents load only the name and description of each
available skill, just enough to know when it might be relevant.

2. **Activation**: When a task matches a skill's description, the agent reads the
full `SKILL.md` instructions into context.

3. **Execution**: The agent follows the instructions, optionally executing bundled
code or loading referenced files as needed.

Full instructions load only when a task calls for them, so agents can keep many
skills on hand with only a small context footprint.

Prompting technique: The "progressive disclosure" model IS a prompting architecture — agents are instructed to load only skill descriptions at startup (low token cost), then load full instructions on match. This is a context-management pattern embedded in the spec, not just a feature description.

Key Design Principle in the Spec

The description field in SKILL.md front-matter is the most important prompt surface:

  • It determines WHEN the skill activates
  • It must be specific enough for the agent's description matcher to trigger correctly
  • The entire activation mechanism depends on the agent's ability to match user intent to this description

Skill authors are effectively writing "activation triggers" — a form of retrieval-prompt engineering.

09

Uniqueness

agentskills/agentskills — Uniqueness & Positioning

Differs from Seeds

This repo is categorically different from all 11 seed frameworks: it is a standard specification, not a framework implementation. The seeds (superpowers, spec-kit, claude-flow, BMAD, taskmaster-ai, etc.) are implementations — they make choices about how to use agents. agentskills.io defines the vocabulary those implementations use.

The closest analogy in tech: agentskills.io is to skill packs what the JSON Schema spec is to JSON validators — it defines correctness, not behavior.

Within the seeds, no analog exists. The closest pattern is how kiro defines its own IDE-native spec format — but kiro's format is proprietary and IDE-locked, while agentskills.io is explicitly cross-platform.

Distinctive Properties

  1. Standard vs implementation: Only repo in the corpus whose primary value is defining the format, not implementing functionality
  2. Progressive disclosure architecture: The three-stage load model (discovery → activation → execution) is a novel context-management contribution to the agent skill ecosystem
  3. Anthropic origin → open governance: The format was released by Anthropic but is now community-governed, giving it vendor-neutral credibility
  4. Multi-vendor adoption: Claude Code, Gemini CLI, Codex, and Microsoft Learn MCP all implement the standard — verified cross-vendor portability
  5. Activation trigger as prompt engineering: The description field in SKILL.md IS a prompt — it's the retrieval query that determines when skills activate

Observable Failure Modes

  • Spec fragmentation: Downstream implementations (Google agents-cli adds metadata.requires.bins, MicrosoftDocs adds context: fork) extend the spec in ways that reduce cross-tool portability
  • Description quality as activation bottleneck: Poorly written descriptions cause wrong-skill activation or no activation; the spec provides no guidance on description quality
  • No verification: No conformance test suite to verify agent implementations comply

Cross-References in Batch

  • anthropics/skills implements this spec (reference gallery)
  • google/agents-cli extends and implements this spec (adds metadata.requires + multi-skill packaging)
  • MicrosoftDocs/mcp implements this spec (adds context: fork extension)
  • ccplugins-awesome plugins may implement this spec (via .claude-plugin format)
04

Workflow

agentskills/agentskills — Workflow

No Application Workflow

This is a specification repo, not a workflow framework. There are no development lifecycle phases, no approval gates, and no artifact sequences for end users.

Specification Governance Workflow

The implicit workflow for the spec itself:

  1. Proposal: Contributors submit issues/PRs on GitHub
  2. Discussion: Community review via GitHub Issues + Discord
  3. Acceptance: Maintainers merge spec changes
  4. Documentation: Updated at agentskills.io
  5. Adoption: Downstream agent products implement the updated spec

Documentation Development Workflow

For contributors to the docs:

# Install Mintlify CLI
npm i -g mint

# Run local docs dev server
npm run dev   # runs: cd docs && npx mint dev

The session-start.sh hook checks for this tooling at session start.

Python Library Development Workflow

For the skills-ref library:

# Format and lint
uv run ruff format .
uv run ruff check --fix .

# Run tests
uv run pytest

Approval Gates

None for skill authors. The spec defines what is required (name + description), and agent products validate against these requirements at skill load time.

Artifacts

Phase Artifact
Spec authoring SPECIFICATION.md updates at agentskills.io
Skill authoring SKILL.md with YAML front-matter + instructions
Reference implementation skills-ref Python library
06

Memory Context

agentskills/agentskills — Memory & Context

Context Architecture

The Agent Skills spec defines a context architecture through progressive disclosure:

Discovery Layer (Low Context)

At agent startup, only name and description fields are loaded for all available skills. This creates a lightweight skill index in context.

Activation Layer (On-Demand Load)

When the agent matches a task to a skill's description, the full SKILL.md content is loaded into context. This is a context-on-demand pattern.

Execution Layer (References)

During execution, skills can reference additional files (references/, assets/) which are loaded as needed — further lazy-loading.

Memory Model

The spec itself defines no persistence model. Skills are stateless instructions — they are loaded per session, per task match.

Individual skill implementations may build state on top of the format:

  • Scripts in scripts/ can read/write files
  • References in references/ are static documentation
  • No built-in session memory, no vector store, no database

Context Footprint Design Goal

"Full instructions load only when a task calls for them, so agents can keep many skills on hand with only a small context footprint."

This is the spec's primary context management contribution — the design explicitly addresses the "loading too many instructions upfront consumes context" problem that naive skill systems face.

State in the skills-ref Library

The Python skills-ref library handles skill discovery and loading logic for implementors — but the spec itself remains stateless at the skill format level.

07

Orchestration

agentskills/agentskills — Orchestration

Scope

This is a specification repository. Orchestration decisions are made by individual agent products that implement the spec, not by the spec itself.

What the Spec Specifies

The Agent Skills spec defines:

  • How skills are discovered (name + description loading at startup)
  • How skills are activated (description matching when task is relevant)
  • How skills are executed (full instructions + optional script execution)

It does NOT specify:

  • How multiple skills interact or chain
  • How agents coordinate with each other
  • What model handles which skill

Agent-Level Orchestration (Implementor's Choice)

Each compliant agent (Claude Code, Gemini CLI, etc.) decides:

  • How to handle skill conflicts (two skills matching the same task)
  • Whether to load multiple skills simultaneously
  • How to chain skill outputs

Isolation Mechanism

None specified in the standard. Individual agent products handle isolation.

Multi-Model

Not specified. The metadata.requires field can specify what binaries a skill needs (bins: [agents-cli]) but not which model should execute it.

Execution Mode

Event-driven / activation-based: skills activate when a task matches, not continuously.

Cross-Tool Portability

High — this is the spec's primary design goal. A skill written to the standard works in any compliant agent.

08

Ui Cli Surface

agentskills/agentskills — UI/CLI Surface

Dedicated CLI Binary

None in this specification repo. The skills-ref Python library can be built and run with uv, but there is no user-facing CLI binary for skill management.

The ecosystem does ship CLIs in other places:

  • npx skills add google/agents-cli — community-built skills installer (referenced in Google agents-cli README)
  • Individual agent CLIs (Claude Code /plugin, Gemini CLI, Codex) handle skill loading

Documentation Site

agentskills.io — built with Mintlify, the primary consumer-facing interface for:

  • Specification documentation
  • Getting started guides
  • Client showcase (agents that support skills)
  • Contributing guide

Run locally with: npm run devcd docs && npx mint dev

IDE Integration

  • Claude Code: Skills work as Claude Code plugins (via .claude-plugin/ format)
  • Gemini CLI: Skills work via gemini-extension.json
  • Codex: Skills work via .codex-plugin/ format (where applicable)

The agentskills.io spec abstracts above all these — individual agent products handle the IDE integration.

Observability

None at the spec level. Implementation-dependent.

Discord Community

discord.gg/MKPE9g8aUy — the primary community interaction point for questions, skill sharing, and spec discussions.

Related frameworks

same archetype · same primary tool · same memory type

Context-Engineering Handbook ★ 9.0k

Provides a first-principles, research-grounded vocabulary and learning path for context engineering — the discipline of designing…

walkinglabs/learn-harness-engineering ★ 6.6k

Teach harness engineering from first principles (12 lectures + 6 projects) and provide a scaffolding skill (harness-creator) that…

Awesome Harness Engineering (walkinglabs) ★ 2.7k

Curate the authoritative reference list of articles, benchmarks, and tools for harness engineering — the practice of shaping the…

cline-memory-bank (nickbaumann98) ★ 581

Custom instructions + 6-file hierarchical Markdown memory bank so Cline maintains full project context across sessions, with a…

FPF (First Principles Framework) ★ 372

Provides a formal pattern language for making reasoning explicit, traceable, and publishable in mixed human/AI engineering work —…

nexu-io/harness-engineering-guide ★ 134

Provide a practical, code-first reference guide to harness engineering — from first principles to production patterns —…