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: Dev tools
16,833 results · page 249 of 562
- View details
bug-reportSkillDev tools
Workflow for creating and submitting bug reports to GitHub
Ready to connect★ 190
- View details
consoleSkillDev tools
Console UI component development workflow focused on TypeScript, React hooks, and accessibility
Ready to connect★ 190
- View details
feature-requestSkillDev tools
Workflow for creating and submitting feature requests to GitHub
Ready to connect★ 190
- View details
lattice-initSkillDev tools
Guided setup and upgrade-check experience for Lattice projects -- scans the repository, detects existing configuration and outdated conventions, suggests refiners and available upgrades in priority order, and creates or reconciles the .lattice/ config. Bridges the gap between installing skills and g
Ready to connect★ 190
- View details
requirement-forgeSkillDev tools
Generate structured feature specifications through a collaborative product interview. Acts as a senior PM and business analyst pair — arrives with a point of view, challenges scope, proposes options at every decision. Composes the requirement-quality atom for spec quality enforcement and collaborati
Ready to connect★ 190
- View details
requirement-forge-refinerSkillDev tools
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config
Ready to connect★ 190
- View details
requirement-qualitySkillDev tools
Apply requirement quality principles when generating or validating feature specifications. Enforces feature completeness, scenario structure, AC verifiability, feature independence, and implementation slice quality. Use when writing feature specs, validating existing requirements, or when the user m
Ready to connect★ 190
- View details
skill-reviewSkillDev tools
Deep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (con
Ready to connect★ 190
- View details
ubiquitous-languageSkillDev tools
Lets your agent use a shared set of engineering skills pulled from a developer's personal agent collection.
Ready to connect★ 190
- View details
codex-cli-reviewSkillDev tools
Code review via Codex CLI with full disk access. Use when: deep review needing full codebase read, uncommitted change review. Not for: quick diff review (use codex-code-review), doc review (use doc-review). Output: severity-grouped findings + merge gate.
Ready to connect★ 188
- View details
codex-implementSkillDev tools
Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.
Ready to connect★ 188
- View details
codex-review-branchSkillDev tools
Fully automated review of an entire feature branch using Codex MCP
Ready to connect★ 188
- View details
codex-review-fastSkillDev tools
Quick second-opinion using Codex MCP (diff only, no tests). Supports review loop with context preservation.
Ready to connect★ 188
- View details
codex-test-genSkillDev tools
Generate unit tests for specified functions using Codex MCP
Ready to connect★ 188
- View details
codex-test-reviewSkillDev tools
Review test case sufficiency using Codex MCP, suggest additional edge cases. Supports review loop with context preservation.
Ready to connect★ 188
- View details
contract-decodeSkillDev tools
EVM contract error and calldata decoder. Use when: user pastes hex revert data, calldata, function selector, or mentions custom error, execution reverted, 4byte, decode. Input contains 0x + 8+ hex chars.
Ready to connect★ 188
- View details
deep-analyzeSkillDev tools
Deep-dive analysis of an initial proposal — research code implementation, produce an actionable roadmap and alternatives
Ready to connect★ 188
- View details
deep-exploreSkillDev tools
Multi-wave parallel code exploration orchestrator. Use when: large-scale codebase research, understanding complex cross-domain systems, deep investigation needing multiple perspectives simultaneously. Not for: quick lookup (use code-explore), dual confirmation (use code-investigate), code review (us
Ready to connect★ 188
- View details
feasibility-studySkillDev tools
Feasibility analysis from first principles. Use when: evaluating solutions before tech-spec, comparing approaches, risk assessment. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: quantitative comparison + recommendation.
Ready to connect★ 188
- View details
feed-datasource-expertSkillDev tools
Expert guidance on implementing paginated feeds and infinite scroll in Flutter using FeedDataSource and PagedFeedDataSource patterns. Covers base feed data source, cursor-based pagination, auto-pagination at length-3, proxy lifecycle with reference counting, feed widget implementation, filtered feed
Ready to connect★ 188
- View details
generate-runnerSkillDev tools
Generate a customized precommit runner for any ecosystem. Use when: non-Node projects need a runner, eject from generic runner, customize runner for project. Not for: running precommit (use /precommit), installing runner (handled by auto-install). Output: customized runner script with eject header.
Ready to connect★ 188
- View details
git-investigateSkillDev tools
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
Ready to connect★ 188
- View details
git-profileSkillDev tools
Git identity and GPG signing profile manager. Discovers profiles from GPG + git config, switches local identity, checks signing health. Use when: user says 'switch identity', 'git profile', 'check signing', 'gpg key status', 'which identity', or /git-profile
Ready to connect★ 188
- View details
issue-analyzeSkillDev tools
GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified ana
Ready to connect★ 188
- View details
load-pr-reviewSkillDev tools
Load GitHub PR review comments into AI session — analyze, triage, plan. Default: analysis-only (no auto-fix). Use when: reviewing PR feedback, planning fixes, addressing review comments, replying to reviewers. Not for: creating reviews (use codex-review-fast), creating PRs (use create-pr), viewing P
Ready to connect★ 188
- View details
necessity-auditSkillDev tools
Necessity audit for over-designed spec elements. Use when: auditing lifecycle spec (1-requirements / 2-tech-spec / 3-architecture) for YAGNI/KISS violations, challenging necessity of FRs/NFRs/abstractions/configs via Codex adversarial debate. Not for: FP reasoning validity (use /codex-review-spec),
Ready to connect★ 188
- View details
next-stepSkillDev tools
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with
Ready to connect★ 188
- View details
post-dev-recapSkillDev tools
Post-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (us
Ready to connect★ 188
- View details
pr-commentSkillDev tools
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summa
Ready to connect★ 188
- View details
pre-pr-auditSkillDev tools
Pre-PR confidence audit with 5-dimension scoring. Use when: final check before commit/push/PR, evaluating PR readiness, assessing test quality + risk + coverage holistically. Triggers: pre-pr, readiness check, confidence audit, final verification, ready to PR, how confident. Not for: code review (us
Ready to connect★ 188
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.
53,585 of the 54,017 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.