Skip to content

Skills

A skill (SKILL.md) is the actual instruction package behind a command — commands themselves are thin dispatchers onto a skill. A skill loads one of two ways: because a command invoked it by name, or because your agent's own judgment matched its description against what you asked for, without you ever typing a slash command at all. Either path runs the same instructions.

This page is the narrative layer. For the exhaustive, generated list of every skill this repo ships — full descriptions and category groupings — see the Skills reference. This page is about what skills are and how they get invoked; that page is the inventory.

Why skills exist as a separate layer from commands

A command gives you a short name to type. A skill is where the actual behavior lives — instructions, guardrails, and (for many skills) the specific sequence of steps an agent follows to do the work correctly and consistently, every time, instead of improvising a slightly different approach each session. Splitting the two apart means:

  • The same skill can be reached two ways — by name (/g-status) or by relevance (you just describe what you want and the right skill's description matches).
  • A skill can be reused across multiple entry points without duplicating its instructions.
  • You never hand-edit a skill's local copy in your project directly — behavior changes land upstream and arrive on your next platform install or update, so a fix or improvement reaches every project running that skill, not just the one you happened to be in when you noticed it.

Skill categories worth knowing

Skills cover a wide range of ground — task/bug management, code review, security scanning, release management, cross-project coordination, marketing, vault/knowledge management, platform integration for each supported AI IDE, and more. A few groups you'll reach for early:

  • Task & bug ownership — g-skl-tasks and g-skl-bugs are the single source of truth for everything task- and bug-related: index files, individual records, status transitions, sync validation.
  • Review & quality — g-skl-code-review, g-skl-security-scan, and g-skl-verify-ladder cover code review, static-analysis-style vulnerability scanning, and configurable multi-level completion gates.
  • Coordination — the g-skl-wpac-* family and g-skl-workspace handle everything about talking to, or working alongside, other gald3r projects.
  • Vault & research — g-skl-vault, g-skl-recon-*, and g-skl-crawl build and query a file-first knowledge base from docs, repos, and web pages you feed it.
  • Platform integration — one g-skl-platform-* skill per supported AI IDE (Cursor, Claude Code, Copilot, Codex, and the rest of the roster), each documenting exactly how that platform's own extension points map onto gald3r.

Full inventory

The Skills reference lists every shipped skill, grouped by category, with its full description. Use that page as your search target; use this one to get oriented first.