ClawHub
Back to skill

Security audit

Postgres Job Queue

Security checks for vulnerabilities and agentic risk

Overview

This skill is a markdown guide for building a Postgres-backed job queue, with no hidden files or automatic execution behavior found.

Install only if you want an agent to provide Postgres job-queue design guidance. Review and adapt the SQL before running it against any real database, preferably in a dedicated schema or test environment first.

SkillSpector

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

Vague Triggers

High
Confidence
90% confidence
Finding
The trigger keywords are extremely broad terms such as 'based', 'priority', 'job', 'queue', and 'postgres', which are likely to appear in ordinary conversation and unrelated prompts. This can cause unintended skill activation, increasing the chance that the agent injects database-queue guidance or associated execution behavior into contexts where the user did not request it.

Vague Triggers

High
Confidence
89% confidence
Finding
The repeated trigger section again uses ambiguous activation terms that overlap heavily with generic technical discussion. Repetition of broad triggers increases the likelihood of accidental routing to this skill, which is more concerning here because the skill advertises partial exec/command-line usage and operational database patterns.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
The skill declares 'MD+execute' capability and states that some functions require exec command-line ability, but it does not clearly bound what commands may be run or warn about system-impacting actions. In an agent ecosystem, ambiguous execution capability can lead users or orchestrators to authorize commands that alter the local system or production infrastructure without adequate safeguards.

Static analysis

No suspicious patterns detected.