Back to skill

Security audit

System Continuity Check

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only workflow review skill with broad activation wording but no hidden code, data access, or automatic system changes.

Install this only if you want a Chinese-language checklist that may activate during system, workflow, or automation design discussions. Treat recommendations about autostart, services, and monitoring as design prompts requiring your explicit approval before implementing them.

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 (5)

Vague Triggers

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger keywords are extremely broad and include common terms like development, design, system, workflow, and component, which can cause the skill to activate in many unrelated conversations. Over-broad activation can hijack normal assistant behavior, inject irrelevant guidance, and create prompt-routing confusion that degrades reliability and may interfere with safer or more appropriate skills.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The entire skill is authored in Chinese and does not indicate that language selection is optional or user-driven. Under the stated policy, a fixed language without user opt-in can be a locale-policy issue unless the restriction is explicitly justified.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The activation rule says the skill auto-activates when users describe system design, workflow development, or automation processes, but it does not define clear boundaries for when it should stay inactive. This ambiguity increases the chance of unintended invocation, causing the skill to override contextually better behavior and produce unsolicited operational advice.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The file title and all instructional content are written exclusively in Chinese, and there is no indication that users may choose another language or that the template is intended only for a Chinese-language context. This can violate a language/locale policy when a skill imposes a specific language without opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The entire skill content is written in Chinese and does not indicate that users may choose another language or that the skill is intentionally limited to a Chinese-speaking or region-specific context. Under the policy, forcing a specific language without opt-in is a natural-language locale violation.

Content

No source excerpt is available for this finding.