{"id":79584,"plugin_id":"plugins_6ab427b8c6908191a438adb4b6f315d4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:26.456Z","digest":"8c79be8a49be08d2e3d7f5619e91ce393807ae0d28aedba7382524566d36d952","against":null,"payload":{"description":"Safely inspect, find, copy, move, rename, delete, synchronize or batch-change filesystem objects.","included_files":[],"name":"safe-file-operations","skill_md_contents":"---\nname: safe-file-operations\ndescription: Safely inspect, find, copy, move, rename, delete, synchronize or batch-change filesystem objects.\n---\n\n# Safe file operations\n\n## Scope and execution truth\nThis is a skills-only assistant workflow. Do not claim to execute system commands, inspect the user's host, install packages, or complete side effects without actual authorized tools and observed results. User-pasted output is evidence, not a machine connection.\n\n## Procedure\n1. Resolve the target path, relative/absolute context, mount, symlinks, leading-dash names and any shared/production scope.\n2. Start with read-only inspection (`pwd`, `find` preview, `stat` as appropriate). Show exact target selection and counts where possible.\n3. For delete, overwrite, recursive permission changes, or bulk renames, separate a preview from any mutating command. Do not combine them in one copyable block.\n4. Prefer new output paths, backups or staging; avoid unsafe variable targets and glob expansion. Treat `rm -rf` and `sudo` as high risk.\n5. Validate before and after: counts, hashes, sample paths, diffs, backups or rollback availability.\n6. Explain GNU versus BSD option differences and filename-safe traversal, using `find ... -exec ... {} +` where appropriate.\n\n## Relevant references\n- Read `../../references/filesystem-operations.md` for domain-specific guidance.\n- Read `../../references/safety-risk-model.md` for domain-specific guidance.\n- Read `../../references/portability-matrix.md` for domain-specific guidance.\n\n## Completion checks\n- Selected files are previewable\n- No path or symlink surprise\n- Recovery plan matches the operation\n\n## Deliverable\nUse the minimum format that makes the answer actionable: the actual command or patch, platform assumptions, a preview before risky changes, and a reproducible validation step. Clearly label proposed actions versus observed execution.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}