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,535 results · page 43 of 152
- View details
superdesignSkillDocs & knowledge
Design or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models. Use whenever the user wants to design a page, feature, flow, slide deck, or brand-new product; improve or reproduce existing UI; compare design results across top models; explore
Ready to connect★ 547
- View details
code-docSkillDocs & knowledge
Use when the user prompts "code doc" to create or update internal Orchid ORM code documentation from changes/ specs, short-code feature folders, or existing implementation code.
Ready to connect★ 543
- View details
implemenation-noteSkillDocs & knowledge
Use when the user prompts "implementation note" for an existing change idea.
Ready to connect★ 543
- View details
create-agentSkillDocs & knowledge
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent for a specific domai
Ready to connect★ 535
- View details
dev-external-contextSkillDocs & knowledge
Parallel external documentation lookup. Spawn multiple @scroll-docs agents simultaneously to fetch SDK refs, API docs, and framework guides for different topics in one pass.
Ready to connect★ 535
- View details
dev-rememberSkillDocs & knowledge
Persist context across engineering sessions — save important decisions, gotchas, or patterns that should survive beyond the current conversation. For long-term workspace memory, prefer mempalace.
Ready to connect★ 535
- View details
fin-journal-entry-prepSkillDocs & knowledge
Prepare journal entries with proper debits, credits, and supporting documentation for month-end close. Use when booking accruals, prepaid amortization, fixed asset depreciation, payroll entries, revenue recognition, or any manual journal entry.
Ready to connect★ 535
- View details
knowledge-adminSkillDocs & knowledge
Administrative operations on the Knowledge base: connect new pgvector servers, check health, view stats, export data, install parser models. Use when the user wants to configure/monitor the system ('connect a new pgvector', 'status of connections', 'how many docs do we have', 'export backup of space
Ready to connect★ 535
- View details
knowledge-browseSkillDocs & knowledge
List and filter documents and units in the Knowledge base. Use when the user wants to see what is indexed ('what's in space X', 'list the last 10 indexed docs', 'which documents have error status', 'show Academy units').
Ready to connect★ 535
- View details
knowledge-organizeSkillDocs & knowledge
Create, move, reorder, or link learning units and documents in the Knowledge base. Use when the user wants to structure content ('create unit Module 3', 'move these docs to lesson 2', 'reorder lessons by logical sequence', 'link doc X to unit Y').
Ready to connect★ 535
- View details
knowledge-summarizeSkillDocs & knowledge
Generate a TL;DR summary of a specific document or learning unit in the Knowledge base. Pulls chunks from pgvector and synthesizes via Claude Haiku. Use when the user wants a quick overview ('summary of lesson 5', 'TL;DR of this PDF', 'explain document X in one paragraph').
Ready to connect★ 535
- View details
legal-signature-requestSkillDocs & knowledge
Prepare and route a document for electronic signature — run the pre-signing checklist, configure the signing order, and send it for execution. Use when a contract is finalized and ready to sign, when verifying entity names, attachments, and signature blocks before sending, or a
Ready to connect★ 535
- View details
ops-compliance-trackingSkillDocs & knowledge
Track compliance requirements and audit readiness. Use when you need compliance, audit preparation, LGPD, regulatory requirements, or when you need to track, prepare, or document compliance activities. Primary framework: LGPD (Brazilian operation). Lex agent.
Ready to connect★ 535
- View details
ops-process-docSkillDocs & knowledge
Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to make clear who owns what, writing an SOP for handoff or audit, or capturing exceptions and edge cases of how the work actually happens. Agent C
Ready to connect★ 535
- View details
integrationsSkillDocs & knowledge
Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot, Salesforce), docs (Notion), or project management (Linear, GitHub). Butterbase covers most of these via manage_in
Ready to connect★ 533
- View details
journey-ragSkillDocs & knowledge
Use as the RAG build stage of the Butterbase journey. Implements the RAG section of 02-plan.md by delegating to rag-dev. Calls manage_rag_content (create_collection, ingest_document). Skipped if the plan has no knowledge-base feature.
Ready to connect★ 533
- View details
substrateSkillDocs & knowledge
Use when the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities, business state, institutional memory, and an append-only action ledger. Use for: founder copilots, AI agents that need memory across sessions, anything that proposes actions on t
Ready to connect★ 533
- View details
changelog-automationSkillDocs & knowledge
Git history'den otomatik changelog, semantic versioning, release notes, conventional commits
Ready to connect★ 531
- View details
developer-relationsSkillDocs & knowledge
Developer relations - community building, documentation, DevRel metrics.
Ready to connect★ 531
- View details
fdeSkillDocs & knowledge
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Us
Ready to connect★ 531
- View details
harvest-singleSkillDocs & knowledge
Single page smart extraction - articles, docs, blog posts to clean markdown
Ready to connect★ 531
- View details
layered-recallSkillDocs & knowledge
Progressive memory recall with 4 scope layers AND 3 depth layers. Scope: identity > project > room > deep. Depth: IDs only > summary > full. 10-50x token savings through fetch-on-confirmation pattern.
Ready to connect★ 531
- View details
audit-docsSkillDocs & knowledge
Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documenta
Ready to connect★ 518
- View details
capture-knowledgeSkillDocs & knowledge
Capture non-obvious facts learned while working into dev/knowledge/, dev/guidelines/, or dev/guides/ so future agents understand the code faster. Trigger when the user says 'capture this', 'document this', 'we should write that down', or autonomously at the end of a feature when something non-obviou
Ready to connect★ 518
- View details
creating-prdSkillDocs & knowledge
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user
Ready to connect★ 518
- View details
generating-documentationSkillDocs & knowledge
Generate comprehensive technical documentation including API docs (OpenAPI/Swagger), code documentation (TypeDoc/Sphinx), documentation sites (Docusaurus/MkDocs), Architecture Decision Records (ADRs), and diagrams (Mermaid/PlantUML). Use when documenting APIs, libraries, systems architecture, or bui
Ready to connect★ 518
- View details
harvesting-reviewSkillDocs & knowledge
Mines a pull request's review threads for lessons that generalize beyond that PR, reconstructs each against the actual code before deciding, checks whether it is already codified, and routes the genuinely-new, durable ones into Infrahub's internal documentation — `dev/knowledge/`, `dev/guides/`, `de
Ready to connect★ 518
- View details
performance-engineeringSkillDocs & knowledge
When validating system performance under load, identifying bottlenecks through profiling, or optimizing application responsiveness. Covers load testing (k6, Locust), profiling (CPU, memory, I/O), and optimization strategies (caching, query optimization, Core Web Vitals). Use for capacity planning, r
Ready to connect★ 518
- View details
speckit-review-commentsSkillDocs & knowledge
Code comment accuracy verification, documentation completeness assessment,
Ready to connect★ 518
- View details
bun-runtimeSkillDocs & knowledge
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
Ready to connect★ 507
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.