devops-helper
Skill4 starsChanged 12 days agoMITView on GitHub
This skill should be used when the user asks to "set up deployment", "configure CI/CD", "create a Dockerfile", "choose a hosting platform", or discusses deployment and infrastructure decisions. Provides pragmatic DevOps guidance for indie developers.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- aiunlocked1412/claude-skill-unlocktheir own version, first seen Apr 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- aiunlocked1412/claude-skill-unlock★ 18same name
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.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- system-architectSkill
- project-detectorSkill
- audit-routerSkill
- command-skill-token-efficiencySkill
- plugin-auditSkill
- sync-featuresSkill
- backend-designerSkill
- frontend-designerSkill
- git-workflowSkill
- dist-extrasSkill
- distribution-strategistSkill
- homebrew-formula-expertSkill
- homebrew-multi-formulaSkill
- homebrew-setup-wizardSkill
- homebrew-workflow-expertSkill
- architecture-decision-recordsSkill
- changelog-automationSkill
- claude-md-lifecycleSkill
- guard-auditSkill
- hooksSkill
- insights-applySkill
- mode-controllerSkill
- drive-engineSkill
- plan-orchestratorSkill
- repo-triageSkill
- session-stateSkill
- task-analyzerSkill
- workflow-engineSkill
- orchestrator-resilienceSkill
- project-plannerSkill
- preflight-checkSkill
- releaseSkill
- test-generatorSkill
- test-strategistSkill
- adhd-workflowSkill
- brainstorm-insightsSkill
- brainstormSkill
- grillSkill
- prompt-refinerSkill
- background-task-managerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Test automation (unit, integration, e2e)
- Distinctive: line 36
Test pyramid (unit > integration > e2e)
- Distinctive: line 45
Start with platform-as-a-service (Vercel, Render)
- Distinctive: line 46
Use managed databases (don't self-host Postgres initially)
- Distinctive: line 65
When analysis is needed, I will:
- Distinctive: line 68
Delegate to agents: when feasible:
- Very specific: line 72
Run in background: - Use Task tool with run_in_background: true
- Distinctive: line 91
When activated, I provide:
≈ “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.
Files
DevOps Helper Skill
Auto-activated when: User discusses deployment, CI/CD, Docker, testing automation, or infrastructure decisions.
Core Capabilities
1. CI/CD Pipelines
- GitHub Actions workflow design
- Test automation (unit, integration, e2e)
- Build optimization
- Deployment strategies (blue/green, canary, rolling)
- Secrets management
2. Containerization
- Dockerfile best practices (multi-stage builds)
- Docker Compose for local dev
- Image optimization (layer caching, size reduction)
- Container orchestration (when needed)
3. Deployment Platforms
- Platform selection (Vercel, Render, Fly.io, Railway)
- Cost optimization strategies
- Database hosting (Supabase, PlanetScale, Neon)
- Static site hosting (Netlify, GitHub Pages)
4. Testing Automation
- Test pyramid (unit > integration > e2e)
- Pre-commit hooks (Husky, lint-staged)
- Code quality gates (coverage thresholds)
- Performance testing basics
Design Philosophy: Solid Indie
Ship Fast Principles:
- Start with platform-as-a-service (Vercel, Render)
- Use managed databases (don't self-host Postgres initially)
- Automate tests, but don't obsess over 100% coverage
- Monitor errors (Sentry), not metrics initially
Right-Sized DevOps:
- Solo/small team: GitHub Actions + Vercel
- Need scaling: Add Fly.io or Railway
- Need full control: Then consider AWS/GCP (not before)
Anti-Patterns to Avoid:
- ❌ Kubernetes for < 10 person teams
- ❌ Self-hosted infrastructure before product-market fit
- ❌ Complex multi-environment setups (dev/staging/prod initially)
- ❌ Over-monitoring (start with errors, add metrics later)
Delegation Strategy
When analysis is needed, I will:
- Quick assessment - Identify DevOps problem
- Delegate to agents when feasible:
devops-engineeragent for pipeline optimizationexperienced-engineeragent for testing strategyperformance-engineeragent for build performance
- Run in background - Use Task tool with
run_in_background: true - Synthesize results - Provide actionable DevOps recommendations
Example Activation
User: "I need to set up deployment for my Next.js app with a PostgreSQL database"
Skill activates and provides:
1. Platform recommendation (Vercel for Next.js + Supabase for PostgreSQL)
2. CI/CD setup (GitHub Actions for tests, Vercel auto-deploys)
3. Environment variables strategy (.env.local, Vercel env vars)
4. Database migrations approach (Drizzle or Prisma)
5. Delegates infrastructure review to devops-engineer agent (background)
6. Returns with complete deployment setup planOutput Format
When activated, I provide:
Immediate Response
- Platform Recommendation: Best fit for project size/budget
- Quick Win: Fastest path to deployment
- Cost Estimate: Monthly hosting costs (indie budget)
Delegated Analysis (Background)
- Launch appropriate agent for infrastructure review
- Provide progress updates
- Synthesize recommendations
Final Output
- Deployment strategy with rationale
- Step-by-step setup (numbered, concrete)
- GitHub Actions workflow (YAML example)
- Environment variables checklist
- Next steps (what to deploy first)
Platform Decision Matrix
| Need | Recommended Platform | Monthly Cost |
| Static site | GitHub Pages / Netlify | Free |
| Next.js/React | Vercel | Free tier → $20/mo |
| Full-stack app | Render / Railway | $7-20/mo |
| Python/Django | Fly.io / Render | $5-15/mo |
| Database | Supabase / PlanetScale | Free tier → $25/mo |
| Background jobs | Render Cron / Railway | Included |
CI/CD Templates
I'll provide templates for:
GitHub Actions Workflow
# Basic CI workflow for testing + deployment
name: CI/CD
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run tests
run: npm test
deploy:
needs: test
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- name: Deploy to Vercel
# Vercel auto-deploys via GitHub integrationDocker Multi-Stage Build
# Build stage
FROM node:18-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
# Production stage
FROM node:18-alpine
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY package*.json ./
RUN npm ci --production
CMD ["node", "dist/index.js"]Integration with Existing Workflow
- Auto-activates during
/brainstormfor deployment discussions - Works with
/next(suggests DevOps implementation steps) - Integrates with
/done(captures deployment decisions, configs used)
Cost Optimization Tips
Free Tier Strategy:
- Frontend: Vercel/Netlify free tier (hobby projects)
- Backend: Render free tier (spins down after 15 min idle)
- Database: Supabase free tier (500MB, unlimited API requests)
- Monitoring: Sentry free tier (5K events/month)
Total: $0/month for MVP, scales to ~$50/month at 1K users
Remember: This skill auto-activates based on keywords. Keep recommendations indie-friendly (managed platforms, reasonable costs, minimal complexity). Ship fast, scale later.
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
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.

