agentleFS
rasulshaikhrasulshaikh/fde-desk/.claude/skills/deploy-surface-check/SKILL.md

deploy-surface-check

Skill0 starsChanged 48 days agoMITView on GitHub

Decide where a customer-facing piece should run (Render, Railway, optional Oracle A1) and what to verify before go-live. Before first deploy, before promoting a prototype, or when infra-ops is triageing a red service.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Before first deploy, before promoting a prototype, or when infra-ops is triageing a red service.

    line 7
  2. Distinctive:

    Oracle Ampere / A1: only when you need always-on ARM VMs or self-host outside PaaS limits.

    line 15
  3. Distinctive:

    No customer PII in build logs

    line 22
  4. Very specific:

    Run a smoke request after deploy.

    line 23
  5. Distinctive:

    If anything irreversible (DNS cutover, production DB migrate) is required, stop for human approve.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Skill: deploy-surface-check

Decide where a customer-facing piece should run (Render, Railway, optional Oracle A1) and what to verify before go-live.

When to use

Before first deploy, before promoting a prototype, or when infra-ops is triageing a red service.

Steps

  1. Name the surface: web API, worker, cron, static site, self-hosted tool (for example n8n).
  2. Pick host:
    • Render for durable public services and managed SSL.
    • Railway for fast sidecars and short-lived experiments.
    • Oracle Ampere / A1 only when you need always-on ARM VMs or self-host outside PaaS limits.
  3. Checklist (write answers into ops/<slug>/deploy/surface-check.md):
    • Env vars listed without values; secrets only in the host secret store
    • Health endpoint or process check defined
    • Logs retention and who gets paged
    • Rollback: previous deploy id or image tag
    • Outbound network needs (Clay, Supabase, Smartlead) documented
    • No customer PII in build logs
  4. Run a smoke request after deploy; record status in ops/templates/stack-status.md style notes.
  5. If anything irreversible (DNS cutover, production DB migrate) is required, stop for human approve.

Anti-patterns

  • Shipping with secrets in repo or in Render/Railway "synced from .env committed file"
  • Using Oracle A1 by default when Render would do
  • Skipping health checks because "it works on my laptop"

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.