ClawHub
Back to skill

Security audit

The Pareto Principle (80/20)

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Markdown-only Pareto analysis coaching skill with disclosed limits and no executable or privileged behavior.

This skill is appropriate if you want an agent to guide prioritization using Pareto analysis. Users should still verify data, avoid using it to ignore safety-critical or regulatory obligations, and treat the linked external sources as references rather than automatic runtime actions.

A.I.G

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

SkillSpector

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

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
80% confidence
Finding

Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Content

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

md
| [D] Asserting "80/20" without measuring | The principle is a hypothesis until tested. Measure the actual distribution before acting on it. |
| [D] Applying 80/20 across different outputs as if they're the same | The 20% driving revenue ≠ the 20% driving support load. Pareto is *per output*. |
| [D] Cutting the trivial many automatically | Sometimes the long-tail customers, features, or markets are strategically essential. The "cut" decision needs to be deliberate, not default. |
| [D] Pareto in safety-critical contexts without caveat | Rare-event-catastrophic domains (security, fraud, aerospace) invert the calculus. Standard 80/20 can be actively dangerous. |
| [D] Confusing ratio with elbow | The "elbow" of the curve is where you cut — not always at 80/20. Look at the actual curve. |
| [D] Applying once, treating as eternal | The vital few rotates. Today's vital few becomes tomorrow's trivial many as the system changes. |
| [D] Using Pareto as rhetoric, not data | "By the 80/20 rule, we should…" without measurement is folk reasoning. Run the analysis. |

Static analysis

No suspicious patterns detected.