agentleFS
Sign inStart free
batterfried-philosophy172batterfried-philosophy172/Agent-Startup-Skills/skills/deploy-planner/SKILL.md

deploy-planner

Skill2 starsChanged 7 months agoMITView on GitHub

Deployment and DevOps agent that generates Dockerfiles, CI/CD configs, and step-by-step deployment guides for free hosting platforms. Triggers on: deploy, launch, hosting, Docker, CI/CD, production, go live, ship it.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. Aizaz-Noor/Agent-Startup-Skills★ 2100% 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.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    After security audit is complete and approved

    line 18
  2. Distinctive:

    When the user asks "how do I deploy this?"

    line 19
  3. Very specific:

    Create a .env.production.example with:

    line 48
  4. Distinctive:

    Write a step-by-step guide:

    line 54
  5. Distinctive:

    All environment variables are documented

    line 101

≈ “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

Deploy Planner — Launch Preparation Agent

Purpose

Prepare the complete deployment package so the user can go from "code on my machine" to "live on the internet" with clear, step-by-step instructions.

When to Use

  • After security audit is complete and approved
  • When the user asks "how do I deploy this?"
  • As the final phase of the SaaS Accelerator pipeline

Process

Step 1: Deployment Target Selection

Recommend a free-tier hosting platform based on the tech stack:

Tech StackRecommended HostFree Tier Limits
Next.jsVercel100GB bandwidth/month
Node.js/ExpressRender750 hours/month
Python/DjangoRailway$5 free credit/month
Static + APINetlify + Supabase100GB + 500MB DB

Step 2: Docker Configuration

Generate a production Dockerfile:

  • Multi-stage build (build stage + production stage)
  • Non-root user
  • Health check endpoint
  • Minimal image size

Generate a docker-compose.yml for local development:

  • App service
  • Database service
  • Volume mounts for persistence
  • Environment variable passthrough

Step 3: Environment Setup Guide

Create a .env.production.example with:

  • Every required variable
  • Description of what each variable does
  • Where to obtain each value (e.g., "Get from Supabase dashboard")

Step 4: Deployment Guide

Write a step-by-step guide:

## Deploy to [Platform]

### Prerequisites
- [ ] Account on [platform]
- [ ] Git repository pushed to GitHub

### Steps
1. Go to [platform dashboard URL]
2. Click "New Project" → "Import from GitHub"
3. Select your repository
4. Set environment variables: [list each one]
5. Click "Deploy"
6. Wait for build to complete (~2-3 minutes)
7. Visit your live URL: https://your-app.vercel.app

### Post-Deployment Verification
- [ ] Homepage loads correctly
- [ ] User registration works
- [ ] Login/logout works
- [ ] Core feature works end-to-end
- [ ] No console errors in browser DevTools

Step 5: Project README

Generate the final README.md for the project repository:

  • Project name and one-line description
  • Tech stack badges
  • Features list
  • Local development setup (step-by-step)
  • Deployment instructions
  • Environment variables reference
  • Contributing guidelines
  • License

Output

  • Dockerfile
  • docker-compose.yml
  • .env.production.example
  • deploy_guide.md
  • Updated README.md

Exit Criteria

  • Deployment guide is platform-specific and step-by-step
  • Docker configuration is production-ready
  • All environment variables are documented
  • Post-deployment verification checklist exists
  • README is complete and professional

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.

Check your setup, free