Spaceship domains
Agent skills for managing domains via the Spaceship registrar API — works with Claude Code, Cursor, Copilot, Codex, and more
npx -y skills add BartWaardenburg/spaceship-skills --skill spaceship-domainsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Manages domains via the Spaceship registrar API — registers domains, configures DNS records, manages contacts and WHOIS privacy, transfers domains, sets up nameservers, and sells domains on SellerHub. Use when asked to "manage domains", "register a domain", "configure DNS", "add DNS records", "set up nameservers", "check domain availability", "transfer a domain", "sell a domain", "set up email DNS", "manage WHOIS privacy", or any Spaceship domain registrar operation. Requires the Spaceship MCP server to be configured.
SKILL.md
6.9 KB, ~1.5k tokens by cl100k_base, as published. Nobody here has run it
Spaceship Domain Management
Manages domains through 48 Spaceship MCP tools across 9 categories: domain lookup, domain info, domain settings, domain lifecycle, DNS management, DNS record creation, contacts & privacy, personal nameservers, and SellerHub marketplace.
When to Use
- Managing domains registered at Spaceship (DNS, settings, contacts, privacy)
- Registering, renewing, transferring, or restoring domains via Spaceship
- Configuring DNS records for domains using Spaceship nameservers
- Setting up email (Google Workspace, Microsoft 365) on Spaceship-managed domains
- Listing domains for sale on Spaceship SellerHub
- Checking domain availability and pricing through Spaceship
- Setting up vanity/glue nameservers for Spaceship domains
When NOT to Use
- Domains managed at other registrars (Cloudflare, GoDaddy, Namecheap, etc.)
- DNS hosted outside Spaceship (e.g. Cloudflare DNS, Route 53, Google Cloud DNS)
- General DNS troubleshooting unrelated to Spaceship
- Web hosting or server configuration
- SSL certificate management (use CAA records for authorization only)
- Email server setup beyond DNS records
Tool Loading
All Spaceship tools are deferred. Load them before use:
ToolSearch: "+spaceship <keyword>"
Examples: +spaceship dns, +spaceship domain, +spaceship contact, +spaceship sellerhub.
Tool Categories
| Category | Tools | Key Operations |
|---|---|---|
| Domain Lookup | check_domain_availability | Check availability + pricing for 1–20 domains |
| Domain Info | list_domains, get_domain | List/inspect domains in account |
| Domain Settings | set_auto_renew, set_transfer_lock, update_nameservers, get_auth_code | Configure domain settings |
| Domain Lifecycle | register_domain, renew_domain, restore_domain, transfer_domain, get_transfer_status, get_async_operation | Registration, renewal, transfer (all async + financial) |
| DNS Management | list_dns_records, save_dns_records, delete_dns_records, check_dns_alignment | Bulk DNS operations |
| DNS Creators | create_a_record, create_aaaa_record, create_cname_record, create_mx_record, create_txt_record, create_srv_record, create_ns_record, create_alias_record, create_caa_record, create_https_record, create_ptr_record, create_svcb_record, create_tlsa_record | Create individual DNS records by type |
| Contacts & Privacy | save_contact, get_contact, save_contact_attributes, get_contact_attributes, update_domain_contacts, set_privacy_level, set_email_protection | Contact profiles, WHOIS privacy |
| Personal NS | list_personal_nameservers, get_personal_nameserver, update_personal_nameserver, delete_personal_nameserver | Vanity nameservers (glue records) |
| SellerHub | list_sellerhub_domains, create_sellerhub_domain, get_sellerhub_domain, update_sellerhub_domain, delete_sellerhub_domain, create_checkout_link, get_verification_records | Domain marketplace |
References
- API Reference — complete parameter specs for all 48 tools
- Gotchas — common pitfalls, edge cases, and correct usage patterns
- Patterns — DNS recipes for Google Workspace, Microsoft 365, Vercel, Netlify, and more
Common Workflows
Check & Register a Domain
1. check_domain_availability({ domains: ["example.com"] })
→ Returns availability + pricing
2. save_contact({ firstName, lastName, email, address1, city, country, phone })
→ Returns { contactId }
3. register_domain({ domain: "example.com", contacts: { registrant: contactId } })
→ Returns { operationId } (async, financial — confirm with user first)
4. get_async_operation({ operationId })
→ Poll until status is "completed"
5. set_privacy_level({ domain, level: "high", userConsent: true })
6. set_transfer_lock({ domain, locked: true })
Configure DNS for a Website
1. list_dns_records({ domain: "example.com" })
→ See existing records
2. create_a_record({ domain, name: "@", address: "93.184.216.34" })
3. create_cname_record({ domain, name: "www", cname: "example.com" })
4. check_dns_alignment({ domain, expectedRecords: [...] })
→ Verify all records are correct
For email, CDN, and hosting provider DNS patterns, see references/patterns.md.
Transfer a Domain to Spaceship
1. save_contact({ ... })
→ Create contact profile first
2. transfer_domain({ domain, authCode: "EPP-CODE", contacts: { registrant: contactId } })
→ Returns { operationId } (async, financial — confirm with user first)
3. get_transfer_status({ domain })
→ Check transfer progress
4. get_async_operation({ operationId })
→ Poll until complete
Sell a Domain on SellerHub
1. create_sellerhub_domain({ domain, binPrice: { amount: "5000", currency: "USD" }, binPriceEnabled: true })
2. get_verification_records()
→ Get DNS verification records (account-level)
3. create_txt_record({ domain, name, value })
→ Add the verification TXT record
4. create_checkout_link({ domain, type: "buyNow" })
→ Returns shareable purchase URL
Key Gotchas
- Async + financial:
register_domain,renew_domain,restore_domain,transfer_domainreturn{ operationId }— always confirm with user before executing, then poll withget_async_operation - DNS creators replace: Each
create_*_recordreplaces ALL existing records with the same name+type - Privacy requires consent:
set_privacy_levelneeds{ userConsent: true }— mandatory - Rate limits: 5 requests per 300 seconds per domain for write endpoints
For the full list with examples, see references/gotchas.md.
Instructions
- Identify the action from the user's request
- Load required tools via
ToolSearchwith+spaceship <keyword> - Confirm destructive/financial operations before executing (register, renew, restore, transfer, delete DNS)
- Follow the appropriate workflow above, or check references/patterns.md for service-specific DNS recipes
- Poll async operations for lifecycle operations
- Report results clearly — show domain status, DNS records, pricing, or operation results in readable format
If $ARGUMENTS is provided, interpret it as the domain name or action to perform.
What ships with it: 3 files
41.9 KB alongside SKILL.md
references/
- api-reference.md16.4 KB
- gotchas.md10.6 KB
- patterns.md14.9 KB
Gives 0 of the 12 instructions most mcp tooling skills give in ~1.5k tokens
Counted across 638 of the 750 authors here whose files we hold, read 2026-08-07
- Create ten complex or independent read-only evaluation questionsin 69 of 638, across 15 files
- Test servers using MCP Inspectorin 61 of 638, across 19 files
- Provide actionable error messages with specific next stepsin 54 of 638, across 12 files
- Prioritize comprehensive API coverage over specific workflows or workflow toolsin 54 of 638, across 12 files
- Use TypeScript and Streamable HTTP for remote servers or clientsin 54 of 638, across 8 files
- Define structured output schemas where possiblein 50 of 638, across 8 files
- Use Zod or Pydantic for input schemasin 47 of 638, across 5 files
- Fetch MCP specification pages with markdown suffixin 46 of 638, across 4 files
- Load framework documentation using WebFetchin 45 of 638, across 3 files
- Verify each evaluation answer independentlyin 45 of 638, across 3 files
- Implement API client with authentication and paginationin 45 of 638, across 3 files
- Define input schemas with validationin 27 of 638, across 9 files
Said here and by no other author read
- identify the requested action
- load required spaceship tools via toolsearch
- follow the appropriate workflow
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.