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: Dev tools
16,976 results · page 492 of 566
- View details
hygieneSkillDev tools
Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.
Ready to connect
- View details
install-vscode-extensionSkillDev tools
How to install a VS Code extension from an extension ID. Useful when the user wants to add new capabilities to their VS Code environment by installing extensions.
Ready to connect
- View details
looking-up-docsSkillDev tools
Find exact, version-correct library/API/framework docs through one lookup
Ready to connect
- View details
minimizeSkillDev tools
This skill should be used when the user asks to "minimize the repro path", "/minimize", "shrink the crash steps", "精简复现路径", "找最小复现", "把 12 步压成 3 步", or wants to compress a recorded crash repro_path into the shortest sequence that still reproduces the same crash signature. Drives live Android replay
Ready to connect
- View details
operating-infraSkillDev tools
Author, inspect, troubleshoot, and review infrastructure across IaC,
Ready to connect
- View details
operational-auditSkillDev tools
Periodic audit of the operational properties of the LearnFlow AI system outside the iteration pipeline: what breaks on restart, a second worker, a dependency blip, or load growth; whether the assumptions of accepted ADRs still hold. Use when: operational audit, аудит системы, production readiness, p
Ready to connect
- View details
pr-polishSkillDev tools
Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to
Ready to connect
- View details
- View details
regression-baselineSkillDev tools
How to tell a real test regression from this repo's pre-existing failure debt — the set-diff against a baseline worktree, the three import roots and the session-end leak assertion that make the baseline an actual baseline, and why a stash inside a killable command must never be used. Use before clai
Ready to connect
- View details
researching-webSkillDev tools
Web research via platform web tools. Use for technical comparisons, current-state
Ready to connect
- View details
setup-repoSkillDev tools
Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktre
Ready to connect
- View details
smart-qaSkillDev tools
This skill should be used when the user says "找 bug" / "看一下有没有 bug" / "smart-qa" / "/smart-qa" / "帮我测一下这个项目" / "智能 QA" / "推断业务流程测一下"，or asks for an autonomous bug-hunt where they DON'T already know what to test. Distinct from `qa` (blind exploration) and `devtest` (verifies a specific change). smart
Ready to connect
- View details
smoke-testsSkillDev tools
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.
Ready to connect
- View details
snapshot-testingSkillDev tools
Use when: (1) enabling golden snapshot testing in a project that uses Arkive, (2) a verifyShowcase build failed and needs diagnosing, (3) the UI changed intentionally and goldens need re-recording, (4) wiring snapshot verification into CI. There is no test to write — Arkive generates it; this skill
Ready to connect
- View details
spec-authorSkillDev tools
Write an executable specification under docs/graph/specs/ that turns a clear goal into testable contracts. Use whenever a feature, endpoint, job, significant function, or AI interaction needs a contract that the tester can encode and the implementer can satisfy. Coordinates product (§3, §9), archite
Ready to connect
- View details
spec-flowSkillDev tools
Use when planning, executing, checkpointing, finishing, or inspecting
Ready to connect
- View details
structureSkillDev tools
Helps structure learning material: breaking it into modules, logical sequencing, learning objectives. Use when: structure, learning plan, modules, outline.
Ready to connect
- View details
sync-upstreamSkillDev tools
Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.
Ready to connect
- View details
test-firstSkillDev tools
The test-SHAPING technique applied inside the test-first protocol — pick the lowest test level that exercises the behavior (unit, integration, contract, e2e, golden, property-based, evaluation), name the test after the spec contract, and assert one outcome per test. The workflow itself (entry condit
Ready to connect
- View details
test-rebase-rulesSkillDev tools
Tests rebase rules by running actual rebase.sh functions against upstream content and comparing with the expected che-code result. Use when asked to test rebase rules, verify rebase rules work correctly, or after fixing rebase rules.
Ready to connect
- View details
test-writingSkillDev tools
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.
Ready to connect
- View details
text-statsSkillDev tools
Compute word count, character count, or reading time for a piece of text using the in-bundle text-stats engine. Invoke whenever the user asks how long a passage is, how many words or characters it has, or how long it takes to read.
Ready to connect
- View details
tool-rename-deprecationSkillDev tools
Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.
Ready to connect
- View details
uv-package-managerSkillDev tools
Teaches your agent to manage Python packages and dependencies using the uv tool.
Ready to connect
- View details
ux-themingSkillDev tools
VS Code theming, color tokens, widget styles, focus indicators, and high-contrast theme support. Use when registering colors, styling widgets with theme tokens, or ensuring HC/focus compliance.
Ready to connect
- View details
validate-rebase-rulesSkillDev tools
Validates that .rebase/ rules (replace, add, override) are still current against upstream VS Code. Generates a rebase-rules-validation.md report with mismatches and proposed fixes. Use when asked to check, validate, or audit rebase rules, or before a rebase.
Ready to connect
- View details
write-frontend-testsSkillDev tools
Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them. TRIGGER when user asks to write frontend tests, add test coverage, or 'write tests for my changes'.
Ready to connect
- View details
writing-csharpSkillDev tools
Idiomatic C# /.NET development. Use when writing C# code, changing `.csproj`
Ready to connect
- View details
writing-goSkillDev tools
Idiomatic Go development. Use when writing Go code, designing APIs, reviewing
Ready to connect
- View details
writing-java-kotlinSkillDev tools
Idiomatic modern Java and Kotlin JVM development. Use when writing `.java`,
Ready to connect
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,082 of the 54,514 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.