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
9,019 results · page 60 of 301
- View details
ask-questions-if-underspecifiedSkillAI & models
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Ready to connect★ 1k
- View details
audit-library-healthSkillAI & models
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
Ready to connect★ 1k
- View details
best-practicesSkillAI & models
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
Ready to connect★ 1k
- View details
browse-and-evaluateSkillAI & models
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
Ready to connect★ 1k
- View details
build-workspace-docsSkillAI & models
Use when regenerating README.md and WORK_AREAS.md in a managed library workspace. Always dry-run first to preview changes.
Ready to connect★ 1k
- View details
install-from-remote-librarySkillAI & models
Use when installing skills from a shared ai-agent-skills library repo. Inspect with `--list` first, prefer `--collection`, and preview with `--dry-run` before installing.
Ready to connect★ 1k
- View details
migrate-skills-between-librariesSkillAI & models
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
Ready to connect★ 1k
- View details
review-a-skillSkillAI & models
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
Ready to connect★ 1k
- View details
share-a-librarySkillAI & models
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
Ready to connect★ 1k
- View details
update-installed-skillsSkillAI & models
Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.
Ready to connect★ 1k
- View details
cpu-z80nSkillAI & models
Z80N (ZX Spectrum Next) for z88dk: Next-only opcodes (mul, nextreg, LDIX…), nextreg I/O model, copper co-processor programs, +zxn / -mz80n / math32_z80n. Use when writing or reviewing Next asm, nextreg/copper code, or measuring HW mul.
Ready to connect★ 1k
- View details
rest-openapiSkillAI & models
Reference for OrangeHRM's OpenAPI v3 annotations via zircote/swagger-php — what to add to Endpoint methods and Model classes, the project's shared component refs (RecordNotFound, ForbiddenResponse, sortOrder, limit, offset), how class constants are used inside annotations, and the `generate-open-api
Ready to connect★ 1k
- View details
rest-serializationSkillAI & models
Reference for shaping OrangeHRM REST API v2 responses — the `Normalizable` + `ModelTrait` contract, writing a Model class that maps a Doctrine entity to a JSON object, the `filter` array (getter chain — supports nested-getter sequences for related entities), the `attributeNames` array (output JSON k
Ready to connect★ 1k
- View details
workflowSkillAI & models
Reference for OrangeHRM's workflow state machine — the `WorkflowStateMachine` entity that models `(workflow, state, role, action) → resultingState` transitions in `ohrm_workflow_state_machine`, the eight `FLOW_*` constants for the workflow types (Leave, Recruitment, Timesheet, Attendance, Employee,
Ready to connect★ 1k
- View details
customizeSkillAI & models
Create a Wisp specialist or author a project-local skill using the tools Wisp actually exposes. Use when the user wants a custom Agent persona, a restricted specialist loadout, a new skill, or changes to an existing project-local skill.
Ready to connect★ 1k
- View details
guidelinesSkillAI & models
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Ready to connect★ 1k
- View details
agentlas-callSkillAI & models
Use when the user types /agentlas-call <agents> <context>, /agentlas call, or /hep-call to borrow and execute named Agentlas Hub/Cloud agents attached to the current project.
Ready to connect★ 1k
- View details
agentlas-core-engine-meta-agentSkillAI & models
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
Ready to connect★ 1k
- View details
agentlas-networkSkillAI & models
Use when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams.
Ready to connect★ 1k
- View details
agentlas-oneSkillAI & models
Use when the user types /agentlas-one on|off, /agentlas one on|off, or asks to enable/disable the persistent personal agent mode.
Ready to connect★ 1k
- View details
agentlas-packagingSkillAI & models
Use when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release.
Ready to connect★ 1k
- View details
agentlas-uploadSkillAI & models
Use when the user types /agentlas-upload, /agentlas upload, $hephaestus-upload, or /hep-upload to scan, gate, and publish an agent/team package to Agentlas Cloud (private) or Agentlas Hub (public).
Ready to connect★ 1k
- View details
clarify-question-loopSkillAI & models
Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
Ready to connect★ 1k
- View details
code-health-checkSkillAI & models
Perform a comprehensive code health check on a directory. Use when the user asks to analyze code quality, find issues, or get a health report.
Ready to connect★ 1k
- View details
codebase-visualizerSkillAI & models
Generate an interactive tree visualization of your codebase. Use when exploring a new repo or understanding project structure.
Ready to connect★ 1k
- View details
hep-buildSkillAI & models
Build, repair, or package Agentlas agents and teams with Hephaestus.
Ready to connect★ 1k
- View details
- View details
hep-stormSkillAI & models
Run a force-robust Stormbreaker loop — route to real agents, execute a verified pipeline to completion.
Ready to connect★ 1k
- View details
hep-uploadSkillAI & models
Upload an Agentlas agent after asking Cloud vs Hub first.
Ready to connect★ 1k
- View details
hephaestus-buildSkillAI & models
Use when the user types /prompts:hep-build or /agentlas-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package an existing local/external agent into Agentlas architecture.
Ready to connect★ 1k
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,764 of the 55,196 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.