Security audit
Security checks for vulnerabilities and agentic risk
This Spanish ad-script skill is purpose-aligned and contains no executable payload, but it does save generated scripts locally and may use business context files.
Install this only if you want a Spanish-language paid-ad scripting workflow and are comfortable with it using your business brief/context and saving generated campaign scripts locally. Review the output directory mismatch before relying on automated file organization.
Referenced artifact was not completely inspected
Las 10 categorías son las 7 clásicas + 3 modernas. Ver `references/hooks-10-tipos.md` para plantillas, ejemplos y casos de uso por nivel de consciencia.
Referenced artifact was not completely inspected
**Profundidad de cada elemento:** plantillas, ejemplos F100K, reparto en el tiempo y errores comunes en `references/meat-4-bloques.md`.
This instruction mandates a fixed language variety and forbids alternative regional forms, which is a natural-language policy violation under SQP-3 when no user choice or opt-in is provided. The file does not indicate that this locale restriction is optional or justified by a region-specific compliance need.
The skill instructs the agent to create directories and write files to the filesystem without requiring explicit user confirmation at the point of action. In an agent environment, silent file writes can violate user expectations, cause unintended persistence of sensitive business data, or be chained with other skills to exfiltrate or stage data for later use.
The title and core instruction require a fixed Spanish output format for all deliveries of the skill. This is a natural-language locale constraint, and the file does not indicate user opt-in, language selection, or a documented region-specific justification.
This markdown file is entirely framed as prescriptive guidance in Spanish, with no indication that users may choose another language or locale. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale constraint is clearly documented and justified, which is not present here.
The OUTPUT section says to save files under guiones/ads/YYYY-MM-DD_[nombre-campaña].md (L254-L258), but immediately after says to create guiones-propios/ if it does not exist (L260). These instructions conflict about where outputs belong, creating an intent/documentation mismatch within the skill file itself.
The manifest describes a skill for scripting paid ads, but this file says the result is pasted into a .md file stored in guiones/ads/. Persisting output to files is an implementation behavior beyond the manifest's purely content-generation description, even if low risk.
Line L165 states that an example markdown file is created if it does not exist. The manifest focuses on generating ad scripts and variant structures, not creating reference/example files on disk.
This markdown file contains user-facing instructional content exclusively in Spanish and does not indicate that the skill is intended only for Spanish-speaking users or provide an opt-in language choice. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation.
SQP-3 applies to all file types and includes language or locale policy violations. This file presents all instructions in Spanish only, with no indication that the skill is region-specific or that users may opt into another language, which can conflict with organizational language-choice expectations.
No suspicious patterns detected.