Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Pilot Audit Log
v1.0.0Comprehensive audit trail of all Pilot Protocol activity for security and compliance. Use this skill when: 1. You need detailed logs of all trust decisions a...
⭐ 0· 16·0 current·0 all-time
byCalin Teodor@teoslayer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name and description align with the requested artifacts: it requires pilotctl and creates an audit directory under ~/.pilot/audit, which is appropriate for an audit-log skill. However the SKILL.md assumes an AGENT variable is available (used in pilotctl calls) but the skill metadata does not declare or require any environment variables—this is inconsistent.
Instruction Scope
Instructions instruct creating and appending to files under ~/.pilot/audit and running pilotctl (expected). They reference $AGENT and other shell variables without declaring or validating them. Several log commands concatenate raw variable contents into JSON/plain-text without escaping, which can produce malformed logs or allow injection of unexpected content into the audit file. The instructions do not send data to external endpoints unrelated to pilotctl, but the undeclared env var and unescaped usage are scope/safety issues.
Install Mechanism
Instruction-only skill with no install spec or downloads; lowest install risk. It relies on the existing pilotctl binary and (optionally) jq, which is consistent with the documented dependencies.
Credentials
The skill declares no required credentials or env vars (reasonable for a local audit tool). However the runtime instructions use $AGENT (and $HOME implicitly) without declaring them. The lack of declared env vars makes it unclear what privileges/inputs are expected. Audit files are written to the user's home directory—this is proportionate but may contain sensitive data and should be permissioned and documented.
Persistence & Privilege
always:false and user-invocable:true (defaults) — normal. The skill writes files in the user's home directory but does not request system-wide changes or other skills' configs. No elevated persistence privileges requested.
What to consider before installing
This skill appears to be an audit logger for Pilot Protocol and is generally coherent, but do the following before installing or running it:
- Confirm what value should populate $AGENT (the SKILL.md uses $AGENT but no env var is declared); add a declared env var or replace with explicit agent IDs.
- Review and sanitize inputs that go into the log (escape JSON and shell metacharacters) to avoid malformed logs or injection via agent names/results.
- Ensure the audit directory (~/.pilot/audit) has correct permissions and a retention/back-up plan—logs may contain sensitive info.
- Verify pilotctl's behavior for the handshake commands used here (they may perform network or trust changes) and ensure you trust the pilotctl binary and daemon being used.
- Consider adding explicit instructions for log rotation, redaction of secrets, and validation of inputs in the SKILL.md.
If you want me to, I can produce a safer, corrected SKILL.md snippet that declares expected env vars, escapes JSON properly, and documents permissions/retention recommendations.Like a lobster shell, security has layers — review code before you run it.
latestvk97ecd6n6w18nptx0mw5x0938184ft2m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl