T09 · Insecure Skill Coding Practices
- Location
scripts/plan-a-demo.js:8- Finding
Hardcoded production identifiers can route employee data to an unintended Discord channel
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly aligned with employee reminder reporting, but its bundled scripts can post employee data to a real-looking default Discord channel with production-send automation.
Review this before installing in production. Replace all bundled spreadsheet, account, and Discord channel defaults with your own explicit configuration, use a test channel first, remove unnecessary Drive authorization, avoid broad .env sourcing where possible, and only enable scheduled prod-send after confirming the destination audience is approved for employee birthday and event data.
scripts/plan-a-demo.js:8Hardcoded production identifiers can route employee data to an unintended Discord channel
references/deployment.md:54Deployment instructions request unnecessary Google Drive authorization
references/deployment.md:28Documentation installs an unpinned global npm dependency
The declared description is specific: a Google Sheets-driven employee reminder and reporting workflow involving staff/event schemas, scheduled jobs, and chat routing. The provided code chunk does not implement or demonstrate any of that functionality directly. Instead, it is a thin launcher script that loads environment variables and runs an external Node script in 'prod-send' mode. Because the visible behavior is primarily orchestration of an unspecified production send operation, and there is no evidence in this chunk of Google Sheets access, reminder/report generation, or Telegram/Discord routing, the code does not accurately represent the declared purpose based on the supplied snippet.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Ví dụ flow:
gog auth credentials /path/to/client_secret.json
gog auth add your-google-account@gmail.com --services sheets,drive
The skill metadata does not declare any tool restrictions even though the workflow clearly involves environment access and outbound network actions to Google Sheets and chat platforms. Without explicit scope boundaries, an agent may invoke broader capabilities than intended, increasing the chance of secret exposure or unauthorized message sending during installation or execution.
The document provides commands that will send real messages to a live Discord channel using a bot token, but the warnings before those commands are weak and do not clearly foreground the external side effect at the point of execution. In an operational skill that reads real Google Sheets data and posts into team chats, this can cause unintended disclosure, spam, or accidental production actions during testing or migration.
The plan explicitly routes automated reports to a fixed Discord channel but does not mention any consent, audience restriction, or data-minimization control. Because the workflow processes employee birthdays and special events, this can expose internal personnel data to a broader chat audience than intended, especially if the channel membership is not tightly controlled.
The deployment guide instructs operators to configure Google auth and chat bot tokens but does not explicitly warn that these credentials must be kept out of committed files, chat transcripts, logs, and shared screenshots. In an ops-focused skill that routes messages to Telegram/Discord and uses Google access, omission of credential-handling guidance materially increases the chance of accidental secret exposure during setup or troubleshooting.
The document prescribes tab names and required column headers entirely in Vietnamese, including a suggested default tab name and all schema labels. Because no opt-in, alternative locale, or justification for a Vietnam-specific deployment context is provided, this appears to enforce a specific language/locale in natural-language instructions.
This markdown file contains operational instructions in Vietnamese (for example, 'Hỗ trợ hiện tại' and 'macOS là môi trường hiện tại đã test Plan A nhiều nhất') while other parts are in English. That imposes a language expectation on users without any stated opt-in, language selection, or justification for a locale-specific audience.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Scheduler
- use `launchd`
- example plist already bundled in scripts
## Notes
macOS là môi trường hiện tại đã test Plan A nhiều nhất.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Scheduler
- use `launchd`
- example plist already bundled in scripts
## Notes
macOS là môi trường hiện tại đã test Plan A nhiều nhất.
The headings and instructions from L03 onward are entirely in Vietnamese, which imposes a language choice on users without opt-in. Under the policy, language-specific guidance should either offer a choice or clearly document why the locale restriction is necessary.
This markdown mixes English headings with core operational instructions in Vietnamese, such as setup and scheduler guidance. Because the file does not state that the skill is intended only for Vietnamese-speaking users or offer an alternate language, it may violate language/locale policy requiring user choice or clear justification.
In send and prod-send modes, the script transmits employee birthdays, department information, event details, and optionally invalid-row details to a Discord channel without any interactive confirmation, recipient validation, or data-classification guardrail. In the context of an internal operations workflow, this can cause accidental disclosure of employee-related information to the wrong channel or broader audience, especially because channel IDs and tokens are environment-driven and the feature is designed for automated scheduled execution.
The script silently sources a local .env file with set -a, exporting all variables into the process environment without any notice or validation. In an agent-skill context, this is dangerous because it can implicitly pull in sensitive credentials or unsafe runtime settings from the local workstation, broadening what the downstream Node process can access and making behavior dependent on hidden local state.
The script directly invokes a production-send mode with no visible warning, dry-run default, or confirmation prompt. In a skill meant to handle reminders and chat routing, that makes accidental real-world delivery to production channels likely, which can leak employee data, spam internal communications, or trigger unintended operational actions.
The natural-language instructions, headings, and operational guidance are presented in Vietnamese only. Under the language/locale policy, forcing a single language without opt-in or justification can be a policy violation.
Natural-language policy requires flagging cases where a skill forces a specific language or locale without user opt-in. This file's operational instructions are entirely in Vietnamese and do not indicate that the skill is region-specific or that users may choose another language.
The natural-language instructions are presented almost entirely in Vietnamese, which effectively forces a specific language for operators reading the deployment guide. Under the stated policy, a fixed language is a concern unless the file offers user choice or clearly documents that the skill is intentionally region- or locale-specific.
The manifest describes an internal reminder/reporting workflow around Google Sheets and chat routing, but this launcher script imports all variables from a local .env file before execution. Reading arbitrary local environment configuration is not described in the manifest and introduces a broader capability than the business-purpose description suggests.