claudeskills.page

13 skills · category

Automation & Tooling skills for Claude Code

Skills for automating the repetitive parts of work: n8n and no-code automations, browser automation scripts, command-line tools people enjoy using, scheduled jobs that never silently miss a run, task runners, mailbox processing, macOS and Home Assistant automations, dotfiles, terminal workflow and git hooks.

Download all 13 (.zip) Browse the list
~/.claude/skills

curl -fsSL claudeskills.page/install.sh \
| sh -s -- --category automation

Done. 13 skills ready · run /skills to confirm

All 13 Automation & Tooling skills

Each card opens the full playbook, example prompts and install commands.

Browser Automation

Script browser chores that resume, not break

Claude checks for an API first, then scripts the chore in Playwright with role-based locators, condition waits instead of sleeps, saved session state, retries with backoff and a progress ledger so reruns skip finished items. It keeps credentials out of code, throttles politely, and pauses for a human at MFA or CAPTCHA prompts rather than trying to get around them.

browser-automation 183 lines

CLI Tool Building

CLIs that work for humans and in pipes

Claude writes the help text before the code, keeps data on stdout and everything else on stderr, uses meaningful exit codes, and adds --json, --dry-run and --yes so the tool works in scripts as well as terminals. It scaffolds in Typer, Click, commander or cobra, tests with CLI runners, and ships via uv tool, npm or GoReleaser.

cli-tool-building 210 lines

Dotfiles Management

One command to a working machine, zero secrets in git

Claude builds a chezmoi (or Stow or yadm) repo where machine differences live in templates and prompted data, secrets come from 1Password, Bitwarden or age encryption at apply time, and run_onchange scripts reinstall packages when the Brewfile changes. Every apply is previewed with a diff, the repo is secret-scanned before pushing, and a fresh container proves the one-line bootstrap.

dotfiles-management 200 lines

Email Automation

Process every message once, never reply to robots

Claude reads mailboxes through the Gmail API, Microsoft Graph or IMAP with the narrowest scope that works, syncs incrementally with UIDs or historyId, and records every processed message in a ledger so reruns never double-act. A bundled parser extracts bodies and sanitized attachments and applies RFC 3834-style rules so auto-replies skip newsletters, bounces and other bots.

email-automation 165 lines · 2 files

Git Hooks Automation

Fast commit hooks backed by the same checks in CI

Claude chooses one hook framework for the repo (pre-commit, lefthook or husky with lint-staged), splits checks between commit, push and CI so commits stay fast, and pins every hook version. Fixes are re-staged without touching unstaged work, gitleaks blocks secrets before they reach history, hooks install themselves, and CI runs the same checks so --no-verify bypasses nothing.

git-hooks-automation 168 lines · 2 files

Home Assistant

Automations that fire right and explain themselves

Claude writes Home Assistant automations in the post-2024.10 schema with stable IDs, the right mode, debounced triggers and guards against unavailable states. Templates get defaults and availability checks, repeated logic becomes blueprints or scripts with fields, configs are split into packages with secrets kept out of git, and missed automations are diagnosed from their traces.

home-assistant 259 lines

macOS Automation

Shortcuts, AppleScript and launchd that just keep running

Claude picks the least fragile macOS mechanism for the job: a Shortcut or Tahoe automation, AppleScript or JXA against the app's dictionary, or a launchd agent with StartCalendarInterval or WatchPaths. Paths are absolute, secrets come from the Keychain, logs go to ~/Library/Logs, and privacy errors like -1743 are traced to the exact binary that needs permission.

macos-automation 190 lines

n8n Workflows

n8n automations that retry safely and report failures

Claude builds n8n workflows item by item with pinned test data, dedupes webhook deliveries, sets per-node retries and an error workflow that posts the execution link, and keeps secrets in credentials only. It knows the 2.x save-versus-publish model and new defaults, exports workflows to git, and self-hosts with Postgres, external task runners and a backed-up encryption key.

n8n-workflows 191 lines

No-Code Automation

Zaps and scenarios that run once, alert and stay cheap

Claude specs each automation with owner, volume and cost before building, chooses instant or polling triggers with deduplication in mind, and filters early so billable steps only run when needed. It adds Zapier replays or Make error handlers with alerts, uses service-account connections, and tells you plainly when a flow has outgrown the canvas and belongs in code.

no-code-automation 150 lines
★ Editor's pick

Scheduled Jobs

Cron jobs safe to rerun, overlap-proof and watched

Claude designs the job to be rerun safely before choosing a schedule, then wires it into a systemd timer, cron, launchd or a Kubernetes CronJob with catch-up, jitter and a time limit. A bundled wrapper adds a portable single-instance lock, UTC logs and healthcheck pings, and every job ships with a heartbeat monitor that alerts when it silently stops running.

scheduled-jobs 212 lines · 2 files

Task Runners

One command menu for every repo, same in CI

Claude inventories the commands scattered across README, CI and scripts, picks one runner (npm scripts, just, Taskfile or Make), and maps them to standard names like setup, dev, test and check. Tasks fail fast under strict shell settings, list themselves with descriptions, confirm before deploying, and CI calls the very same check task developers run locally.

task-runners 224 lines

Terminal Productivity

A fast shell where everything is a few keys away

Claude measures shell startup before changing anything, profiles slow plugins, and builds a lean setup: shared deduplicated history, fzf pickers for files, history and branches, zoxide jumps, tmux sessions that survive disconnects, and a minimal starship prompt. Aliases come from your most-repeated commands, and secrets stay out of rc files and history.

terminal-productivity 212 lines

Windows Automation

Scheduled tasks and installs that run with nobody logged in

Claude wires scripts into Windows the way an admin would: tasks registered from code with an explicit principal, time limit, catch-up and restart settings, transcripts under ProgramData, and exit codes Task Scheduler actually records. Installs go through winget with exact IDs, registry changes are backed up and read back, and AutoHotkey v2 is used only when an app has no API.

windows-automation 255 lines

Choosing Automation & Tooling skills

Install the skills that match requests you make every week. Each costs about 100 tokens of standing context until Claude loads it.

Start with

Background reading

Install

Every Automation & Tooling skill in one command

Installs all 13 into ~/.claude/skills/. Add --project after -- to install into the current repository instead.

The installer is a 101-line POSIX shell script. It downloads each skill you name from claudeskills.page and unpacks it into your skills folder, nothing else: no sudo, no telemetry. Every skill page shows the full SKILL.md, so you can read what you install first. Read install.sh

All 13 Automation & Tooling skills

curl -fsSL https://claudeskills.page/install.sh \ | sh -s -- --category automation

Only the ones you want: list their names

curl -fsSL https://claudeskills.page/install.sh \ | sh -s -- browser-automation cli-tool-building

Automation & Tooling skills FAQ

Short answers about installing and using these skills. For the details, read the install guide.

How do I install every Automation & Tooling skill at once?

Run curl -fsSL https://claudeskills.page/install.sh | sh -s -- --category automation to install all 13 into ~/.claude/skills/, adding --project to install into the current repository. Or download the bundle at https://claudeskills.page/downloads/category/automation.zip and unzip it yourself. To pick a few, pass their names instead: curl -fsSL https://claudeskills.page/install.sh | sh -s -- browser-automation cli-tool-building dotfiles-management.

Will installing 13 skills slow Claude Code down?

No. Claude Code keeps only each skill's short description in context — roughly 100 tokens per skill — and loads the full instructions only when a request matches. Install the whole category if it fits your work; unused skills cost almost nothing.

Which Automation & Tooling skill should I start with?

Start with Scheduled Jobs, Browser Automation, CLI Tool Building. They cover the most common requests in this category; add the rest as your work calls for them.

Collections with Automation & Tooling skills

Explore other categories

esc