From agentic-guardrails
Safety rules for working inside cloud-synced folders — OneDrive, SharePoint synced libraries, Google Drive for desktop, Dropbox. Use whenever a task touches files under a synced folder, before bulk operations, or when a file read returns empty/garbage content for a file that clearly should have data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-guardrails:synced-foldersThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Synced folders look like normal directories but have three hazards: cloud-only
Synced folders look like normal directories but have three hazards: cloud-only placeholders, pointer stubs, and sync-conflict artifacts. The hooks catch most of this, but knowing why keeps you out of the ask-loop.
agw scan <folder> --json
Reports per folder: total files, placeholders (cloud-only, not hydrated), gdoc_stubs (.gdoc/.gsheet/.gslides pointer files), and sync artifacts (conflict copies, .tmp.driveupload, ~$ lock files). Plan around these before touching anything.
OneDrive Files On-Demand and Drive "online-only" files occupy zero local blocks; the bytes live in the cloud. Reading one through normal tools can return empty content, and writing one can permanently destroy the cloud copy (this is a real, documented data-loss class).
ConflictedCopy / conflicted copy files (Dropbox), -PC-name copies
(OneDrive): these hold a human's unmerged work. Never archive or overwrite
them without explicit instruction.~$xxxx.docx Office lock files and .tmp.driveupload: transient; ignore.agw publish or agw move.~/.agw) so
versions don't churn sync quota. Don't relocate it into a synced folder.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub profsynapse/agentic-guardrails-plugin --plugin agentic-guardrails