Magnus Hedemark f08b21d2d6 feat: add forgejo-cli skill — Forgejo/Gitea Git forge CLI
CLI wrapper for the Forgejo/Gitea REST API v1. Commands:
- me: current user profile
- repos: list user repositories
- search: search repositories by query
- issues: list issues in a repo (filters out PRs)
- view: view issue or PR details with body, labels, milestone
- prs: list pull requests with head/base branch info

All cli-builder patterns: --json, --dry-run, --quiet, --verbose,
lazy auth, emit() dual-output, structured logging, pre-parsed
global flags. Auth via FORGEJO_TOKEN (token auth header).

Signed-off-by: Jasper <magnus@groktop.us>
2026-05-21 23:14:20 -04:00

agent-skills

A collection of AI agent skills — reusable workflows, protocols, and knowledge packs for agentic systems. Skills follow the Agent Skills open format, making them compatible with any agent framework that supports the standard.

Skills

cli-builder

Build and refactor CLI tools for AI agent consumption. 10 universal patterns (non-interactive, --json, --dry-run, idempotent, lazy auth, progressive help), an agent-compatibility test suite, a Python API client pattern, and a bash scaffold template. Principles grounded in real failures from building 15+ agent-facing CLIs.

systematic-debugging

4-phase root cause debugging protocol: understand bugs before fixing. Covers schema/environment divergence, exception type specificity in fallback chains, progressive characterization grids for API/retrieval failures, dependency source detection (editable dev forks), macOS sandboxed application debugging, and the Rule of Three for recognizing architectural problems. Adapted from obra/superpowers (MIT) with significant expansion from real-world use.

tempest-cli

Hyper-local weather from a WeatherFlow Tempest station. Query current conditions, 7-day forecast, historical observations, and real-time UDP broadcasts. A complete reference implementation of the cli-builder patterns in a working, testable project — including the CLI binary and full API field layout reference.

software-architecture-analysis

Reverse-engineer a software codebase to understand its architecture, data flow, privacy posture, and feature surface — then produce a clean-room design document, PRD, or migration plan under new constraints (local-first, privacy-first, self-hosted). Includes an interface extraction pattern for designing swappable storage provider abstractions.

data-architect

Act as a virtual data architect. Discover data assets, assess maturity, evaluate platforms, design architectures, establish governance, and create migration plans. Covers modern data patterns (data mesh, data lakehouse, streaming, real-time analytics) with vendor evaluation frameworks and maturity models.

agent-skills

Reference for the Agent Skills open format itself — directory structure, frontmatter schema, naming conventions, and progressive disclosure model. Use this meta-skill when creating or reviewing any other skill in this repository.


Installation

Skills don't require installation in the traditional sense. They are loaded by your AI agent when triggered. Each agent framework documents its own skill directory path and loading mechanism — follow the links below for the authoritative setup guide for your harness.

Harness Setup Guide
Claude Code code.claude.com/docs/en/skills
OpenCode opencode.ai/docs/skills
OpenAI Codex developers.openai.com/codex/skills
GitHub Copilot docs.github.com/en/copilot/concepts/agents/about-agent-skills
Cursor cursor.com/docs/context/skills
Gemini CLI geminicli.com/docs/cli/skills
Hermes Agent See below

Hermes Agent

Hermes Agent loads skills from ~/.hermes/skills/, organized by category subdirectory:

cp -r cli-builder ~/.hermes/skills/devops/
cp -r systematic-debugging ~/.hermes/skills/software-development/
cp -r tempest-cli ~/.hermes/skills/devops/

Hermes loads skill metadata at session start. Use the /skills command to list available skills, and skill_view(name) to load a specific skill's full instructions. Skills can also be pinned for persistent availability.

Generic / Other Frameworks

The agentskills.io clients page maintains an up-to-date list of every agent framework that supports the Agent Skills format, with links to each one's setup instructions. Any framework listed there can load these skills — follow that framework's specific documentation for the correct directory path and loading mechanism.

For frameworks without built-in skill loading, the format is intentionally simple:

  1. Place the skill directory in your agent's accessible file path
  2. The agent reads SKILL.md when triggered by keywords in the task
  3. Supporting files in references/, templates/, and scripts/ are loaded on demand

You can also instruct your agent to read specific SKILL.md files at session start, or reference skills in your agent's system prompt or CLAUDE.md/AGENTS.md.


Contributing

Skills follow the Agent Skills specification. See the agent-skills reference skill for format details, and AGENTS.md in this repo for agent-specific loading and compliance guidance.

Before submitting a new skill:

  1. Ensure SKILL.md has valid YAML frontmatter (required: name, description)
  2. The name field must match the parent directory name
  3. Keep SKILL.md under 500 lines and 5,000 tokens
  4. Move detailed reference material to references/ for progressive disclosure
  5. Validate with skills-ref validate ./my-skill if available

License

MIT — see LICENSE.md for full terms.

S
Description
No description provided
Readme
24 MiB
Languages
Python 91.2%
Shell 5%
Ruby 2.1%
Go Template 0.5%
Rich Text Format 0.4%
Other 0.5%