Security audit
Security checks for vulnerabilities and agentic risk
This looks like a local content archiver, but its instructions are too broad and vague about API keys, callbacks, and command use for a skill that can read, write, and execute commands.
Review this skill carefully before installing. It may be fine for saving articles, tweets, videos, and PDFs as local markdown snapshots, but only use it if you are comfortable with broad read/write/exec capability, local storage under ~/archive, and unclear API key and callback behavior. Avoid giving it sensitive URLs, private documents, or API keys unless you understand exactly where the data will be stored or sent.
The manifest advertises unrelated capabilities such as video/audio processing and SEO optimization in a skill that is presented as a local content archiver. This scope confusion can cause the agent to invoke the skill for unrelated tasks and grant it read/exec/write behavior outside the user's expected intent, increasing the chance of unintended file operations or network use.
The activation text is overly broad and inconsistent, covering unrelated domains like media editing and SEO. In an agent environment, this can cause inappropriate auto-selection of a skill that has write and exec privileges, leading to unnecessary local file creation, content capture, or command execution in contexts the user did not intend.
The description emphasizes content extraction but does not prominently warn that retrieved external content is written to local files by default. Users may supply sensitive URLs or text expecting transient processing, while the skill persists that data under the home directory, creating privacy and retention risk.
Supporting callback URLs alongside external content retrieval introduces outbound network transmission, but the skill does not clearly explain what data may be sent, to whom, and under what trust model. This can expose captured content, metadata, or processing results to third-party endpoints without sufficiently informed user consent.
Requiring an API key and implying external service use is not justified by the stated purpose of a free local archiving skill, especially when the toolset already includes read/write/exec. This creates unnecessary credential exposure and network transmission risk because users may provide secrets or permit outbound calls without understanding why they are needed.
The usage constraints narrowly state that media files are not stored and only descriptions/metadata are kept, but later feature documentation advertises generic file processing, API integration, and command execution capabilities. While not executable code, these statements pull in a broader operational intent that conflicts with the earlier limitation-focused description.
No suspicious patterns detected.
