Security audit
Security checks for vulnerabilities and agentic risk
This is a Spanish-language markdown guide for data and API architecture that does not include code execution, credential handling, network access, or persistence.
Install this if you want a Spanish technical assistant for category-theory-based data modeling, schema/API generation, and architecture audits. Users who need English or another language should be aware that the skill explicitly directs Spanish output.
La línea L27 indica explícitamente 'Escribir en espanol tecnico', lo que fuerza una política de idioma en la salida. Según la regla SQP-3, esto constituye una violación de política lingüística cuando no se ofrece opt-in ni alternativa de idioma al usuario.
The document's operative instructions are written in Spanish (for example, 'Usar este archivo...' and subsequent imperative guidance), which imposes a language requirement on users of the skill artifact. The policy allows locale constraints only when user choice is offered or the regional limitation is clearly justified, neither of which appears here.
The file's operational instruction is written as a directive in Spanish ('Usar este archivo...') and the rest of the taxonomy is entirely Spanish, which effectively imposes a language choice on users or downstream agents. The policy allows locale constraints only when users can opt in or when the restriction is clearly documented and justified, neither of which appears here.
The entire skill is written in Spanish and provides instructions only in that language. Under the policy, forcing a specific language without opt-in or a documented regional justification is a natural-language policy violation.
The file's operative instructions are written in Spanish (for example, 'Usar este mapa para despachar la solicitud al playbook minimo'), and the rest of the routing guidance is likewise language-specific. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified, which is not present here.
The file’s instructional content and operational guidance are presented entirely in Spanish, which can impose a language constraint on users without opt-in. The stated policy flags language or locale restrictions unless the skill offers a choice or clearly justifies the constraint as region-specific.
The file content is entirely in Spanish and does not offer a language-selection mechanism or document a locale-specific requirement. This can exclude or mislead users who do not understand Spanish, causing incorrect use of architectural guidance and weakening safe operation through misunderstanding rather than direct code execution risk.
This markdown file is written entirely as imperative guidance in Spanish (for example, 'Usar este mapa', 'No editar', 'Empezar siempre'), which effectively imposes a language/locale on users of the skill. The policy allows locale constraints only when justified or when users are given a choice, neither of which appears here.
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
The document states that the agent is the "Arquitecto Categórico" and presents the file as its internal architecture, embedding a Spanish-language identity/name into the skill behavior without offering any user language choice or opt-in. This can violate language/locale policy when a skill constrains interaction style or language implicitly rather than letting the user choose.
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
The scope-determination section uses broad trigger logic such as 'Combined? → Execute all applicable,' which can cause the skill to activate on loosely related requests and expand into multiple audit modes without clear user intent. In an agent setting, ambiguous activation criteria can lead to overreach, misuse of the skill in the wrong context, or unintended processing of sensitive schemas, logs, or provenance data.
Suspicious Unicode normalization or mixed-script content
Suspicious Unicode normalization or mixed-script content
This markdown file contains user-facing instructions exclusively in Spanish, and there is no indication that the user can opt into another language or that the skill is intentionally restricted to a Spanish-speaking audience. Per the policy, forcing a specific language without user opt-in is a natural-language policy violation.
This markdown file presents all operative documentation in Spanish and does not indicate that users may choose another language. Per the policy criteria, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is documented and justified.
No suspicious patterns detected.
