tool-subcommand

Filter CLI output through a declarative YAML DSL.

397|41|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/edouard-claude/snip --skill tool-subcommand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-subcommand
Source: https://github.com/edouard-claude/snip/tree/main
Command: npx skills add https://github.com/edouard-claude/snip --skill tool-subcommand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Snip users often contend with noisy, verbose CLI output that blooms the AI context. This Skill provides a declarative YAML DSL to filter and condense command output so you can focus on signal.

Core Features & Use Cases

  • Declarative 19-action filter DSL to keep, remove, transform, and extract relevant lines from command output.
  • Per-project and user-level filter directories (filters/*.yaml embedded in the binary, ~/.config/snip/filters, and optional project dirs) for flexible workflow customization.
  • Safe, deterministic pipelines with built-in fallbacks and error handling to preserve original command exit codes and avoid data loss.

Quick Start

Create a new YAML filter under filters/your-tool.yaml and run snip with your command to apply it.

Frequently Asked Questions about tool-subcommand

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage from verbose CLI output in AI contexts?

You can reduce token usage by applying declarative YAML filters to CLI output, condensing command results to focus on signal. This Skill uses a 19-action DSL to keep, remove, transform, and extract relevant lines before they enter the context window.

How do I create a YAML filter to clean up command line output?

To create a YAML filter, define your desired transformations using the 19-action DSL in a new file under filters/your-tool.yaml. Running the CLI command through the snip tool then automatically applies these declarative filtering rules to the output.

What is a declarative DSL for filtering CLI output and how does it work?

A declarative DSL for CLI filtering uses a 19-action vocabulary to specify deterministic pipelines that keep, remove, or transform lines. It processes command output safely with built-in fallbacks to preserve original exit codes and prevent data loss.

Can I customize CLI output filters for specific projects and user directories?

Yes, you can customize CLI output filters by placing YAML files in per-project directories or user-level paths like ~/.config/snip/filters. The system also loads built-in filters embedded directly in the binary for flexible workflow customization.

Do I need a SKILL.md file to use YAML filters for command line output?

Yes, the YAML filtering Skill requires a SKILL.md frontmatter containing a name and description to function properly. This metadata ensures the 19-action DSL pipelines execute with deterministic behavior and safe fallbacks.

What happens to original command exit codes when filtering CLI output through YAML?

Filtering CLI output through YAML preserves the original command exit codes by utilizing safe, deterministic pipelines with built-in fallbacks. This error handling ensures that condensing output for token savings does not result in data loss or failed executions.