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: Files & storage
4,446 results · page 41 of 149
- View details
common-architecture-diagrammingSkillFiles & storage
Standards for creating clear, audience-appropriate C4 and UML architecture diagrams with Mermaid. Use when producing system context diagrams, container views, sequence diagrams, ERDs, or updating ARCHITECTURE.md files; defer design-session deliverables to system-design-diagramming.
Ready to connect★ 565
- View details
common-feedback-reporterSkillFiles & storage
Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.
Ready to connect★ 565
- View details
common-workflow-writingSkillFiles & storage
Rules for writing concise, token-efficient workflow and skill files. Prevents over-building that requires costly optimization passes. Use when creating or editing workflow files, SKILL.md files, or new skill definitions.
Ready to connect★ 565
- View details
flutter-localizationSkillFiles & storage
Add Flutter translation assets, locale initialization, localized strings, locale switching, and plurals with easy_localization and CSV or JSON files. Use for Flutter i18n work; not RTL-only layout or locale-specific date formatting.
Ready to connect★ 565
- View details
flutter-securitySkillFiles & storage
Secure Flutter token/PII storage, build-time secrets, network trust, and release hardening using OWASP Mobile practices. Use for secure storage, secret injection, certificate pinning, jailbreak/root risk, or release builds—not generic form validation, API error handling, auth-provider setup, or test
Ready to connect★ 565
- View details
golang-configurationSkillFiles & storage
Load and validate application configuration from environment variables and config files. Use when managing Go application config with environment variables or viper.
Ready to connect★ 565
- View details
session-reportSkillFiles & storage
Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.
Ready to connect★ 565
- View details
pm-brainstormSkillFiles & storage
Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.
Ready to connect★ 561
- View details
qa-find-bugsSkillFiles & storage
Drive the live product at https://dashboard.bex.co as a signed-in QA user (QA_EMAIL / QA_PASSWORD from .env), hunt real bugs across the hosting features, research each fix down to file:line, file the non-duplicate findings to the w6 board through /pm, and /ship the scheduled milestone. Use when the
Ready to connect★ 561
- View details
qa-find-bugs-cliSkillFiles & storage
Hunt live hosting bugs through the bex CLI against the pinned Render CLI contract, trace failures into server compatibility or the Bex launcher, and file researched, non-duplicate fixes through /pm. Use when asked to QA the CLI or find hosting bugs from terminal journeys. Ships the filing only when
Ready to connect★ 561
- View details
shared/tech-stack-detectionSkillFiles & storage
A general method for detecting a project's tech stack by analyzing config files to identify languages, frameworks, and toolchains.
Ready to connect★ 556
- View details
briefSkillFiles & storage
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
Ready to connect★ 551
- View details
freezeSkillFiles & storage
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.
Ready to connect★ 551
- View details
phx-briefSkillFiles & storage
Interactive briefing of a plan file — explains reasoning, schema decisions,
Ready to connect★ 551
- View details
plugin-dev-workflowSkillFiles & storage
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
Ready to connect★ 551
- View details
quickSkillFiles & storage
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
Ready to connect★ 551
- View details
tasksSkillFiles & storage
Convert a PRD markdown file to prd.json for execution. Triggers on: convert prd, create tasks, prd to json, generate tasks from prd.
Ready to connect★ 542
- View details
Plugin SettingsSkillFiles & storage
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin
Ready to connect★ 538
- View details
create-commandSkillFiles & storage
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants to create a reusable s
Ready to connect★ 535
- View details
dev-deepinitSkillFiles & storage
Deep codebase initialization — generate hierarchical AGENTS.md / CLAUDE.md context files for a new project so engineering agents have full context from session start.
Ready to connect★ 535
- View details
knowledge-ingestSkillFiles & storage
Upload a file (PDF, DOCX, PPTX, XLSX, HTML, EPUB, image) or URL to the Knowledge base. Triggers Marker parsing, chunking, embedding, and async classification. Use when the user says 'index this PDF', 'add this URL to the knowledge base', 'upload these files to Academy', or pastes a file path/URL wit
Ready to connect★ 535
- View details
legal-vendor-checkSkillFiles & storage
Verify the status of existing agreements with a vendor across all connected systems — int-evo-crm, Gmail, Notion, and local files — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, or when you need a consolidated view of what's signed and what's missing.
Ready to connect★ 535
- View details
plugin-healthSkillFiles & storage
Check an installed plugin's health — verify manifest SHA256 matches files on disk, detect tampering or corruption. Use when the user asks if a plugin is working, reports a bug, or wants to validate integrity. Triggers on "plugin X está funcionando?", "health plugin X", "status plugin X", "está ok o
Ready to connect★ 535
- View details
plugin-security-scanSkillFiles & storage
Semantic security scan of plugin agents, skills, rules, and commands markdown files. Detects prompt injection, credential exfiltration patterns, and privilege escalation instructions. Invoked automatically by the plugin install gate (Wave 2.5) — not for direct user invocation. Returns strict JSON.
Ready to connect★ 535
- View details
durable-objectsSkillFiles & storage
Teaches your agent how to build applications on Cloudflare's durable storage and compute services.
Ready to connect★ 533
- View details
journey-planSkillFiles & storage
Use as stage 2 of the Butterbase journey, after journey-idea has written 01-idea.md. Translates the idea + capability map into a concrete Butterbase plan — tables (with columns/types/RLS shape), auth providers, function list (name + trigger), storage buckets, AI/RAG/realtime/durable usage, and the c
Ready to connect★ 533
- View details
journey-storageSkillFiles & storage
Use as the storage build stage of the Butterbase journey. Implements the Storage section of 02-plan.md by delegating to the storage skill. Calls manage_storage (update_config) for bucket setup; uploads are exercised at frontend integration time, not here. Skipped if the plan has no file uploads.
Ready to connect★ 533
- View details
journey-templatesSkillFiles & storage
Use as the optional template-publishing stage of the Butterbase journey, after deploy (and substrate, if used). Walks the user through authoring a clone-ready README, bundling agent spec files, dry-running and pushing the repo snapshot, flipping visibility to public + listed, and self-clone-testing.
Ready to connect★ 533
- View details
storageSkillFiles & storage
Use when uploading or downloading files, generating presigned URLs, configuring storage ACLs, or persisting file references (avatars, attachments, images) in a Butterbase app
Ready to connect★ 533
- View details
agent-linterSkillFiles & storage
Structural validation of agent and skill files. Frontmatter checks, naming conventions, required section checks, and consistency audits. Runs automatically when a new agent/skill is added or existing files are edited.
Ready to connect★ 531
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.