output

Solid

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

Code & Development 3 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
20
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
1 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

tune-output

Change how Claude's replies are shaped — adopt, revise or reject a response-style rule — then record the pass in a ledger so the next one starts from evidence instead of from scratch. Owns the output style file, the blind A/B harness that tests a candidate before it ships, and the history of what has already been tried. TRIGGER when: the user wants replies formatted or worded differently, brings a response-style idea from another project or repo to evaluate, asks why a style rule exists or is missing, or says an existing style rule is not working. DO NOT TRIGGER when: the subject is prose inside a document or README (that is `documentation`), commit message wording (`shared/commit-message-rules.md`), a single one-off reply the user just wants rewritten, or a subagent's prompt.

1 Updated 2 days ago
AnotherSava
Data & Documents Listed

style-check

Fast deterministic prose-style checker. Wraps research-kit/tools/style_lint.py for file-scoped use. Use when the user invokes /style-check <file>, asks to "check style", "scan for AI tells", "polish before sending", or wants a quick mechanical pass before submission. For LLM whole-document review use /style-review; for section-scoped pre-submission validation use /validate-section.

0 Updated yesterday
hsigstad
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 1 months ago
Sandeeprdy1729