T09 · Insecure Skill Coding Practices
- Location
SKILL.md:256- Finding
RSS Feeds Retrieved Over Plaintext HTTP
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This RSS news skill is not malware, but it needs review because its command-execution guidance and network use are paired with mismatched triggers and inconsistent documentation.
Install only if you are comfortable with an agent making outbound requests to listed news RSS feeds and running local shell/Python commands. Treat retrieved feed text and links as untrusted, prefer HTTPS feeds, and avoid providing API keys or callback URLs because this free artifact does not clearly require or implement them.
SKILL.md:256RSS Feeds Retrieved Over Plaintext HTTP
The trigger condition is overly broad and mismatched to the tool’s purpose, instructing use for generic writing and content-generation scenarios. In a skill with exec capability and outbound HTTP behavior, imprecise routing materially increases the risk of unintended execution, data exposure, and user confusion about why the tool was invoked.
The trigger conditions say the skill should be used for marketing copy, title optimization, and content creation, which is unrelated to an RSS news fetcher. This is especially risky in an agent setting because broad, mismatched triggers can cause the skill to activate in unrelated conversations and execute outbound network activity or local commands unexpectedly.
The file says the free version requires no API key, but the known limitations section later says an API key is required. Contradictions about authentication and prerequisites are security-relevant because they can cause operators to inject unnecessary secrets into the skill workflow or mis-handle credential storage for a tool that should not need them.
The display name and the surrounding documentation are presented in Chinese, with no indication that users may choose another language or locale. Under the stated policy, forcing a specific language without opt-in can be a natural-language policy violation unless clearly justified.
The description does not clearly warn users that the skill performs outbound HTTP requests to third-party news sources. Missing disclosure of network side effects is security-relevant because users and agents may invoke the skill without understanding that it will contact external services, potentially leaking metadata such as IP address, timing, and requested topics.
The document claims support for create/query/export operations, but the described functionality is only RSS retrieval. Overstated capabilities can mislead an agent into invoking the skill in unintended contexts, which is dangerous because execution-enabled skills may be granted broader trust or permissions than their real purpose warrants.
The skill documents a callback_url parameter and callback-style processing, but the rest of the file only describes a local CLI RSS fetcher. This mismatch can cause an agent or integrator to send data to an assumed callback endpoint or expose workflow assumptions that do not actually exist, creating confusion around data flow and possible SSRF-style misuse if later implemented unsafely.
Repeated claims of create/query/export support conflict with the free-version limitations and examples, indicating inconsistent and unreliable security-relevant documentation. In agent ecosystems, contradictory docs can lead to unsafe invocation, incorrect routing, or over-privileged execution because the platform cannot accurately infer what the skill does.
The capability coverage keywords are excessively broad and vague, making the skill appear applicable to many loosely related prompts. Broad matching is dangerous in agent environments because it can increase accidental activation frequency and push a networked execution skill into contexts where its behavior is unexpected or unnecessary.