T09 · Insecure Skill Coding Practices
- Location
scripts/create-calendar.js:6- Finding
Unrestricted API endpoint configuration can disclose the Bearer credential and calendar data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it says, but its configurable API endpoint can receive the user's calendar API key despite documentation saying the key only goes to the official service.
Install only if you trust the Claw Calendar service and can protect the API key. Do not set CLAW_CALENDAR_API_URL unless it is a trusted HTTPS endpoint, because the scripts will send the API key and calendar data there. Treat created events, reminders, and subscription URLs as external account changes that may sync to devices.
scripts/create-calendar.js:6Unrestricted API endpoint configuration can disclose the Bearer credential and calendar data
Referenced artifact was not completely inspected
| `scripts/create-event.js` | 在日历中创建新事件 |
Referenced artifact was not completely inspected
| `scripts/create-event.js` | 在日历中创建新事件 |
Referenced artifact was not completely inspected
| `scripts/create-event.js` | 在日历中创建新事件 |
The code sends authenticated requests to a remote endpoint using a bearer token from an environment variable, yet static analysis indicates network capability is undeclared. In a skill ecosystem, undeclared network egress is dangerous because it can enable data exfiltration or unauthorized external communication outside the permissions users and reviewers expect.
The code sends authenticated requests to a remote endpoint using a bearer token from an environment variable, yet static analysis indicates network capability is undeclared. In a skill ecosystem, undeclared network egress is dangerous because it can enable data exfiltration or unauthorized external communication outside the permissions users and reviewers expect.
The markdown explicitly tells users to export CLAW_CALENDAR_API_KEY, but it does not warn that this value is a secret credential that should be protected and not committed, logged, or shared. Because this file is a markdown skill description, omission of a privacy/security warning around credential handling fits the missing user warnings category.
The skill documents commands that create calendars, add events, and enable reminders, but it does not clearly warn that these actions modify external calendar data and may propagate to connected devices through subscription/sync behavior. This can cause unintended writes, reminders, and data exposure across a user's phone or desktop calendars if the user or agent invokes the skill without explicit awareness of those side effects.
This JavaScript file contains natural-language comments and error/output strings exclusively in Chinese, including usage guidance and failure messages. Under the policy rule for language/locale, this is a violation because the skill does not offer user opt-in or document that it is intentionally limited to a Chinese-speaking or region-specific context.
The script explicitly formats dates with the 'zh-CN' locale and all user-facing messages are in Chinese, which imposes a specific language/locale on users. Under the policy, this is a natural-language locale violation unless the skill offers user opt-in or clearly documents a justified region-specific constraint.
This code file contains user-facing natural-language text entirely in Chinese, including the top-level usage description and runtime messages. Under the policy rule, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly documented and justified, which is not present here.
The code hard-codes the locale 'zh-CN' for date formatting, which forces a specific language/locale in user-visible output. The file does not offer an opt-in, fallback, or configuration mechanism, and no region-specific justification is documented here.