printing-press-output-review

Reviews sampled CLI command output for plausibility bugs that rule-based checks miss.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/filippolmt/skills --skill printing-press-output-review-filippolmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: printing-press-output-review
Source: https://github.com/filippolmt/skills/tree/main/skills/printing-press-output-review
Command: npx skills add https://github.com/filippolmt/skills --skill printing-press-output-review-filippolmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rule-based checks on a generated CLI's output can only catch what regexes encode, so semantic bugs like irrelevant search results, silently dropped sources, broken ranking, and malformed URLs ship undetected. This Skill dispatches a reviewer agent to judge sampled command output the way a human tester would. ## Core Features & Use Cases - Semantic relevance review: Judges whether query results actually match user intent beyond mechanical substring matching. - Format and URL inspection: Detects mojibake, raw HTML entities, and URLs pointing at index pages instead of canonical permalinks. - Aggregation and ranking validation: Verifies fan-out commands show all requested sources and that ranked output is plausibly ordered. - Structured result contract: Emits a parseable PASS, WARN, or SKIP block that parent skills consume during shipcheck. - Use Case: During a printing-press shipcheck at Phase 4.85, the parent skill invokes this reviewer against the printed CLI's live-check samples, and any plausibility findings are logged as non-blocking warnings for the user to triage before publishing. ## Quick Start Invoke this skill from the printing-press shipcheck by passing the printed CLI's working directory so it reviews the sampled live-check output and returns a structured findings block.

Frequently Asked Questions about printing-press-output-review

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

FAQPage Schema
How do I review generated CLI output for semantic bugs?

Run the scorecard live-check to gather sampled command output, then dispatch a reviewer agent to judge query relevance, format bugs, source completeness, and ranking plausibility. Findings are returned as warnings in a structured result block.

What bugs do rule-based CLI output checks miss?

Rule-based checks miss substring matches that coincidentally contain the query, silent drops of failed sources in aggregation commands, broken ranking weights, and URLs pointing at category pages instead of permalinks. These require agentic judgment rather than regexes.

Can I invoke printing-press-output-review directly?

No, it is an internal sub-skill marked user-invocable false. It is called by the main printing-press skill at shipcheck Phase 4.85 and by printing-press-polish during its diagnostic loop; the actionable wrappers are /printing-press and /printing-press-polish.

Do output review warnings block shipping the CLI?

No, under the current Wave B policy all findings surface as warnings and never errors, so shipcheck proceeds regardless. Findings are logged to the run's artifact directory and the user decides case by case whether to fix before shipping.

What are the limitations of agentic output review?

It cannot verify numeric accuracy against ground truth, detect data freshness issues, or judge subjective quality. It only covers sampled commands in the live-check features array and assumes English-language query and output.