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: Docs & knowledge
4,436 results · page 69 of 148
- View details
texture-workflowSkillDocs & knowledge
Production texture workflow for atlases, baking AO/curvature/normal/roughness maps, decals, and texture memory optimization. Use for game-ready texture pipelines in Blender via MCP.
Ready to connect★ 187
- View details
ab-analyze-backendSkillDocs & knowledge
Analyze and document a project's backend patterns — API design, data access, service structure. Use when the user wants a backend-only architecture analysis.
Ready to connect★ 190
- View details
ab-analyze-frontendSkillDocs & knowledge
Analyze and document a project's frontend patterns — component structure, state management, conventions. Use when the user wants a frontend-only architecture analysis.
Ready to connect★ 190
- View details
ab-analyze-projectSkillDocs & knowledge
Analyze a project's architecture end to end — extract domain language, map the tech stack, document frontend and backend patterns. Use when onboarding a new codebase or refreshing the architecture baseline.
Ready to connect★ 190
- View details
ab-update-architectureSkillDocs & knowledge
Refresh architecture and domain documentation after impactful changes. Use when code has drifted from the documented architecture.
Ready to connect★ 190
- View details
architecture-compassSkillDocs & knowledge
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation —
Ready to connect★ 190
- View details
architecture-refinerSkillDocs & knowledge
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use w
Ready to connect★ 190
- View details
clean-code-refinerSkillDocs & knowledge
Facilitate a structured conversation to define clean code principles for a repository. Produces a formal clean-code.md document that the clean-code atom will use as its override. Use when setting up coding standards, defining code quality rules, or when the user says 'setup clean code', 'define codi
Ready to connect★ 190
- View details
context-anchoringSkillDocs & knowledge
Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own docu
Ready to connect★ 190
- View details
ddd-refinerSkillDocs & knowledge
Facilitate a structured conversation to define DDD guardrails for domain design within a repository. Produces a formal ddd-principles.md document that the domain-driven-design atom will use as its override. Use when setting up domain design principles, defining aggregate rules, or when the user says
Ready to connect★ 190
- View details
domain-modelSkillDocs & knowledge
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Ready to connect★ 190
- View details
knowledge-primingSkillDocs & knowledge
Load project-specific context -- tech stack, architecture overview, directory layout, trusted sources, and conventions -- so that all skills operate with awareness of what this project actually is. Use when a knowledge base document exists, or when the user asks about the project's tech stack, archi
Ready to connect★ 190
- View details
knowledge-priming-refinerSkillDocs & knowledge
Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI
Ready to connect★ 190
- View details
language-idioms-refinerSkillDocs & knowledge
Facilitate a structured conversation to define language-specific idioms and patterns for a repository. Produces a language-idioms.md document consumed by multiple atoms to adapt pseudocode defaults to the project's language. Use when setting up a new project, switching languages, or when the user sa
Ready to connect★ 190
- View details
learning-harvestSkillDocs & knowledge
Manage the operational learnings lifecycle — load prior learnings to inform current work, harvest new patterns worth preserving, and keep the document tight over time. Provides a protocol for accumulating actionable patterns from practice that complement standards and defaults. Use when a workflow s
Ready to connect★ 190
- View details
refiners-updateSkillDocs & knowledge
Update existing Lattice standards after a significant change — the update-mode counterpart to lattice-init. Scans .lattice/standards/, asks what changed, and routes each affected standard to its refiner's revise mode, recording a git-native change note. Use when the user says 'update refiners', 'ref
Ready to connect★ 190
- View details
review-refinerSkillDocs & knowledge
Facilitate a structured conversation to customize how the review molecule works -- atom loading rules, severity classification, report format, scope rules, insight capture, and health logging. Produces a formal review-standards.md document that the review molecule will use as its process configurati
Ready to connect★ 190
- View details
skill-alignSkillDocs & knowledge
Audit and fix all Lattice documentation, README, docs/, PROJECT.md, GitHub issue templates, and CLAUDE.md to ensure they are fully aligned with the current skill inventory. Documentation drift is the most common source of user confusion in Lattice — a skill exists in the codebase but not in the docs
Ready to connect★ 190
- View details
sync-architectureSkillDocs & knowledge
Post-implementation documentation-sync detector. Spins up ONE read-only subagent on a completed task's diff to find everything the change introduced that the architecture docs don't yet know about — new endpoints, patterns, dependencies, domain terms, ADR-worthy decisions — routed to the exact doc e
Ready to connect★ 190
- View details
publish-reportSkillDocs & knowledge
Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs. Use whenever Codex creates or finishes an .html, .htm, .md, .markdown, or static build output that a person could share (a report, plan, doc, dashboard, or analysis) — proactively offer to publish it w
Ready to connect★ 189
- View details
- View details
codex-review-docSkillDocs & knowledge
Review documents using Codex MCP. Supports review loop with context preservation.
Ready to connect★ 188
- View details
context-managementSkillDocs & knowledge
Invoke this Skill when a system prompt requires token budget allocation design, context compression strategies, lazy-loading mechanisms, or memory persistence solutions. Suitable for scenarios that require fine-grained context window management, such as long-conversation AI assistants, code editor i
Ready to connect★ 186
- View details
de-ai-flavorSkillDocs & knowledge
Remove AI artifacts from documents. Use when: cleaning AI-generated text, removing tool names, fixing boilerplate patterns. Not for: doc review (use doc-review), doc refactoring (use doc-refactor). Output: cleaned document preserving original intent.
Ready to connect★ 188
- View details
doc-refactorSkillDocs & knowledge
Refactor documents — simplify without losing information, visualize flows with sequenceDiagram.
Ready to connect★ 188
- View details
fp-briefSkillDocs & knowledge
First-principles briefing from technical documents. Use when: understanding why decisions were made, onboarding to feature reasoning, reviewing decision chains, explaining doc from first principles. Not for: PM/CTO summary (use project-brief), pre-doc analysis (use feasibility-study), code explanati
Ready to connect★ 188
- View details
injection-defenseSkillDocs & knowledge
Use this skill when a system prompt needs to defend against security threats such as prompt injection, jailbreak attacks, social engineering, and content trust boundary breaches. Suitable for system prompts of any system that accepts external input, such as AI agents, chatbots, and document processi
Ready to connect★ 186
- View details
portfolioSkillDocs & knowledge
Portfolio system knowledge base. Use when: position queries, routing strategy questions, provider integration. Not for: general code exploration (use code-explore), code review (use codex-code-review). Output: domain-specific analysis + recommendations.
Ready to connect★ 188
- View details
pr-summarySkillDocs & knowledge
List open PRs, filter automation PRs, group by ticket ID, format as Markdown. Use when: user asks for PR summary, PR status, or /pr-summary
Ready to connect★ 188
- View details
recap-askSkillDocs & knowledge
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap-<date>.md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general projec
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,462 of the 53,895 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.