weekly-ops-review

• Outcome: Pass
• Latest audit: Sep 12, 2026 · 12:34 AM UTC
• Version: 1.0.0

Overview

This skill is a coherent weekly review helper with a small local draft-generating script and no evidence of hidden networking, credential access, persistence, or destructive behavior.

Installers should understand that the skill is meant to organize materials they provide into a weekly review. If using the helper script, run it on intentional inputs and specify an output path you are comfortable creating or overwriting. Consider narrowing trigger phrases in deployment environments that auto-activate skills from ordinary natural language.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (6)

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger examples include broad natural-language phrases such as 'weekly review' and 'next week priorities' that are common in ordinary user requests. In agent/router systems, overly generic triggers can cause unintended activation of this skill on unrelated prompts, leading to misrouting, confusing behavior, or unnecessary access to user-provided notes and files.

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 89% confidence
• Finding: The skill references a local script that can produce structured files and the static analysis indicates file-write capability, but the manifest does not declare any tool scope such as permissions or allowed-tools. This creates a mismatch between documented capability boundaries and actual behavior, which can lead to unintended file creation or modification without clear operator review.

Natural-Language Policy Violations

Medium

• Confidence: 85% confidence
• Finding: The trigger phrase list mixes English and Chinese phrases, but the document does not explain whether the skill is intended for a Chinese-speaking context or offer any user opt-in for language/locale handling. Under the policy rule, forcing or assuming a specific language without explicit choice or justification is a natural-language policy concern.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger phrase at line 8, "整理这周做了什么" ('organize what was done this week'), is broad natural language that could easily overlap with ordinary user requests outside the intended skill boundary. This can cause unintended invocation or routing confusion, especially in systems that select skills from loose semantic matches rather than explicit user choice.

Natural-Language Policy Violations

Medium

• Confidence: 94% confidence
• Finding: The smoke-test instructions and acceptance criteria are written entirely in Chinese, which imposes a specific language on users or reviewers without any opt-in or stated regional requirement. Under the policy, language constraints should either be optional for the user or clearly justified as region-specific.

Natural-Language Policy Violations

Low

• Confidence: 78% confidence
• Finding: The file presents core instructions and user-facing content in a mixed Chinese/English format, but does not state whether users may choose their preferred language or locale. This can be a policy concern when a skill appears to impose a language style without user opt-in.

Static analysis

No suspicious patterns detected.