output
Solidoutput style linter run by the stop hook or via <path> argument
Install
Quality Score: 82/100
Skill Content
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
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.
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.
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