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 44 of 149
- View details
freeze-testsSkillFiles & storage
Use when refactoring production code and you want to ensure test files are not modified. Activate with /freeze-tests to block all edits to test files for safe refactoring.
Ready to connect★ 478
- View details
no-skipSkillFiles & storage
Use when you want to prevent .skip(), .only(), xit(), and xdescribe() from being committed to test files. Activate with /no-skip for session-scoped test skip prevention.
Ready to connect★ 478
- View details
qe-bug-reporting-excellenceSkillFiles & storage
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.
Ready to connect★ 478
- View details
xp-practicesSkillFiles & storage
Apply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.
Ready to connect★ 478
- View details
ci-fix-monitorSkillFiles & storage
Codex adapter for monitoring and fixing CI failures on opencode-swarm PRs. Use when diagnosing failed checks, fixing `package-check` (npm tarball) failures, resolving quality/lint/format errors, fixing macOS cross-platform file I/O failures, or watching a PR until all checks are green.
Ready to connect★ 467
- View details
durable-session-stateSkillFiles & storage
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after co
Ready to connect★ 467
- View details
graphifySkillFiles & storage
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god node
Ready to connect★ 467
- View details
grep-for-mock-module-across-the-entire-test-file-and-confirm-eveSkillFiles & storage
grep for 'mock.module' across the entire test file and confirm every occurrence uses spread-real-exports before marking the file as converted
Ready to connect★ 467
- View details
include-test-files-that-assert-on-behavior-being-changed-in-declSkillFiles & storage
include test files that assert on behavior being changed in declared scope
Ready to connect★ 467
- View details
run-affected-test-file-in-isolation-and-in-co-run-with-its-test-SkillFiles & storage
run affected test file in isolation AND in co-run with its test-suite peers after mock cleanup changes
Ready to connect★ 467
- View details
run-affected-test-suite-end-to-end-after-multi-file-signature-chSkillFiles & storage
run affected test suite end-to-end after multi-file signature changes
Ready to connect★ 467
- View details
running-testsSkillFiles & storage
Codex adapter for safely executing opencode-swarm tests. Use whenever Codex needs to run focused tests, per-file isolation loops, CI-equivalent validation, test-impact checks, or diagnose failing/truncated test output without stalling the session.
Ready to connect★ 467
- View details
safe-extractionSkillFiles & storage
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, _internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
Ready to connect★ 467
- View details
skill-edit-validationSkillFiles & storage
Content-assertion sweep after editing SKILL.md files. Triggered when a task changes skill or prompt content that tests assert against. Prevents stale-assertion CI failures.
Ready to connect★ 467
- View details
subprocess-safetySkillFiles & storage
Guidelines for safe subprocess calls in opencode-swarm. Load before adding, modifying, or reviewing any file that calls spawn, spawnSync, bunSpawn, or child_process. Covers the six required properties, Windows portability, _internals DI seam pattern, and verification grep.
Ready to connect★ 467
- View details
swarm-implementSkillFiles & storage
Codex adapter for complex implementation work using the canonical opencode-swarm implementation workflow. Use for multi-file features, bug fixes, refactors, risky code changes, or tasks that benefit from exploration, scoped planning, implementation, review, and validation.
Ready to connect★ 467
- View details
swarm-pr-reviewSkillFiles & storage
Thin adapter for the canonical swarm-pr-review skill. The authoritative workflow lives in .opencode and this file only preserves the mirror contract for Codex-side skill discovery.
Ready to connect★ 467
- View details
test-file-splitSkillFiles & storage
Protocol for splitting test files that approach or exceed the FR-006 500-line limit (enforced in CI by scripts/check-test-file-cap.ts as a diff-scoped ratchet). Covers describe-block extraction, shared helper management, pure-function extraction, mock isolation verification, and cascading-split dete
Ready to connect★ 467
- View details
detecting-languagesSkillFiles & storage
Use when the user wants to know which programming language a file or snippet is. Covers implicit detection in `ts-pack parse`/`process`, confirming support with `ts-pack list`/`info`, and the SDK detection functions for path, extension, and raw content.
Ready to connect★ 465
- View details
extracting-code-structureSkillFiles & storage
Use when the user wants structured code metadata from a source file — functions, classes, imports, exports, symbols, docstrings, comments, or syntax diagnostics. Covers `ts-pack process` feature flags, the JSON result shape, and the default feature set.
Ready to connect★ 465
- View details
parsing-sourceSkillFiles & storage
Use when the user wants a tree-sitter syntax tree for a source file — an s-expression dump or JSON tree. Covers `ts-pack parse`, language auto-detection vs `--language`, stdin input, and reading `has_errors`.
Ready to connect★ 465
- View details
reviewing-changesSkillFiles & storage
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with add_review_comment, and settle with exactly one review_verdict.
Ready to connect★ 459
- View details
mastra-file-agentsSkillFiles & storage
Migrate Mastra code-based agents (agents built with new Agent(...) and registered in a Mastra({ agents }) map) to the file-based convention: one directory per agent under src/mastra/agents. Use when the user wants to convert or refactor Mastra agents to the per-directory convention, mentions Mastra
Ready to connect★ 462
- View details
toxySkillFiles & storage
Use this skill whenever the user wants to extract text or data from documents using Toxy (the .NET text extraction library). Trigger when the user mentions reading, parsing, or extracting content from files like docx, xlsx, xls, pdf, csv, txt, epub, html, eml, vcf using C# or .NET. Also trigger when
Ready to connect★ 462
- View details
commitsSkillFiles & storage
Use when picking a branch name, staging files, or writing a commit message — covers branch conventions, the project's Conventional Commits format with the scope vocabulary observed in history, and the documentation-update gate that fires before every commit (`docs/*`, `README.md`, godoc, Helm values
Ready to connect★ 458
- View details
coding-agentSkillFiles & storage
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit
Ready to connect★ 456
- View details
ngx-page-object-modelSkillFiles & storage
MUST invoke before creating or editing any Angular component's tests (spec file). Enforces the Page Object Model pattern – tests drive components through the rendered DOM (their public contract) rather than reaching into component internals.
Ready to connect★ 450
- View details
architecture-cleanupSkillFiles & storage
Find and execute bounded architecture cleanup across public exports, package ownership, Convex bundle graphs, plugins, CLI/scaffolds, generated files, docs, and agent navigation.
Ready to connect★ 447
- View details
changeset-resolveSkillFiles & storage
Repair an unreleased `.changeset/*.md` file so it matches the real branch delta against `main`. Use when a changeset was edited iteratively during debugging, when bullets may reflect turn-by-turn history instead of `main...HEAD`, when "removed/gone/renamed" claims need proof, or when you need to aud
Ready to connect★ 447
- View details
component-colocationSkillFiles & storage
Use after migrating/refactoring features (especially tables/data grids) when reviewing component structure - enforces merging over-split components, colocating files where used, removing unused code, following vertical slice architecture. Prevents premature abstraction and over-engineering.
Ready to connect★ 447
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.