unix-cli-best-practices

Safe, portable, and efficient command-line patterns for macOS/BSD Unix tools (grep, find, sed, awk, xargs, mdfind, pbcopy, open) and modern alternatives (ripgrep, fd). Covers common shell scripting and one-liner use cases including fast searching, text processing, codebase navigation, and parallel execution.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/agents/reidbaker-agent/skills/unix-cli-best-practices/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable reference with lean examples, held back by the absence of validation/dry-run checkpoints for its destructive and batch operations.

Suggestions

Add explicit validation/dry-run steps before destructive batch commands (e.g. preview the file list with 'grep -rlZ ... ' before piping to 'xargs -0 rm', or recommend 'fd -e log -X rm -i' / a confirm step) to lift workflow_clarity above 3.

Split the per-tool reference into a bundled references file (e.g. references/tool-flags.md) and keep SKILL.md as a concise overview with one-level-deep links to improve progressive_disclosure toward 5.

Trim the small redundancy between the opening paragraph and the 'Modern high-performance alternatives' intro to push conciseness to 5.

Dimension	Reasoning	Score
Conciseness	The body is lean: tight bullet lists of commands with purposeful, minimal code examples and no padding explaining what grep/sed/awk are; only minor redundancy in the intro paragraphs keeps it from a 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands and code blocks (rg flags, grep --exclude-dir, sed -i '', awk one-liners, xargs -0) that cover the common cases concretely.	5 / 5
Workflow Clarity	Sequences and safe/unsafe contrasts are present, but destructive and batch operations (xargs -0 rm, fd -e log -x rm, grep -rlZ \| xargs rm) have no validation, dry-run, or verification checkpoints, which the rubric caps at 3.	3 / 5
Progressive Disclosure	No bundle files exist, but the single 177-line file is well-organized with clear, navigable section headers per tool; it exceeds the under-50-line simple-skill exception, so it lands at 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that names concrete tools and use cases, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness and slightly weakens trigger guidance.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when working on macOS/BSD command-line tasks, shell one-liners, or portable text processing across grep/find/sed/awk/xargs') to raise completeness above 3.

Include a few more natural trigger synonyms users say (e.g. 'regex search', 'find files', 'CLI text processing') to broaden trigger-term coverage.

Tighten distinctiveness by foregrounding the macOS/BSD portability angle up front so it is less likely to collide with general shell-scripting skills.

Dimension	Reasoning	Score
Specificity	Lists many concrete tools (grep, find, sed, awk, xargs, mdfind, pbcopy, open, ripgrep, fd) alongside specific use cases (fast searching, text processing, codebase navigation, parallel execution), giving comprehensive coverage of concrete actions rather than vague language.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the rubric caps completeness at 3 in that case, and 'when' is only weakly implied by the use-case list.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('shell scripting', 'one-liner', tool names like ripgrep/fd) with good coverage, but a few common variations are absent (e.g. 'regex', 'find files', 'CLI').	4 / 5
Distinctiveness Conflict Risk	The macOS/BSD portability niche plus an explicit named-tool list make it mostly distinct with minimal conflict risk, though 'command-line patterns'/'shell scripting' could still overlap with general shell-scripting skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: flutter/agent-plugins
Path: .agents/agents/reidbaker-agent/skills/unix-cli-best-practices/SKILL.md
Commit: c3c71cf

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.