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 126 of 149
- View details
no-commentsSkillFiles & storage
Use when asked to audit comments in code files and propose structural replacements or deletions with per-candidate approval. Enumerates comments in C, JavaScript, TypeScript, HTML, CSS, and shell-style syntax, classifies each as earned or unearned, drafts structural alternatives, and returns a compl
Ready to connect
- View details
odylith-code-hygiene-guardSkillFiles & storage
Use when a slice shows duplicate helpers, fake modularization, oversized-file pressure, or AI-shaped code slop that needs explicit cleanup discipline.
Ready to connect
- View details
odylith-syncSkillFiles & storage
Use when changed files need governed Odylith surfaces refreshed.
Ready to connect
- View details
okf-project-knowledge-baseSkillFiles & storage
Durable project knowledge as Git-native OKF bundles (docs/knowledge/, one concept per file, with provenance and trust tiers). Use to record a decision, finding, or rule that must outlive the session. Not session state or agent instructions.
Ready to connect
- View details
pre-compactSkillFiles & storage
Prepare the session for context compaction - write a handoff file a fresh session can continue from, propose updates to the project's durable docs, apply them on approval or with `auto`. Use before compacting or clearing context, or on "pre-compact".
Ready to connect
- View details
premortemSkillFiles & storage
Imagine failure first to surface guardrails before plan execution or deliverable ship. Two modes: --plan (5 strategic domains for plan files in ~/.claude/plans/) and --output (5 execution domains for shippable deliverables like LinkedIn posts, AEO articles, landing-page-copy, proposals, positioning)
Ready to connect
- View details
prohibit-bad-habitsSkillFiles & storage
Use when a user wants to define patterns the agent should not do; result is structured project docs or agent-rule files listing each prohibited pattern. Don''t use for remote, credential, publish, deploy, or irreversible changes.
Ready to connect
- View details
push-gateSkillFiles & storage
Pre-push safety gate for any git push to a remote (GitHub, GitLab, Bitbucket, self-hosted). Runs gitleaks + regex-layer secret scan, forbidden-file check, divergence check, size warning, and requires explicit confirm before pushing. Refuses on any secret hit. Triggers on: push to origin, push to git
Ready to connect
- View details
reel-analyzerSkillFiles & storage
Feed Claude any viral reel (a link or a file) and it studies the whole thing — frame by frame plus the transcript — then breaks down exactly why it works: the hook, the beat structure, the pacing, and the on-screen visuals. Use when the user says "study this reel", "break down this video", "analyze
Ready to connect
- View details
refactor-opsSkillFiles & storage
Safe refactoring patterns - extract, rename, restructure with test-driven methodology and dead code detection. Use for: refactor, refactoring, extract function, extract component, rename, move file, restructure, dead code, unused imports, code smell, duplicate code, long function, god object, featur
Ready to connect
- View details
rfdb-batchhandle-deletes-existing-nodesSkillFiles & storage
Fix nodes silently disappearing from RFDB when an enricher or post-resolution pass writes new nodes via BatchHandle. Use when: (1) writing a TypeScript enricher that should ADD nodes/edges to existing files, (2) after calling `client.createBatch()` + `batch.addNode({file: 'X', ...})` + `batch.commit
Ready to connect
- View details
rfdb-metadata-gotchasSkillFiles & storage
Fix silent metadata issues in RFDB node storage. Covers two traps: (1) metadata flattening — nested metadata fields become top-level after serialization, so node.metadata.field is undefined but node.field works. (2) reserved keys — fields named "type", "id", "name", "file", "exported" are silently s
Ready to connect
- View details
rfdb-stale-node-cleanupSkillFiles & storage
Recover from stale RFDB nodes that survive `commit_batch` cleanup despite having their `file` field listed in `changed_files`. Use when: (1) re-running an enricher/orchestrator step but old data with the same file field stays in the graph, (2) `commit_batch(changed_files=[X], ...)` reports success b
Ready to connect
- View details
rfdb-v2-clear-ephemeral-trapSkillFiles & storage
Fix RFDB V2 graph data silently not persisting to disk after analysis. Use when: (1) rfdb-server reports "0 nodes, 0 edges" on restart despite successful analysis, (2) segment directories exist but are empty (no .bin files), (3) manifest_index.json shows total_nodes: 0 despite analysis logging 70k+
Ready to connect
- View details
runbookSkillFiles & storage
'Synthesizes documentation sources (SKILL.md files, MCP configs, code comments, client docs) into structured
Ready to connect
- View details
skill-reviewerSkillFiles & storage
'Reviews SKILL.md files for structural quality across 8 dimensions (frontmatter, triggers, process, inputs, outputs,
Ready to connect
- View details
skillifySkillFiles & storage
Distil a proven workflow from this conversation into a reusable Skill file.
Ready to connect
- View details
skills-best-practicesSkillFiles & storage
Build high-quality Agent Skills for any agent - opinionated best practices distilled from the Agent Skills spec, official Anthropic guidance, and production experience. Covers SKILL.md structure, frontmatter, description writing, single-file vs references/ layout, progressive disclosure, testing, pa
Ready to connect
- View details
spawnSkillFiles & storage
Generate PhD-level expert-agent prompt files (.md) for Claude Code - authoring, not runtime. For spawning parallel RUNTIME workers use fleet-worker/fleetflow (via parallel-ops). Triggers: spawn agent, create agent file, generate expert prompt, new agent persona.
Ready to connect
- View details
standard-readmeSkillFiles & storage
Writes or audits README files following the Standard Readme specification (github.com/RichardLitt/standard-readme). Use whenever the user asks to create, write, rewrite, improve, audit, or fix a README, or asks about README quality or structure - even if they never mention "standard readme" explicit
Ready to connect
- View details
testgenSkillFiles & storage
Generate tests with skill-preloaded routing, framework detection, and auto-TaskCreate. Triggers on: generate tests, write tests, testgen, create test file, add test coverage.
Ready to connect
- View details
add-rebase-rulesSkillFiles & storage
Generates .rebase add/override/replace rules from a commit that changes code/ files, updates rebase.sh conflict routing, and appends .rebase/CHANGELOG.md. Use when asked to add rebasing rules for a commit or PR.
Ready to connect
- View details
aicooSkillFiles & storage
Aicoo Skills — your AI COO. Onboard to Aicoo, sign in, build your agent's memory from your files and repo, share your agent via a link, invite teammates, sync notes and context, talk to other people's agents, and browse or post on Aicoo Square. Triggers: 'onboard aicoo', 'set up aicoo', 'sign in to
Ready to connect
- View details
author-contributionsSkillFiles & storage
Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns
Ready to connect
- View details
autonomous-syncSkillFiles & storage
Use this skill when the user wants to keep their Aicoo agent updated automatically, set up scheduled syncs, configure triggers for knowledge updates, use CRON jobs, /loop commands, file watchers, or hooks to push changes to Aicoo. Triggers on: 'auto sync', 'keep updated', 'schedule', 'CRON', 'loop',
Ready to connect
- View details
build-memorySkillFiles & storage
Use this skill when the user wants to build, refresh, or teach their Aicoo agent memory from their real context — files, repo, git history, docs, or Claude/agent memory. Triggers on: 'build my memory', 'build my agent memory', 'teach my agent about me', 'what should my agent know', 'update my memory
Ready to connect
- View details
code-oss-logsSkillFiles & storage
Find and read logs from Code OSS dev builds. Use when: finding logs, reading log files, debugging Code OSS, checking renderer logs, extension host logs, agent host logs, main process logs, investigating errors in dev builds.
Ready to connect
- View details
compile-identitySkillFiles & storage
Use this skill when the user wants to hand a session off to another agent, share their working context, compile a session into something another agent can read, write a POSITIONS file, record which decisions were overruled, prepare a handoff folder, or measure whether a shared folder actually transf
Ready to connect
- View details
component-fixturesSkillFiles & storage
Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.
Ready to connect
- View details
cpu-profile-analysisSkillFiles & storage
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-*.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/render
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,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.