Back to skill

Security audit

TOSR Publish Then Update Test

Security checks for vulnerabilities and agentic risk

Overview

This is a small markdown-only integration-test skill that clearly describes creating, updating, inspecting, and deleting a test skill through the real ClawHub API.

Install or invoke this only when you intend to run a real ClawHub lifecycle test. Use test credentials where possible, verify the slug before any update or delete action, and confirm cleanup afterward.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill documentation explicitly states it performs publish, update, and delete operations against a real API, but it does not provide a clear user-facing warning that executing the skill will make live changes and delete resources. This creates a real safety issue because users or agents may run it in a non-test context without understanding that it is destructive and targets production-like external state.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
## Notes

This skill is ephemeral and will be automatically deleted after the test completes.
If you see this skill listed on clawhub, it means a test run failed to clean up properly.
Confidence
84% confidence
Finding
The phrase indicating the skill will be 'automatically deleted after the test completes' describes autonomous destructive behavior without any mention of user approval or execution safeguards. In a skill that interacts with a real API, automatic cleanup increases risk because it normalizes unsupervised state-changing actions and could delete the wrong resource if identifiers or environment boundaries are wrong.

Tool Parameter Abuse

High
Category
Tool Misuse
Content
1. **Publish** — Creates a new skill via POST /api/v1/skills with multipart form data
2. **Inspect** — Retrieves skill metadata via GET /api/v1/skills/{slug}
3. **Update** — Publishes a new version of an existing skill
4. **Delete** — Removes the skill via DELETE /api/v1/skills/{slug}

## Notes
Confidence
95% confidence
Finding
The documented use of DELETE /api/v1/skills/{slug} against a real API is a true high-risk capability because the target resource is parameterized and potentially destructive. If the slug is influenced incorrectly, reused, or executed in the wrong environment, the skill could delete arbitrary skills rather than only ephemeral test artifacts.

Static analysis

No suspicious patterns detected.