Security audit
Security checks for vulnerabilities and agentic risk
This is a low-risk academic writing diagnosis skill made of Markdown guidance and examples, with no executable code or hidden data access.
Before installing, understand that this skill is narrowly focused on diagnosing Discussion structure and uses a mixed Chinese-English teaching style. Specify your preferred response language and treat its academic-writing feedback as guidance rather than a substitute for your advisor or journal requirements.
The description states the skill diagnoses Discussion sections in an "English psychology research paper," which is a natural-language constraint. Under the policy rule, forcing a specific language is reportable unless the skill offers a language choice or clearly documents a justified region/compliance limitation; neither is present here.
This markdown file describes when to use the example with phrases like 'Discussion 整体结构散乱' and '我的 Discussion 结构对不对', which are relatively broad and lack explicit scope limits or negative examples. The wording could overlap with many ordinary writing-help requests, increasing the chance of unintended invocation of this specific example.
The document is primarily written in Chinese and presents its guidance, section headings, and usage instructions in that language without offering an alternative language option or stating that the skill is region- or language-specific. This can violate a language/locale policy when users are not given a choice or explicit opt-in.
This markdown file presents its operational guidance and usage instructions primarily in Chinese, which can force a specific language on users without opt-in. The policy explicitly disallows language or locale constraints unless the skill offers user choice or clearly documents a justified regional limitation.
This markdown file presents core instructions in a mixed Chinese-English format, which can impose a language/locale expectation on users without explicitly offering an alternative. Under the policy rule, forcing or assuming a language without user opt-in can be a natural-language policy concern.
Most of the instructional content and usage guidance in the file is written in Chinese, which can amount to an implicit language constraint if the skill is surfaced to users without opt-in. The file does not indicate that users may choose another language or that the Chinese-only presentation is required for a documented region-specific purpose.
The content includes substantial Chinese headings and explanations alongside English technical phrases and quotations, but does not indicate whether the skill should respond in Chinese, English, or follow the user's preferred language. This can conflict with a language/locale policy that requires user choice rather than implicit language forcing.
The usage section says to cite this example when a user uploads methodological, tutorial, or tools-and-techniques papers, and gives a few example situations, but it does not define boundaries or negative examples. This can lead to overuse on adjacent paper types or unclear activation in mixed-methods cases.
This markdown file contains user-facing instructional content in Chinese, including headings, analysis, and usage guidance, but does not indicate that the user can choose another language or that the content is intentionally limited to a Chinese-speaking audience. Under the language/locale policy rule, forcing a specific language without opt-in is a natural-language policy concern.
