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 90 of 149
- View details
asset-creatorSkillFiles & storage
Creates code-based visual assets — SVG icons, OG image HTML templates, social banners, and icon sets. Use when generating visuals as code (vector/HTML), NOT raster images — for raster generation see @rune-pro/media. Outputs files with usage instructions.
Ready to connect★ 86
- View details
asset-specSkillFiles & storage
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Ready to connect★ 86
- View details
balance-checkSkillFiles & storage
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
Ready to connect★ 86
- View details
build-scaffoldSkillFiles & storage
Create project skeleton. Pick stack, create files, install dependencies. AI decides everything.
Ready to connect★ 86
- View details
create-storiesSkillFiles & storage
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Ready to connect★ 86
- View details
design-systemSkillFiles & storage
Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
Ready to connect★ 86
- View details
dev-storySkillFiles & storage
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /stor
Ready to connect★ 86
- View details
doc-processorSkillFiles & storage
Generate and parse office documents — PDF, DOCX, XLSX, PPTX, CSV. Use when creating reports, exporting tabular data, or processing uploaded office files. NOT for project documentation (use docs).
Ready to connect★ 86
- View details
file-transferSkillFiles & storage
Transfer files between local and server. Guide user through SCP or upload methods.
Ready to connect★ 86
- View details
full-reviewSkillFiles & storage
Full project review from beginning. Check every file. Plain language report.
Ready to connect★ 86
- View details
integrity-checkSkillFiles & storage
Verify integrity of persisted state, skill outputs, and context bus data. Use when validating .rune/ files or sub-agent outputs against prompt injection, memory poisoning, identity spoofing, or adversarial payloads. Called by sentinel, team, session-bridge.
Ready to connect★ 86
- View details
judge-when-to-askSkillFiles & storage
Decide when AutoCode acts on its own and when it must stop and ask the user. Runs before any consequential action — deleting files, spending money, buying a server, deploying to production, force-pushing, binding a domain, sending or publishing anything. Ordinary reversible work proceeds silently; o
Ready to connect★ 86
- View details
memory-curateSkillFiles & storage
Use this skill on a weekly cadence and at every change archive to keep the project's tiered memory (MEMORY.md index + per-topic memory files + workspace artifacts under .memory/) coherent and fresh. Detects stale entries, merges duplicates, prunes superseded facts, refreshes the inference layer from
Ready to connect★ 86
- View details
neural-memorySkillFiles & storage
Cross-session cognitive persistence via Neural Memory MCP. Use when needing semantic recall of past decisions / errors / insights across projects — distinct from session-bridge (file-based, project-scoped). Provides hypothesis tracking, evidence chains, and graph-based associative memory.
Ready to connect★ 86
- View details
openspec-apply-changeSkillFiles & storage
Use this skill at Step 6 of the v2 SOP to implement one task from the change's tasks/ directory at a time. Each invocation should produce a code diff for exactly one task document, touching ≤ 2 files, with prompts pre-routed through mcp-model-router and any L3/L4 text pre-desensitized via phi-desens
Ready to connect★ 86
- View details
prd-authorSkillFiles & storage
ALIAS · Alias skill. Merged into `prd` as of v2.1. This file is kept only for compatibility with older SOP references.
Ready to connect★ 86
- View details
qa-planSkillFiles & storage
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprin
Ready to connect★ 86
- View details
quick-designSkillFiles & storage
Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.
Ready to connect★ 86
- View details
quick-fixSkillFiles & storage
Use this skill for micro-changes (bugfix / docs / 小配置) that satisfy: ≤2 files changed, no L3/L4 PHI field touched, no new LLM call, no spec/design modification. This skill routes to the 5-step micro SOP instead of the full 12-step SOP. Auto-checks via scripts/sop_router.py; if any check fails, redir
Ready to connect★ 86
- View details
scope-guardSkillFiles & storage
Detects scope creep by quantifying drift percentage. Auto-triggered by L1 orchestrators when files exceed the original plan. Compares git changes against plan, classifies drift into 4 tiers: ON_TRACK, MINOR_DRIFT, SIGNIFICANT_DRIFT, OUT_OF_CONTROL.
Ready to connect★ 86
- View details
session-bridgeSkillFiles & storage
Universal context persistence across sessions. Auto-saves decisions, conventions, and progress to .rune/ files. Loads state at session start. Use when any skill makes architectural decisions or establishes patterns that must survive session boundaries.
Ready to connect★ 86
- View details
skill-routerSkillFiles & storage
Meta-enforcement layer that routes EVERY agent action through the correct skill. MUST check this routing table before ANY response involving code, files, or technical decisions. Default: route to rune:cook for code tasks. Prevents rationalization, enforces check-before-act discipline.
Ready to connect★ 86
- View details
skill-testSkillFiles & storage
Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).
Ready to connect★ 86
- View details
sprint-statusSkillFiles & storage
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update',
Ready to connect★ 86
- View details
story-doneSkillFiles & storage
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Ready to connect★ 86
- View details
story-readinessSkillFiles & storage
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on
Ready to connect★ 86
- View details
task-decompositionSkillFiles & storage
Use this skill at Step 4 of the v2 SOP to decompose an OpenSpec change's tasks.md into atomic, prioritized, single-document, ≤2-file-change tasks. Enforces strict separation of frontend vs backend tracks, Chinese naming for task documents, and explicit dependency order. Each task gets its own task d
Ready to connect★ 86
- View details
test-evidence-reviewSkillFiles & storage
Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.
Ready to connect★ 86
- View details
test-helpersSkillFiles & storage
Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
Ready to connect★ 86
- View details
aai-bitbucketSkillFiles & storage
Use aai-cli to inspect and manage Bitbucket repositories, pull requests, branches, commits, source files, comments, and pipelines.
Ready to connect★ 85
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.