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,833 results · page 87 of 562
- View details
humanize-rlcrSkillDev tools
Start RLCR (Ralph-Loop with Codex Review) on Codex using the native Stop hook.
Ready to connect★ 1k
- View details
- View details
auditSkillDev tools
Use when stuck, confused, or disoriented in a crosslink-tracked project — dumps the full context (session state, active issue, locks, blockers, hook config, git state, project rules) so you can re-orient and decide a next action. Trigger when the user says "I'm stuck", "audit", "what's going on", or
Ready to connect★ 1k
- View details
crosslink-guideSkillDev tools
Use when working in any repo that has `.crosslink/` and the workflow involves issue tracking, sessions, locks, swarms, kickoff, or knowledge pages. Reference for the full crosslink CLI surface plus the harness footguns (auto-CHANGELOG entries on issue close, --no-changelog flag, label-based skip rul
Ready to connect★ 1k
- View details
featureSkillDev tools
Use to create a `feat/<slug>` branch from a human-readable description and register a matching crosslink issue (priority medium, label `feature`). Slugifies the description, validates preconditions (no uncommitted changes, branch doesn't already exist), and checks out the new branch. Trigger when th
Ready to connect★ 1k
- View details
atmos-ansibleSkillDev tools
Ansible orchestration: playbook execution, variable passing, inventory management, stack-based configuration for configuration management
Ready to connect★ 1k
- View details
atmos-compositionsSkillDev tools
Atmos compositions: named service groupings, compositions.<name>.services, components.container[*].composition, composition validate, and service contract checks
Ready to connect★ 1k
- View details
atmos-configSkillDev tools
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, base_path, imports, minimal bootstrap, and routing to narrower Atmos skills
Ready to connect★ 1k
- View details
atmos-custom-commandsSkillDev tools
Custom CLI commands: command definition in atmos.yaml, arguments, flags, shared native step types, when: conditions, output/UI steps, env vars, custom component types
Ready to connect★ 1k
- View details
atmos-devcontainerSkillDev tools
Devcontainer orchestration: start/stop/attach/shell/exec/rebuild, instance management, config handling, VS Code integration
Ready to connect★ 1k
- View details
atmos-gitSkillDev tools
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts
Ready to connect★ 1k
- View details
atmos-importsSkillDev tools
Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts
Ready to connect★ 1k
- View details
atmos-initSkillDev tools
Bootstrapping new Atmos projects with atmos init: built-in template catalog, differences from atmos scaffold generate, project record, and update-safe 3-way merge
Ready to connect★ 1k
- View details
atmos-introspectionSkillDev tools
Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help=<topic> scoped CLI help
Ready to connect★ 1k
- View details
atmos-modernizationSkillDev tools
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, name_template, and declared secrets
Ready to connect★ 1k
- View details
atmos-proSkillDev tools
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection
Ready to connect★ 1k
- View details
atmos-profilesSkillDev tools
Atmos profiles: profile directories, --profile and ATMOS_PROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides
Ready to connect★ 1k
- View details
atmos-project-layoutSkillDev tools
Atmos project layout: base_path, relative path resolution, root stacks/components/workflows/schemas directories, atmos.d modular config, and repository path conventions
Ready to connect★ 1k
- View details
atmos-schemasSkillDev tools
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration
Ready to connect★ 1k
- View details
atmos-secretsSkillDev tools
Atmos Secrets: declarative secrets.vars, !secret, cloud/Vault/1Password/SOPS backends, init/set/get/import/push/pull/shell/exec/validate, masking, and CI validation
Ready to connect★ 1k
- View details
atmos-stacksSkillDev tools
Stack configuration: local and remote imports, inheritance, deep merging, locals, vars, settings, metadata, overrides, dependencies, and modernization
Ready to connect★ 1k
- View details
atmos-stepsSkillDev tools
Shared Atmos step DSL for workflows, custom commands, hooks, and cast recordings: step types, env, output, working_directory, retry, and native alternatives to shell glue
Ready to connect★ 1k
- View details
atmos-templatesSkillDev tools
Go templates: Sprig/Gomplate functions, Atmos's own collectKeys, atmos.Component, atmos.GomplateDatasource, atmos.Store, template configuration, evaluations
Ready to connect★ 1k
- View details
atmos-workflowsSkillDev tools
Workflow automation: native step types, multi-step workflows, parallel/matrix/wait/container/emulator steps, when: conditions (CEL), require/assert preconditions, output steps, retries, dependencies, and cross-component orchestration
Ready to connect★ 1k
- View details
code-hygieneSkillDev tools
Reviews code changes for architectural smells that mechanical checks (lint, tests, coverage) structurally can't catch: duplicated 'shared' abstractions, missing sentinel errors, generics that discard their own type info, self-aware nolint suppressions of mandated rules, business logic in the wrong l
Ready to connect★ 1k
- View details
component-developmentSkillDev tools
Atmos core component development: adding or changing native component types, component registry providers, commands, stack schema, docs, examples, DAG/affected behavior, auth, hooks, source/provisioning, and tests
Ready to connect★ 1k
- View details
field-testSkillDev tools
Hands-on manual DX test pass of a feature or CLI command: read the real implementation and tests, hypothesize plausible user misunderstandings and misuse automated tests don't cover, build durable fixtures, execute for real against real state, and report ranked findings. Investigation only — never f
Ready to connect★ 1k
- View details
pr-maintenance-loopSkillDev tools
Start an hourly background loop that keeps the current branch's PR rebased, its addressed CodeRabbit threads resolved, its CI checks passing, its lint clean, its tests passing with adequate patch coverage, and its code free of architectural-smell (code-hygiene) findings — working toward autonomous m
Ready to connect★ 1k
- View details
speckit-checklistSkillDev tools
Generate a custom checklist for the current feature based on user requirements.
Ready to connect★ 1k
- View details
speckit-clarifySkillDev tools
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Ready to connect★ 1k
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.
53,585 of the 54,017 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.