{"id":79589,"plugin_id":"plugins_6ab427b8c6908191a438adb4b6f315d4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:26.639Z","digest":"fec0c4600c11e66ccf216b232bf2f458419c7a454687560dec364a163bda6f23","against":null,"payload":{"description":"Search and transform Unix text safely with grep, sed, awk, find, sort and related tools.","included_files":[],"name":"text-search-transform","skill_md_contents":"---\nname: text-search-transform\ndescription: Search and transform Unix text safely with grep, sed, awk, find, sort and related tools.\n---\n\n# Text processing and search\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. Identify input encoding, regex flavor, desired matching semantics, file count, line endings and locale sensitivity.\n2. Select simplest tool: grep/ripgrep for search, sed for stream edits, awk for column/record processing, find for path selection.\n3. Clarify literal versus regex matching and basic versus extended regex; do not reuse GNU-only flags in BSD/macOS commands without labeling.\n4. Show sample read-only output before using `-i` or writing over a source. Prefer new output files and diff/reconciliation checks.\n5. Avoid parsing general CSV as plain text. Route quoted or multiline CSV to `structured-data-cli`.\n6. Check unusual filenames, untrusted patterns and output size; use NUL delimiter where actually supported.\n\n## Relevant references\n- Read `../../references/text-processing.md` for domain-specific guidance.\n- Read `../../references/portability-matrix.md` for domain-specific guidance.\n- Read `../../references/filesystem-operations.md` for domain-specific guidance.\n\n## Completion checks\n- Correct regex dialect\n- Non-destructive transform path\n- Verified encoding assumptions\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":{}}