T09 · Insecure Skill Coding Practices
- Location
.- Finding
Unvalidated API Base URL Can Disclose Bearer Credentials and Calendar Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Claw Calendar API helper, with no evidence of hidden execution, persistence, or malicious behavior, though users should treat its API URL and key as sensitive.
Install only if you intend to use Claw Calendar and are comfortable giving the skill a Claw Calendar API key. Keep CLAW_CALENDAR_API_URL unset unless you deliberately use a trusted custom deployment, and never point it at an untrusted or plaintext HTTP server because the API key and calendar data will be sent there.
.Unvalidated API Base URL Can Disclose Bearer Credentials 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` | 在日历中创建新事件 |
This script performs authenticated POST requests to an external calendar service, yet the corresponding network capability is reported as undeclared. In the context of agent skills, hidden network access is risky because it allows external communication beyond the permission model, which can facilitate covert data transfer, remote command dependence, or unreviewed side effects such as creating or modifying remote resources.
This script performs authenticated POST requests to an external calendar service, yet the corresponding network capability is reported as undeclared. In the context of agent skills, hidden network access is risky because it allows external communication beyond the permission model, which can facilitate covert data transfer, remote command dependence, or unreviewed side effects such as creating or modifying remote resources.
The file's comments and runtime messages are entirely in Chinese, including usage and error output. This imposes a specific language on all users without opt-in, which matches the policy-violation category for language or locale constraints.
The code hard-codes the locale 'zh-CN' in date formatting and all user-facing messages are written in Chinese, which enforces a specific language/locale for all users. The policy allows locale constraints only when users can opt in or when the restriction is clearly documented and justified, neither of which is present in this file.
The manifest-style descriptions are presented in fixed Chinese/English wording, including a primary Chinese description, but there is no statement that the skill will adapt to the user's preferred language or ask for language preference. This can violate a language/locale policy when a skill appears to impose a default language experience without explicit opt-in.
This code file contains natural-language strings and usage text exclusively in Chinese, including the top-level description and CLI guidance. 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.
This code hard-codes the locale 'zh-CN' for date formatting, which is a natural-language/locale policy concern under the rule for all file types. The file does not provide any opt-in, configuration, or documentation indicating that Chinese-only output is required for a region-specific purpose.