agentleFS
Sign inStart free
softstars-assoftstars-as/softkiln-plugin/skills/go-live/SKILL.md

go-live

Skill0 starsChanged 3 months agoMITView on GitHub

Put a hosted app on its own custom domain with HTTPS, and check it is production-ready — domain and certificate, secrets, backups, sign-in and a security scan. Use when the user asks to point a domain at their app, set up a custom URL or SSL, or asks whether the app is ready for real users.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. whawkinsiv/solo-founder-skills★ 260same name
    2. whawkinsiv/claude-code-skills★ 258same name
    3. ohad6k/VibeRaven★ 64same name
    4. a-lottes/aSPARK★ 25same name
    5. madeehahassan/plsbuild-os★ 1same name
    6. akimisri17/idea-to-app-kit★ 0same 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Start with get_app for the app's current production and dev URLs, and list_domains for what is already pointing at it.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Take the app live on its own domain

A deployed app already has a production URL. This is the rest: the user's own domain, and the checks worth running before real people arrive.

Start with get_app for the app's current production and dev URLs, and list_domains for what is already pointing at it.

The domain

add_domain attaches the domain and syncs the DNS records; the certificate is issued and renewed automatically. Then set_primary_domain to make it the one the app is actually presented as — attaching a domain does not promote it.

Verification is not instant. Re-run list_domains rather than assuming it worked, and tell the user plainly if it has not verified yet.

Before you tell them it is ready

  • run_security_scan, then list_security_findings. Report what it found; don't allow-list a finding to make the output clean.
  • get_backup_health — a never or stale verdict means there is no restore path. update_backup_settings to fix the schedule, and trigger_backup for one now.
  • get_variables — confirm the production environment has the configuration it needs. Values are never returned, only whether a key is set; that is enough to spot a missing one.
  • get_app_auth and get_signin_experience if the app has users. The sign-in page is branded through set_signin_branding and set_signin_css, not by anything in the repo.
  • get_app_status on prod — last, to confirm what is live is what you think.

Do not

  • Promise a domain is live before list_domains says it verified.
  • Suggest a DNS or certificate step the user has to do by hand. If something needs their action, add_domain says so in what it returns.

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