Security audit
Security checks for vulnerabilities and agentic risk
This is a descriptive privacy-readiness checklist skill with no executable code or hidden system access.
This appears safe to install as a planning aid. Treat its outputs as non-legal guidance, avoid pasting unnecessary personal data or customer records, and verify jurisdiction-specific compliance steps with qualified privacy counsel before acting.
Line L14 states that documentation is "English-first," which is a natural-language locale constraint. The file does not indicate that users can choose another language or that the constraint is justified by a region-specific requirement, so it conflicts with the language/locale policy guidance.
Lines L014-L015 state that the skill 'does not execute code, call APIs, access the network, scrape websites, submit forms, make purchases, send messages, or perform any external action.' However, later guidance explicitly tells users to generate cookie banners with Cookiebot and edit documents in Notion/Google Docs, which contradicts the stated no-external-action framing by operationalizing concrete third-party service usage. This is an intent/documentation contradiction rather than a mere omission.
The example prompt begins with "Help me compare two markets," which is a generic conversational phrase rather than a narrowly scoped invocation. In a markdown skill description, this can make activation cues less specific and increase the chance of unintended matching with ordinary user requests.
L132 asserts the skill remains purely descriptive with no network access or external side effects. Yet the example scenario at L146 recommends using online services such as Cookiebot, iubenda, and FreePrivacyPolicy, which conflicts with the strict framing that the skill is purely non-external in nature. The contradiction is in the documentation's claimed boundaries versus the prescribed behavior in example outputs.
The file is a markdown skill description, and these lines introduce a scenario entirely in Chinese. Under the policy rule, forcing or assuming a specific language without explicit user choice can be a locale/language policy issue, especially because the surrounding document does not explain that multilingual output is optional or user-selected.
The manifest specifies "language": "en", which imposes a single language setting. Under the policy, locale or language restrictions should either offer user choice or be clearly justified as region-specific, and neither is present here.
No suspicious patterns detected.
