Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: AI & models
8,992 results · page 189 of 300
- View details
clui-cc-claude-overlaySkillAI & models
Command Line User Interface for Claude Code — a floating macOS desktop overlay with multi-tab sessions, permission approval UI, voice input, and skills marketplace.
Ready to connect★ 81
- View details
- View details
- View details
- View details
- View details
- View details
- View details
craft-content-modelingSkillAI & models
Craft CMS 5 content modeling — sections, entry types, fields, Matrix, relations, project config, and content architecture strategy. Covers choosing section types, designing entry types and field layouts, selecting field types, configuring Matrix and nested entries, relations and eager loading, and m
Ready to connect★ 81
- View details
craft-garnishSkillAI & models
Garnish — Craft CMS's built-in JavaScript UI toolkit for the control panel. ALWAYS load when writing, editing, or reviewing JavaScript that runs in the Craft CP — plugin CP assets, custom field type JS, element index JS, CP webpack config, or code importing garnishjs / referencing window.Garnish. Al
Ready to connect★ 81
- View details
craft-php-guidelinesSkillAI & models
Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section
Ready to connect★ 81
- View details
craft-plugin-releaseSkillAI & models
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking
Ready to connect★ 81
- View details
director-modeSkillAI & models
Direct substantial repository work across Claude Code, Codex CLI, or Grok Build with a concise brief, parallel agents, evidence-based completion, and optional cross-CLI continuation. Use for project onboarding, multi-step implementation, agent coordination, verification planning, low-interruption se
Ready to connect★ 81
- View details
evolving-loopSkillAI & models
Self-Evolving Development Loop - Dynamic skill generation with learning and evolution
Ready to connect★ 81
- View details
getting-startedSkillAI & models
Guided five-minute onboarding for Director Mode Lite across Claude Code, Codex CLI, and Grok Build. Use after installation or when choosing a first workflow.
Ready to connect★ 81
- View details
gitxSkillAI & models
Portable Git workflow skill for AI coding agents that turns messy AI-generated changes into clean Git history. Use for smart Conventional Commits, logical commit splitting, branches, checks, pull and push, GitHub PRs and issues, secret scanning, commit planning, Git status and history, repository di
Ready to connect★ 81
- View details
hooks-checkSkillAI & models
Validate hooks configuration and scripts. Use after adding or editing hooks in settings.json, before committing hook changes, or when a hook fails to fire.
Ready to connect★ 81
- View details
interop-routerSkillAI & models
Suggest whether Claude Code, Codex CLI, or Grok Build is a useful next collaborator, without launching a CLI or changing controls. Use when comparing the three CLIs, planning a handoff, or deciding whether an independent implementation or review would help.
Ready to connect★ 81
- View details
loadSkillAI & models
Load context from an earlier Claude Code or Codex session, selected by conversation name or recency. Explicit invocation only: `/load` in Claude Code, `$load` in Codex. Never trigger this from ordinary wording such as "load" or "continue".
Ready to connect★ 81
- View details
mcp-checkSkillAI & models
Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
Ready to connect★ 81
- View details
session-relaySkillAI & models
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same
Ready to connect★ 81
- View details
swift-testingSkillAI & models
Expert guidance on Swift Testing best practices, patterns, and implementation. Use when developers mention: (1) Swift Testing, @Test, #expect, #require, or @Suite, (2) "use Swift Testing" or "modern testing patterns", (3) test doubles, mocks, stubs, spies, or fixtures, (4) unit tests, integration te
Ready to connect★ 81
- View details
test-firstSkillAI & models
Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.
Ready to connect★ 81
- View details
test-runnerSkillAI & models
Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
Ready to connect★ 81
- View details
vitaecontextSkillAI & models
Route broad or ambiguous VitaeContext work to the right module while keeping context scoped. Use when a request spans multiple surfaces, asks for overall digital-presence strategy, involves provider or install architecture, needs agent-context planning, or the correct platform skill is unclear.
Ready to connect★ 81
- View details
vitaecontext-vitaegraphSkillAI & models
Build, deepen, validate, index, and maintain a private hierarchical career knowledge graph from supplied career materials. Use when the user asks to create or update a VitaeGraph, model education with nested courses or thesis work, enrich projects from Git repositories, or supply deep selected caree
Ready to connect★ 81
- View details
agent-ciSkillAI & models
Run GitHub Actions CI locally with Agent CI only when explicitly requested.
Ready to connect★ 80
- View details
amoxide-project-aliasesSkillAI & models
Use amoxide for project-local .aliases and optional profiles when commands are simple, trusted, and useful to agents without shadowing zsh aliases.
Ready to connect★ 80
- View details
atlasSkillAI & models
Analyzing dependencies, circular references, and God Classes; authoring ADRs/RFCs. Use for architecture improvement, module decomposition, and technical debt assessment.
Ready to connect★ 80
- View details
attestSkillAI & models
Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.
Ready to connect★ 80
- View details
autonomous-agent-loopSkillAI & models
Maintains durable goal and handoff state. Use for explicit goal-management requests, resuming a recorded goal, or diagnosing agents that stall and need repeated prompts.
Ready to connect★ 80
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
54,624 of the 55,055 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.