Domainion Ops

What to consider before installing and using this skill: - Source verification: The skill has no homepage and an unknown source. Prefer skills from known authors or with a verifiable homepage. - Metadata mismatch: The registry declares no required env vars or binaries, but SKILL.md expects multiple API keys and CLI tools (curl, dig, xmllint, python3, grep). Confirm with the publisher or platform how secrets and required system tools are handled before use. - Secrets handling: SKILL.md suggests storing provider API keys in environment variables or in ~/.domainion (a plaintext file). Do not store long-lived credentials in plaintext if you can avoid it — use your platform's secret storage, short-lived or least-privilege API keys, or sandbox/test accounts. Only provide keys at the moment of an interactive operation if possible. - Namecheap IP whitelist: Namecheap requires a whitelisted client IP. The skill suggests using ifconfig.me to detect your IP — that makes an external request and reveals your public IP to that service. If you must use Namecheap, prefer a controlled method to determine IP (your corporate NAT address, an internal check) rather than a public probe. - Required tools: The skill's examples depend on command-line tools (curl, dig, grep, xmllint, python3). Ensure your agent runtime/environment has those tools and understand that the agent may execute network-facing commands. - Minimizing blast radius: Create and use limited-scope API keys where possible (sandbox/test keys, readonly keys for checks). Avoid giving full account keys unless absolutely needed (e.g., purchases). Monitor and revoke keys after use if feasible. - Supervision and prompts: The skill's instructions say to prompt for creds if missing. Prefer interactive invocation only (do not enable automatic/autonomous invocation for this skill) and confirm destructive actions (nameserver changes, full zone replaces) each time. - Questions to ask the publisher/platform before installing: Why metadata omits required env vars and binaries? Will the platform treat the listed provider env names as secrets and encrypt/store them? Can the skill be limited to interactive invocation only? Is there an official maintainer or homepage for support? Given the coherence of the API examples but the metadata mismatches and weak secret-storage guidance, proceed only after clarifying the above points, using limited/sandbox credentials, and avoiding storing secrets in plaintext.