agentsclimarketplace

Cli control

Skill yarlson/yarstack/plugins/yarstack/skills/cli-control

Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.

Install
npx -y skills add yarlson/yarstack --skill cli-control

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Verify terminal-hosted CLI or TUI behavior with repeatable local evidence. Use for output, prompts, interactive input, signals, hangs, resizing, startup, exit status, or terminal restoration.

SKILL.md

1.5 KB, as published. Nobody here has run it

CLI Control

Gather reproducible evidence from terminal-hosted interfaces without changing production behavior.

Workflow

  1. Identify the command, working directory, terminal conditions, and observable contract.
  2. Choose the smallest repeatable method: direct execution or repository tests for ordinary output and status; a terminal-capable harness for prompts, signals, resizing, hangs, or restoration.
  3. Prefer an existing trusted harness. Otherwise use a temporary local harness outside the repository without adding dependencies.
  4. Drive one action at a time and capture the smallest transcript or measurement that proves or disproves the behavior.
  5. Check interrupts, cleanup, exit status, hangs, and terminal restoration only where relevant.
  6. Clean up only sessions, processes, and artifacts created by this workflow.

Keep verification read-only unless the parent task separately authorizes implementation. Use behavior-implement and test-design for fixes or regression tests. Leave browser, desktop, Electron, and other graphical surfaces to ui-control.

Do not send credentials or destructive commands, retain sensitive transcripts, or keep one-off harness code in the repository without a product-test consumer.

Finish with the command and conditions, observed output and exit status, evidence, and any blocker or limitation.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.