domain-attachment

Attach domains to applications with creation-time or post-creation binding.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nixopus/agent --skill domain-attachment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-attachment
Source: https://github.com/nixopus/agent/tree/main/skills/domain-attachment
Command: npx skills add https://github.com/nixopus/agent --skill domain-attachment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain management for applications is error-prone and manual, leading to DNS misconfigurations and TLS provisioning delays. This skill standardizes domain attachment flows to ensure reliable access and automated security.

Core Features & Use Cases

  • Preferred path: pass domains at creation time using a generated subdomain; wildcard DNS and TLS are automatic.
  • Post-Creation: attach a generated subdomain to an existing app via add_application_domain; TLS is handled automatically.
  • Custom Domain Setup: use create_domain to obtain DNS instructions, then update_domain and attach the domain.

Quick Start

Use a domain-attachment command to attach a domain to your app at creation or after deployment.

Frequently Asked Questions about domain-attachment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bind a custom domain to an existing application?

To bind a custom domain, use create_domain to retrieve DNS instructions, configure your DNS records, then call update_domain and attach the domain to your application. This validates DNS and completes domain attachment.

Can I attach a generated subdomain during application creation?

Yes, you can attach domains at creation time by passing a generated subdomain. This preferred path automatically handles wildcard DNS and TLS provisioning, ensuring reliable access and automated security without manual setup.

What is the best way to automate TLS provisioning for subdomains?

Automating TLS provisioning is best achieved by attaching a generated subdomain to your app. Both creation-time and post-creation attachment via add_application_domain handle TLS automatically without manual intervention.

Why does custom domain setup require DNS verification steps?

Custom domain setup requires DNS verification to prevent misconfigurations and ensure domain ownership. This standardized flow validates DNS instructions before completing domain attachment, avoiding TLS provisioning delays.

How do I update DNS records for a custom domain attachment?

To update DNS records for a custom domain attachment, use create_domain to obtain the specific DNS instructions, configure those records with your DNS provider, then call update_domain to finalize the verification.

Does post-creation domain binding support automated TLS?

Yes, post-creation domain binding supports automated TLS. When you attach a generated subdomain to an existing app via add_application_domain, TLS is handled automatically through the standardized attachment flow.