T08 · Insecure Dependencies
- Location
docs/QUICKSTART.md:11- Finding
Conflicting Package Identities and Unverified Installation Sources
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a prompt-only agent team, but conflicting package names and install sources make it easy to install the wrong skill.
Install only from the canonical ClawHub package after confirming the expected slug, version, and publisher. Avoid the manual Git clone instructions unless the repository and commit are independently verified, and review generated backend configs so sample database credentials are replaced before any staging or production use.
docs/QUICKSTART.md:11Conflicting Package Identities and Unverified Installation Sources
agents/engineering/backend-architect.md:211Predictable Hard-Coded Database Credentials in Reusable Deployment Template
This markdown file is written entirely in Chinese, including headings, status labels, plans, pricing, and contact sections, with no indication that other languages are supported or that Chinese is a justified locale-specific requirement. Under the policy for natural-language violations, forcing a specific language without user opt-in should be flagged.
The entire skill description and usage guidance are presented only in Chinese, with no indication that users may choose another language or that the skill is intended exclusively for a Chinese-speaking or region-specific audience. This creates a natural-language locale constraint without user opt-in, which matches the policy-violation criterion for language or locale restrictions.
The file consistently presents the skill name, description, usage instructions, workflow, and support content in Chinese, which effectively imposes a specific language on users. The policy allows locale constraints only when they are opt-in or clearly justified as region-specific, neither of which is stated here.
The file’s natural-language description and all operational content are written in Chinese, while also labeling the skill in English, which indicates a language choice is being imposed rather than explicitly offered as an option. Under the stated policy, a skill should not force a specific language or locale without user opt-in or a documented regional justification.
The manifest description and nearly all natural-language instructions are written in Chinese, presenting the skill as operating in a Chinese-language mode without any opt-in or alternative language option. Under the policy, a skill should not impose a specific language or locale unless it explicitly offers user choice or clearly documents a justified regional constraint.
This markdown skill file presents its description, role, mission, rules, and templates exclusively in Chinese. The policy requires flagging language or locale constraints when a skill forces a specific language without user opt-in, and no alternative language choice or justification is provided here.
This markdown skill appears to require Chinese comprehension throughout its description, role instructions, and templates. Under the policy, forcing a specific language without user opt-in or a documented justification is a natural-language policy violation.
The file’s natural-language content is predominantly in Chinese, including the skill description and all behavioral guidance, with no indication that users may choose another language. This can violate a language/locale policy when a skill implicitly constrains interaction language without opt-in or justification.
The file’s natural-language description and instructions are predominantly in Chinese, but there is no indication that users can opt into another language or that the skill is intentionally limited to a Chinese-speaking context. This can violate language/locale policy when a skill effectively forces one language without user choice.
The file’s natural-language description and section content are written in Chinese, and the skill identity is presented as a Chinese-language role without offering any language choice. This can violate language/locale policy expectations when users have not explicitly opted into Chinese or when no region-specific justification is documented.
The manifest description is entirely in Chinese and the document consistently defines the role, workflow, and deliverables in Chinese, with no indication that the user may choose another language. This is a natural-language locale policy concern because it imposes a specific language by default rather than offering an explicit language preference or opt-in.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
description: 电商平台 API
servers:
- url: https://api.example.com/v1
paths:
/products:
The description and nearly all instructional content are written in Chinese, indicating a fixed language expectation for the skill. There is no natural-language notice that the skill can adapt to other languages or that Chinese is required for a justified region-specific use case, which creates a language/locale policy concern.
This markdown skill consistently specifies its role, workflow, templates, and communication style in Chinese, and does not indicate that users may choose another language. Under the policy rule for language or locale constraints, this is a natural-language policy concern because it effectively forces a specific language without opt-in or justification.
The description and title are written in Chinese and present the skill as a Chinese-language experience, but there is no indication that users may choose another language or that the locale restriction is required for a region-specific purpose. This can violate language/locale policy when a skill implicitly forces a specific language without user opt-in.
The file’s natural-language content is presented entirely in Chinese, including the description and role instructions, with no indication that users can choose another language. This creates a language/locale policy concern because it imposes a specific language without opt-in or justification as a region-specific skill.
The manifest description and the body of the skill are written in Chinese, indicating the skill is intended to operate in a specific language. There is no statement offering the user a language choice or documenting a justified region-specific limitation, which conflicts with the language/locale policy criteria.
The manifest description and the skill's headings and role text are written in Chinese, which indicates a fixed language preference for the skill. The file does not state that the user can choose another language or opt in to Chinese, so it may violate language/locale policy requirements.
This markdown skill overwhelmingly specifies its role, rules, workflow, and templates in Chinese, which can force a specific language/locale on users. The file does not offer an opt-in language choice or explain that the skill is intentionally limited to a Chinese-speaking or region-specific context.
The file mixes an English skill name with a Chinese description and title, indicating the skill is defined to operate in Chinese by default. There is no opt-in, language selection, or justification that this is a region-specific skill, which can violate language/locale policy requirements.
The natural-language content in the description and body is presented in Chinese throughout the file, with no indication that the user can choose another language or that the locale restriction is intentional. This can violate language/locale policy when users are not given an explicit language option.
The manifest description and the main instructional content are written entirely in Chinese, presenting the skill as a Chinese-language strategist without offering a user language choice or documenting a justified locale restriction. This can violate language/locale policy when users are not given an opt-in or alternative language path.
The manifest description and all instructional content are written in Chinese, presenting the skill as a Chinese-language specialist experience without offering any user opt-in or alternative language choice. Under the stated policy, forcing a specific language without user choice is a natural-language policy violation unless the locale constraint is explicitly justified.
The file’s natural-language description and all operational guidance are written in Chinese, and there is no statement that the skill supports other languages or that Chinese is an opt-in preference. Under the policy, forcing a specific language without user choice is a locale/language policy violation unless the constraint is explicitly documented and justified.
The manifest description and title present the skill in Chinese, indicating a language-specific experience, but the file does not state that users can choose another language or that the skill is intentionally limited to a Chinese-speaking context. This creates a natural-language policy concern because the skill appears to impose a specific language without explicit user opt-in.
No suspicious patterns detected.