How do I install the Heroku Domains Tls skill?

Run npx skillmds@latest add dsouzaanush/heroku-domains-tls in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Heroku Domains Tls safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Heroku Domains Tls?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Heroku Domains Tls free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Heroku Domains Tls?

dsouzaAnush (@dsouzaanush) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Heroku Domains Tls by dsouzaanush — Agent Skill

Name: Heroku Domains Tls
Rating: 4.666666666666667 (3 reviews)
Author: dsouzaAnush

Heroku Domains Tls

Configure custom domains and TLS on Heroku with ACM-first guidance. Use when the agent needs to add or inspect domains, enable or refresh automated certificate management, review certificate status, attach or replace manual certificates, or manage domain cutover safely on Heroku.

dsouzaAnush Updated Aug 19, 2026 0 repo stars

File contents

Heroku Domains and TLS

Manage custom domains and certificates without treating DNS or certificate changes as harmless.

Preferred model

For common-runtime apps, prefer Automated Certificate Management (ACM) first:

heroku domains:add
heroku certs:auto:enable
heroku certs:auto:refresh only when verification or renewal needs to be retriggered

Use manual certificates only when ACM is not viable or the user explicitly requires manual certificate control.

Read-only-first flow

Begin with:

heroku domains:info <hostname> -a <app>
heroku domains:wait <hostname> -a <app>
heroku certs:info -a <app> --show-domains

Use inspection to confirm:

the target hostname
the DNS target that must exist before TLS can activate
whether the hostname is an apex domain that needs ALIAS, ANAME, or equivalent flattening instead of an A record
whether ACM already covers the domain
whether a manual certificate is currently attached

Manual certificate workflow

Use manual certificate management intentionally:

heroku certs:add <crt> <key> -a <app>
heroku certs:update <crt> <key> -a <app> --name <name>
heroku domains:update <hostname> -a <app> --cert <name>
heroku certs:remove -a <app> --name <name>

Guardrails

Ask for confirmation before:

adding or removing a custom domain
changing DNS targets during a live cutover
enabling manual certificates instead of ACM
replacing or removing a certificate
repointing a hostname to a different certificate

References

Read references/domains-tls.md for DNS validation, ACM troubleshooting, and source links.

---name: heroku-domains-tlsdescription: Configure custom domains and TLS on Heroku with ACM-first guidance. Use when the agent needs to add or inspect domains, enable or refresh automated certificate management, review certificate status, attach or replace manual certificates, or manage domain cutover safely on Heroku.---# Heroku Domains and TLSManage custom domains and certificates without treating DNS or certificate changes as harmless.## Preferred modelFor common-runtime apps, prefer Automated Certificate Management (ACM) first:- `heroku domains:add`- `heroku certs:auto:enable`- `heroku certs:auto:refresh` only when verification or renewal needs to be retriggeredUse manual certificates only when ACM is not viable or the user explicitly requires manual certificate control.## Read-only-first flowBegin with:- `heroku domains:info <hostname> -a <app>`- `heroku domains:wait <hostname> -a <app>`- `heroku certs:info -a <app> --show-domains`Use inspection to confirm:- the target hostname- the DNS target that must exist before TLS can activate- whether the hostname is an apex domain that needs ALIAS, ANAME, or equivalent flattening instead of an A record- whether ACM already covers the domain- whether a manual certificate is currently attached## Manual certificate workflowUse manual certificate management intentionally:- `heroku certs:add <crt> <key> -a <app>`- `heroku certs:update <crt> <key> -a <app> --name <name>`- `heroku domains:update <hostname> -a <app> --cert <name>`- `heroku certs:remove -a <app> --name <name>`## GuardrailsAsk for confirmation before:- adding or removing a custom domain- changing DNS targets during a live cutover- enabling manual certificates instead of ACM- replacing or removing a certificate- repointing a hostname to a different certificate## References- Read `references/domains-tls.md` for DNS validation, ACM troubleshooting, and source links.

Frequently asked questions