Back to skill

Security audit

Legal Contract Review Playbook

Security checks for vulnerabilities and agentic risk

Overview

This is a document-only contract review workflow skill with clear legal disclaimers and no code execution, network access, credentials, or persistence.

Before using it, treat outputs as planning aids only and have qualified counsel verify jurisdiction-specific law, deadlines, confidentiality duties, citations, and legal strategy. Avoid pasting sensitive contract material unless your environment is approved for that data.

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

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The front matter sets language: en, and the acceptance criteria later require the documentation to be 'English-first'. This creates a language preference constraint without explaining that users may choose another language or that the limitation is required for a justified region-specific purpose.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The phrase 'SKILL.md and README.md are English-first' imposes a default language policy. Although the file includes a Chinese-language scenario, it does not explicitly offer multilingual support or user opt-in for language selection, so the wording may conflict with organizational expectations around user language choice.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The manifest sets the skill language to "en", which is a natural-language locale constraint. Under the policy, locale restrictions should either offer user choice/opt-in or be clearly documented and justified; this file does not provide that context.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The trigger section uses general phrases such as "contract review" and "agreement checklist" without narrowing context or giving exclusion conditions. In a markdown skill description, this can create ambiguous activation because these phrases are common requests and the file does not clarify when the skill should or should not be invoked.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.