{"id":79574,"plugin_id":"plugins_6ab427b8c6908191a438adb4b6f315d4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:26.151Z","digest":"10744e0f3ac340e99fcf98ee5eeaa2b8ffbdbddb5e0d744f7440c567f6a95272","against":null,"payload":{"description":"Translate plain-language Unix or CLI tasks into safe, copy-ready shell commands with assumptions and verification.","included_files":[],"name":"command-from-task","skill_md_contents":"---\nname: command-from-task\ndescription: Translate plain-language Unix or CLI tasks into safe, copy-ready shell commands with assumptions and verification.\n---\n\n# Write a command from a task\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. Clarify inputs, outputs, scope, path, shell and platform only when necessary. Write a one-sentence intended effect before generating complex commands.\n2. Prefer one simple command to a brittle pipeline; avoid parsing `ls`, needless privilege, `eval`, and dynamically constructed shell text.\n3. Quote paths and variables, protect leading-dash filenames as the utility allows, and distinguish shell globbing from regular expressions.\n4. If output is changed, identify overwrite/privilege risk. Generate a read-only preview first for consequential operations. Keep destructive command separate and never auto-execute it.\n5. Show labeled GNU and BSD/macOS alternatives if relevant. For POSIX `sh`, avoid arrays, `[[ ]]`, process substitution and nonstandard pipefail.\n6. Include a minimal command explanation and a meaningful validation command; skip boilerplate for straightforward read-only questions.\n\n## Relevant references\n- Read `../../references/shell-quoting.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- Copy-ready syntax\n- No unverifiable side effects\n- Preview and validation appropriate to scope\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":{}}