Back to skill

Security audit

discussion-grammar-diagnosis

Security checks for vulnerabilities and agentic risk

Overview

This is a low-risk writing diagnostic skill that only provides grammar analysis guidance for academic Discussion sections.

Safe to install for its stated purpose. Be aware that the generic "grammar check" trigger may route ordinary grammar requests to this specialized Discussion-section skill, and much of the reference material is written in Chinese with English examples.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger list includes the generic phrase "grammar check," which is broad enough to match many unrelated user requests and may cause this skill to activate outside its intended scope. Over-broad activation can route users into the wrong skill, creating prompt-routing confusion, reduced reliability, and possible interference with more appropriate skills.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrase "grammar check" is broad and likely to activate on many generic user requests unrelated to this specific Discussion-section diagnostic skill. Over-broad activation can cause unintended routing, inappropriate tool invocation, or interference with other skills, even though the skill itself appears low-risk and non-code-executing.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The document mixes English examples with Chinese headings, labels, and usage instructions throughout, effectively constraining the skill artifact to Chinese. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale limitation is explicitly justified, which is not stated here.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

This markdown file contains user-facing instructions in a mixed Chinese/English format, but it does not indicate that the user can choose a preferred language or that the checklist is intentionally limited to a bilingual audience. Under the policy rule for language or locale constraints, forcing or assuming a language presentation without opt-in can be a natural-language policy issue.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The usage section describes when to cite this example using broad natural-language conditions like '出现以下情况时' and question-style examples, but it does not define clear trigger boundaries or exclusions. Without explicit constraints or negative examples, the skill could be invoked for loosely related grammar discussions rather than this specific tense-switch case.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This markdown file presents the rubric as '官方评分标准' under a bilingual heading but the operational sections are written in Chinese, with no indication that users may choose another language. Under the policy, forcing a specific language without user opt-in is a natural-language policy concern unless the locale restriction is explicitly justified.

Content

No source excerpt is available for this finding.