Back to skill

Security audit

PPT Rescue Kit / PPT急救工具箱

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed PowerPoint-building workflow that uses JishuDB persistence and local output with clear approval, scoping, and retry safeguards.

Install this only if you are comfortable with the agent saving deck drafts, sources, citations, and revision records into an approved JishuDB knowledge base. Confirm the selected KB, retained sources, and output folder before allowing write access.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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 (1)

Unbounded Resource Access

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.

Content

Scanner excerpt · SKILL.md (reported line 224)May include surrounding context.

md
content; replay URL/preparation only with identical supported keys and
   arguments. After an identified failure is repaired and retry is approved,
   use `kb_retry_job({kbId, jobId})` for the existing failed/cancelled job.
   Do not rotate identities, repeatedly upload, delete evidence, or retry
   indefinitely. Surface sanitized error codes, not credentials.

### Completion and handoff

Static analysis

No suspicious patterns detected.