agentleFS
SylphAI-IncSylphAI-Inc/swe-cli-skills/SKILL.md

swe-cli-skills

Skill8 starsChanged 8 months agoMITView on GitHub

Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 2

    1. SylphAI-Inc/skills★ 111100% same
    2. lsongdev/skills★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 0 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Terraform: Always terraform plan after terraform import (detects drift)

    line 92
  2. Very specific:

    kubectl: ALWAYS verify kubectl config current-context before apply

    line 94
  3. Very specific:

    Git: Use git --no-pager and --no-edit flags (agents have no TTY)

    line 96
  4. Very specific:

    SSH: Use BatchMode=yes to prevent password prompt hangs

    line 97
  5. Very specific:

    psql: Always use -v ON_ERROR_STOP=1 in scripts (psql continues after errors by default)

    line 98
  6. Very specific:

    Redis: NEVER use KEYS * in production — use SCAN instead (blocks server)

    line 99
  7. Very specific:

    gcloud: Always set --project explicitly in automation (don't rely on default project)

    line 100
  8. Very specific:

    npm: Use npm ci in CI/CD, not npm install (ensures reproducible builds)

    line 101
  9. Very specific:

    Read this root SKILL.md to find the right category

    line 112
  10. Very specific:

    Read only the specific CLI guide you need (e.g., skills/cloud/aws.md)

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SWE CLI Skills

man pages for machines — Your agent knows the commands. We teach it the workflows.

This skill provides expert-level CLI knowledge for the tools software engineers use daily. Each guide encodes senior engineer judgment — not reference docs, but operational workflows, safety guardrails, flag gotchas, error recovery, and composition patterns.

When to Use This Skill

Load a specific CLI guide when:

  • You need to run complex CLI operations (multi-step workflows, piped commands)
  • You're unsure about flag ordering, safety checks, or non-interactive alternatives
  • You encounter a CLI error and need the actual fix (not generic advice)
  • You need to compose multiple CLIs together (e.g., aws → jq → xargs)

Available CLI Guides

Guides are organized by category. Read the category index or jump directly to a CLI guide.

☁️ Cloud (skills/cloud/)

CLIFileUse For
AWS CLIskills/cloud/aws.mdS3 filter ordering, IAM auth, EC2 queries, JMESPath, Lambda
gcloudskills/cloud/gcloud.mdGCP project/config management, GKE, Cloud Run, IAM, logging
Azure CLIskills/cloud/azure.mdResource groups, AKS, App Service, RBAC, ARM deployments

🏗️ Infrastructure as Code (skills/iac/)

CLIFileUse For
Terraformskills/iac/terraform.mdState management, import workflows, safe apply, workspace migration

🐳 Containers & Orchestration (skills/containers/)

CLIFileUse For
Dockerskills/containers/docker.mdBuild cache, multi-stage builds, compose v2, cleanup, debugging
kubectlskills/containers/kubectl.mdContext safety, namespace gotchas, rollout/rollback, pod debugging
Helmskills/containers/helm.mdValues precedence, upgrade resets, rollback, chart debugging

🔀 Git & Version Control (skills/git-vcs/)

CLIFileUse For
Gitskills/git-vcs/git.mdNon-interactive alternatives, rebase, merge, conflict resolution
GitHub CLIskills/git-vcs/gh.mdPR workflows, issue management, releases, Actions

🛠️ Dev Tools (skills/dev-tools/)

CLIFileUse For
jqskills/dev-tools/jq.mdJSON filtering, select vs map, array ops, shell variable injection
sedskills/dev-tools/sed.mdStream editing, in-place substitution, macOS vs Linux portability
makeskills/dev-tools/make.mdBuild automation, Makefile patterns, phony targets, variables
curlskills/dev-tools/curl.mdAuth headers, multipart uploads, API debugging, response handling
SSH/SCPskills/dev-tools/ssh.mdTunneling, ProxyJump, key management, agent-safe patterns

📦 Package Managers (skills/package-managers/)

CLIFileUse For
npmskills/package-managers/npm.mdDependency management, scripts, workspaces, publishing, lockfiles
pip & uvskills/package-managers/pip-uv.mdVirtual envs, dependency resolution, uv acceleration, constraints

🗄️ Databases (skills/databases/)

CLIFileUse For
psqlskills/databases/psql.mdConnection strings, non-interactive queries, backup/restore, meta-commands
redis-cliskills/databases/redis.mdConnection, key operations, debugging, persistence, cluster management

🚀 Platforms & Services (skills/platforms/)

CLIFileUse For
Stripe CLIskills/platforms/stripe.mdWebhook testing, API debugging, fixtures, payment flow testing
Sentry CLIskills/platforms/sentry.mdRelease management, sourcemap uploads, deploy tracking
Vercel CLIskills/platforms/vercel.mdDeployments, env vars, serverless functions, domains
Firebase CLIskills/platforms/firebase.mdHosting deploy, Firestore rules, auth emulators, Cloud Functions
flyctlskills/platforms/fly.mdApp deployment, scaling, secrets, regions, Machines API

Quick Reference: Critical Gotchas

These are the highest-impact mistakes — check the full guide for details:

  • AWS S3: --exclude must come BEFORE --include (left-to-right evaluation)
  • Terraform: Always terraform plan after terraform import (detects drift)
  • Docker: Copy dependency files before source code (cache optimization)
  • kubectl: ALWAYS verify kubectl config current-context before apply
  • Helm: helm upgrade RESETS values not specified — use --reuse-values
  • Git: Use git --no-pager and --no-edit flags (agents have no TTY)
  • SSH: Use BatchMode=yes to prevent password prompt hangs
  • psql: Always use -v ON_ERROR_STOP=1 in scripts (psql continues after errors by default)
  • Redis: NEVER use KEYS * in production — use SCAN instead (blocks server)
  • gcloud: Always set --project explicitly in automation (don't rely on default project)
  • npm: Use npm ci in CI/CD, not npm install (ensures reproducible builds)
  • sed: sed -i behaves differently on macOS vs Linux — use -i.bak for portability
  • make: Indentation MUST be real tabs, not spaces (invisible error)
  • Stripe: stripe listen webhook secret changes on every restart — update your env var
  • Sentry: Sourcemap --url-prefix must exactly match browser request paths
  • Vercel: vercel without --prod deploys to preview, not production
  • Firebase: firebase deploy without --only deploys EVERYTHING

Token Efficiency

This skill uses a category sub-index architecture. Instead of loading all CLI guides at once:

  1. Read this root SKILL.md to find the right category
  2. Read only the specific CLI guide you need (e.g., skills/cloud/aws.md)

This keeps token usage minimal — load one guide (~200-400 lines) instead of the entire library.

Each Guide Contains

  1. Setup & Auth — Installation and credential configuration
  2. Core Workflows — The 20% of commands covering 80% of usage
  3. Flag Gotchas — Ordering traps, version quirks, surprising defaults
  4. Error Patterns — Real error messages → real fixes
  5. Anti-Patterns — "Never do X because Y" with safe alternatives
  6. Composability — How to pipe this CLI with others
  7. Agent Constraints — Non-interactive alternatives, TTY workarounds

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.