Security audit
Security checks for vulnerabilities and agentic risk
This DNS lookup skill is mostly a local dig wrapper, but its instructions are materially overbroad and internally inconsistent for an exec-enabled skill.
Review this before installing: use it only for DNS lookup tasks, be aware that DNS queries can reveal domain names to resolvers, and do not let the broad database, coding, file-processing, or API-integration wording expand its authority beyond dig-based DNS diagnostics.
The manifest description mixes a DNS lookup tool with unrelated database/SQL usage guidance, which can cause the agent to invoke this skill in the wrong context. In an agentic system with exec permission, misleading routing metadata is security-relevant because it broadens activation scope and may trigger command execution for tasks the skill was never designed to handle.
The skill description uses overly broad and inconsistent invocation guidance, including unrelated domains, which weakens routing precision. For an exec-capable skill, ambiguous trigger text increases the likelihood of accidental or inappropriate execution, expanding attack surface and creating opportunities for misuse.
The documentation does not warn that DNS lookups disclose queried domains and potentially internal hostnames to external DNS resolvers. In enterprise or sensitive environments, this can leak operational details, customer domains, or unreleased infrastructure names through routine use of the skill.
The capability coverage section lists vague keyword-style triggers without meaningful constraints, including unrelated terms like code generation and deployment. Such broad trigger language can cause the agent to select this skill for loosely related requests, which is dangerous because the skill has exec access and performs external network queries.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
CentOS/RHEL/Fedora：
sudo dnf install bind-utils
Ubuntu/Debian：
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
CentOS/RHEL/Fedora：
sudo dnf install bind-utils
Ubuntu/Debian：
The FAQ states the free edition supports only single-domain queries, yet the rest of the document presents generic dig command usage including ANY queries, multiple record types, alternate resolvers, and broad '核心功能' language with no mechanism or instruction enforcing edition limits. This creates intent ambiguity about what the skill actually allows versus what the documentation claims is restricted.
The security section discusses API keys and HTTPS even though the skill is described as a local dig-based command with no API usage. Contradictory security guidance can mislead operators about the actual trust boundary, causing them to overlook the real risks of shell command construction and external DNS data disclosure.
The later core-function sections advertise generic file processing and external API integration capabilities that are not justified by a DNS lookup skill. Overstated capabilities can cause over-broad trust and invocation, increasing the chance that an agent grants this exec-enabled skill tasks outside its safe design scope.