T09 · Insecure Skill Coding Practices
- Location
scripts/export_prompts.py:168- Finding
Spreadsheet Formula Injection in Generated CSV Manifest
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent local prompt-generation workflow with one real CSV-export hardening issue users should understand before opening generated manifests in spreadsheets.
Reasonable to install for local storyboard prompt generation. Use trusted storyboard CSV inputs when possible, and avoid opening generated manifest.csv files in spreadsheet software unless formula-like cells have been sanitized; manifest.json is safer for exact data review. Confirm the target model and output language before batch generation.
scripts/export_prompts.py:168Spreadsheet Formula Injection in Generated CSV Manifest
Without declared permissions the skill's intent is opaque and cannot be validated.
The markdown explicitly states that Hailuo H3 and Runway prompts must be output in English. This is a natural-language locale constraint presented as a rule, but the file does not frame it as a user choice or opt-in, which can violate language/locale policy requirements.
Line L11 requires H3 outputs to be in English, and similar language mandates appear elsewhere in the document for other models. This is a natural-language locale policy concern because it forces a language choice based on model dialect rather than explicitly offering the user a choice or documenting a justified restriction.
The section beginning at L50 states that Runway uses English prompts and provides English-only prompting guidance. Without noting that this is an optional preference, user-selected setting, or unavoidable model limitation, the file imposes a language policy that could conflict with organizational expectations around user language choice.
The document title and all operational instructions are written in Chinese, and line L16 explicitly requires dialogue/voiceover to preserve the original language while the surrounding spec provides no option for users to choose another working language or locale. This can be a language-policy issue when a skill effectively forces Chinese as the specification and interaction language without opt-in or documented regional justification.
The documentation says certain model dialects must be written in Chinese while Runway uses short English sentences, which imposes locale/language constraints as part of the skill behavior. The README does not indicate that users can choose their preferred language or opt in to these language-specific defaults.
No suspicious patterns detected.