AGENTS.md — Agent Briefing for iberi22/skills

Overview

This repository is a curated registry of agent skills — reusable expertise modules that can be loaded by AI agents (e.g., via SWAL, Codex, Claude Code, or any agent framework that supports skill injection).

Each skill lives in skills/<category>/<skill-name>/ and is defined by a SKILL.md file with YAML frontmatter.

How to Use These Skills

1. Load by ID

Reference a skill by its id (declared in frontmatter). Example:

skills:
  - id: nextjs
  - id: python
  - id: content-creator

2. Load by Category

You can also load all skills within a category:

skills:
  - category: marketing

3. Raw URL Access

Each skill exposes a raw_url pointing to its SKILL.md on GitHub (raw). This is useful for dynamic loading at runtime:

https://raw.githubusercontent.com/iberi22/skills/main/skills/<category>/<skill-name>/SKILL.md

4. Manifest

The canonical registry is at _registry/manifest.yaml. It contains metadata for all skills: id, name, description, category, tags, path, raw_url, authors, etc. Parse this to discover available skills programmatically.

Format Conventions (v2)

All SKILL.md files follow the v2 format:

---
id: unique-skill-id
name: Display Name
category: category-name
tags:
  - tag1
  - tag2
goals:
  - "One-line description of what this skill enables."
  - "Another goal or context."
authors:
  - Author Name
---

# Content

Markdown body with system prompt, instructions, examples, and constraints.

Required Frontmatter Fields

Optional Frontmatter Fields

Category Taxonomy

Note: Category counts are auto-generated in _registry/manifest.yaml.

Contributing

Adding a New Skill

1. Create a folder: skills/<category>/<skill-name>/
2. Add SKILL.md with valid YAML frontmatter and markdown body.
3. Optionally add companion files (e.g., setup.md, examples/).
4. Run python3 scripts/manifest-generator.py to regenerate the manifest.
5. Open a Pull Request.

PR Checklist

• SKILL.md frontmatter is valid YAML (run a YAML linter).
• id is unique across the entire registry.
• category matches an existing folder or is added to taxonomy.
• goals are concise and actionable.
• No sensitive data (API keys, passwords, internal URLs) in content.

CI / Lint

Pull requests are validated by GitHub Actions:

• YAML lint — all SKILL.md frontmatters must parse cleanly.
• ID uniqueness — no duplicate skill IDs.
• Manifest freshness — manifest.yaml must be up to date (or the manifest workflow will auto-commit it after merge).

Automation

Questions?

Open an issue or reach out via the repo discussions.