domain name generator
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is a coherent instruction-only domain naming skill that uses the disclosed DomainKits MCP/API, with ordinary privacy and account-key considerations.
This skill appears safe to install if you are comfortable connecting DomainKits. Before using it, understand that domain ideas and project descriptions used for searches may go to DomainKits, keep your API key private, and only enable domain monitoring when you deliberately want ongoing tracking.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If configured, DomainKits queries may run using the user's API key and account quota or permissions.
The skill can use a user-provided DomainKits API key for higher limits. This is disclosed and purpose-aligned, but it gives the skill access under the user's DomainKits account.
"headers": { "X-API-Key": "$env:DOMAINKITS_API_KEY" }Use a DomainKits key you trust, avoid sharing it outside the intended connector configuration, and review any account limits or scopes available from DomainKits.
Potential business names, project concepts, or domain candidates may be handled by the DomainKits service during availability and related checks.
The skill depends on an external MCP provider for domain intelligence, so project descriptions, keywords, or candidate domains used with those tools may be sent to DomainKits.
"baseUrl": "https://api.domainkits.com/v1/mcp"
Do not use sensitive unreleased brand ideas with the connector unless you are comfortable with DomainKits receiving those queries.
If used, the skill may set up ongoing monitoring for a target domain through DomainKits.
The skill discloses an optional monitoring capability that can persist beyond a single query. It is described as user-driven and aligned with domain tracking.
Optional follow-up tools (user-driven): ... `monitor` — Set up expiry monitoring for a target domain
Only enable monitoring for domains you intentionally want tracked, and confirm how to disable it if you no longer need it.