output

Solid

output style linter run by the stop hook or via <path> argument

Code & Development 1 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

**every reply is linted:** against the output style rules to keep conversations consistent - used by the `retardify-output.sh` `stop` hook automatically but can be used manually for debugging - grades the mechanically checkable rules like markup, constraints, shapes, etc - blocks on HARD findings and quotes the offending line so the fix is mechanical # Instructions ## Telemetry ```! if [ -n "$ARGUMENTS" ]; then "${CLAUDE_PLUGIN_ROOT}"/skills/output/output.sh $ARGUMENTS; echo "sidecar exit: $?" else echo "no path given, so nothing ran; pass a reply file, or - to grade stdin"; fi ``` - `help: requested` → the run was refused before it started; `## Help` below is the whole turn - this already ran; never re-issue it, and never a bare `output.sh`, which waits on stdin forever - `fail (sidecar exit > 0)` → HARD findings: report them, fix the reply's shape, then regrade - `success (sidecar exit = 0)` → clean or SOFT-only; note any SOFT findings and move on ## Findings > every finding reads `TIER RULE:LINE detail`, and the rule is an address into the style spec | rule | what it caught | |---|---| | `B1` | markup outside a list, table, fence or backtick: bold, italics, emoji, fenced plaintext | | `B2` | a prose line, or past the tolerance, a reply that has gone fully paragraphs | | `B6` | a banned sentence shape standing in for a plain statement | | `C2` | a line wider than the spec's character cap | | `C8` | a reply taller than the spec's line ceiling | | `V2` | file names carryi...

Details

Author
MaisonDeVolonte
Repository
MaisonDeVolonte/construct
Created
4 weeks ago
Last Updated
2 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

structured-output

Strict structured output enforcement skill. Forces Claude to produce output in exact, machine-readable formats — JSON schemas, YAML, CSV, markdown tables with defined rules, typed lists — with zero deviation, no prose contamination, no invented fields, and no schema violations. Validates output against the schema before delivery. Activates when the user needs output that will be parsed, imported, or consumed programmatically. Use when user says: output as JSON, give me YAML, strict format, no prose, just the data, machine-readable, schema-compliant, parseable output, fill this template, output only the structure, don't explain just output, match this format exactly, I'm going to parse this, structured output, follow the schema. Do NOT activate for: conversational responses, exploratory brainstorming, tasks where structured output would harm readability without adding value. First response: "Structured Output active. Paste your schema or describe the exact format you need. I'll produce and validate output befo

3 Updated 2 weeks ago
Sandeeprdy1729
Code & Development Listed

lint-and-style-config

Enforces a strict analysis_options.yaml built on very_good_analysis with strict-casts/strict-raw-types, a fixed set of silence-producing bug classes promoted to error (unawaited_futures, discarded_futures, empty_catches, use_build_context_synchronously, cancel_subscriptions, close_sinks, avoid_dynamic_calls, exhaustive_cases, avoid_print), dart format as the sole whitespace authority, generated-file excludes mirrored to coverage, and line-scoped-only suppression discipline; teaches the version-pinned-include trap (a missing include silently disables all rules), the errors-only-re-ranks-vs-linter-enables mechanic, and the sealed-switch analyze-vs-compile gap. Use when editing analysis_options.yaml, adding or disabling a lint, writing an `// ignore:`/`// ignore_for_file:`, bumping the Dart SDK or very_good_analysis version, wiring riverpod_lint, or explaining why discarded_futures, use_build_context_synchronously, close_sinks, or missing_provider_scope fires.

0 Updated 2 weeks ago
zakariaf
Code & Development Solid

writing-user-outputs

CLI output formatting standards for worktrunk. Load before editing any code that calls warning_message, hint_message, error_message, info_message, eprintln, or println, or that produces strings the user will see (CLI help, progress UI, snapshot text). Documents ANSI color nesting rules, message patterns, and output system architecture.

6,561 Updated today
max-sixty