shell-history-hygiene
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-25 00:14
12,494 results
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to…
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or…
Audit OpenClaw token usage, purge stale sessions, and optimize inference speed. Use when the user sends /optimize, /audit, asks to purge sessions, or wants a…
Use when creating Autonomous Databases, troubleshooting wallet connection failures, managing PDBs, optimizing ADB costs, or selecting clone types. Covers…
Diagnose and fix failing or degraded skills automatically - systemic-first triage, per-category playbooks, and a verification plan
Autonomous cloud-cost analyst across Neon, Vercel, Railway and GitHub Actions - pulls per-object usage, attributes it to the biggest drivers, root-causes each,…
Deploy affiliate content to GitHub Pages for free hosting. Triggers on: "deploy to GitHub Pages", "host on GitHub Pages", "free hosting for my affiliate site",…
Visit each competitor's homepage, features page, pricing page, and blog using Chrome MCP, then write a structured competitive intelligence report saved to…
Laravel Horizon queues, Octane performance, Reverb WebSockets, Redis caching, PostgreSQL database. ALWAYS activate when: working with queue jobs, cache,…
Use when choosing and architecting an Amazon ECS deployment model for a NEW workload — Fargate vs ECS on EC2 vs Managed Instances vs Express Mode vs ECS…
Run local performance audits on a project without network calls. This skill should be used when the user says 'audit performance', 'check bundle size', 'find…
Wait for CI/CD pipelines to complete after pushing code, then act on results. This skill should be used after git push, after creating a PR, when the user says…
Cut a GitHub release for a project from a bump keyword, then let CI publish. Use when the user runs /release <major|minor|patch|stable [beta]> (optionally a…
Generate GitHub release notes / a changelog for a project by diffing a base ref against origin/main. Use when the user runs /release-notes (optionally a…
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
LOAD THIS SKILL when: reading application logs, listing log files, or accessing remote pod logs. Contains all logs-tool commands.
For an external contributor's open PRs to brave/brave-core, ensure the `sync-and-rebase-pr-from-fork.yml` workflow has been dispatched for each PR's latest…
Fall-to-disk rules and templates after deep learning platform initialization is complete: solidify verified platform knowledge into the fixed common-name accel trio and the host layer. Use when an accelerator platform setup just finished and needs to be distilled, when specializing or…
Audit accelerator environment skills and platform/cluster docs for personal repository, user, Conda, credential, and validation-artifact leakage; use when…
ByteHouse cluster diagnostic tool, used for health checks, slow query analysis, load analysis, performance bottleneck diagnosis, and throughput analysis. Use this Skill when users mention operational troubleshooting needs such as "ByteHouse cluster diagnosis", "health check", "slow query", "query optimization", "performance analysis", "load analysis", "resource usage", "throughput", "compute group", "CPU/memory alert", etc.
Manages Volcano Engine (Volcengine) ESCloud/CloudSearch (Elasticsearch + OpenSearch) clusters: control plane provisioning/scale/delete via…
For daily operations inspection scenarios, collect alarms, health checks, and other information on a daily basis, structure and accumulate it, and output it periodically (daily/weekly/monthly reports).
Perform change risk analysis for scenarios such as code changes, configuration changes, scaling up or down, network policy adjustments, and ingress switching. Whenever the user is asking questions like "how risky is this change", "what will this change affect", or "which services/resources will be impacted upstream and downstream", this skill should be used; even if the user only provides a natural language change description, proactively try to combine topology.json…
Bring up the stack and test/demo end-to-end the **deployment/infrastructure** of a private IPFS Cluster (Kubo) — single-machine 3-node docker-compose. Generate secrets → start the cluster (including Caddy reverse proxy) → verify the three peers are formed → upload HTML via the cluster proxy (:9095) → assert three-node replicas PINNED →…