Action Guard

v1.0.0

Prevents duplicate external actions (posts, replies, sends, transfers, deploys). Check before acting, record after. Use when: (1) replying to social media po...

0· 138·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (prevent duplicate external actions) aligns with the included CLI script and SKILL.md. The script only implements check/record/history/stats/search for action records and requires no external services or credentials.
Instruction Scope
Runtime instructions are limited to invoking the local Node script to check/record actions and to wrap external actions. This stays within the stated purpose. Note: SKILL.md suggests recording notes which could contain sensitive content (messages, transaction details); the skill will store whatever is provided in plaintext in the local data directory.
Install Mechanism
No install spec or external downloads; code is provided in the package and runs locally with Node. No network fetches, package installs, or archive extraction are present.
Credentials
No environment variables, credentials, or config paths are required. The script uses only a data directory (default .action-guard in the current working directory).
Persistence & Privilege
The script persists records to a local file (.action-guard/actions.jsonl). It does not request persistent platform privileges, does not set always:true, and does not modify other skills or system-wide settings. Note: the file is stored in plaintext in the working-directory; consider permissions/backup/rotation and that concurrent agent runs have no built-in file-locking (possible race conditions leading to duplicate external actions).
Assessment
This skill appears coherent and local-only: it stores action records in .action-guard/actions.jsonl and provides CLI commands to check and record actions. Before installing/using: 1) Ensure you run it from a sensible working directory or set --data-dir to a secure path; the notes and targets are stored in plaintext, so avoid recording secrets or private keys. 2) If you plan to use it in parallel or distributed automation (multiple processes/machines), be aware there is no file-locking or centralized store — race conditions could still allow duplicate actions. 3) If you need stronger guarantees or shared state, consider using a secure central database or add locking/atomic check-and-write logic. Otherwise this local CLI is consistent with its description and does not request unnecessary access or credentials.

Like a lobster shell, security has layers — review code before you run it.

agentsvk979z71zrge9nxxat0pt3hqtms8320gmdedupvk979z71zrge9nxxat0pt3hqtms8320gmlatestvk979z71zrge9nxxat0pt3hqtms8320gmsafetyvk979z71zrge9nxxat0pt3hqtms8320gm

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments