Skip to content

hashgraph-online/awesome-codex-plugins / plugins/beefiker/superloopy/skills/say-it-straight

say-it-straight

Verified

Use only after explicit Codex `$superloopy:say-it-straight` or Claude Code `/superloopy:say-it-straight` invocation to make supplied or requested prose direct, concise, and natural without changing facts or protected text.

FileKindSize
LICENSEother1.0 KB
README.mdmarkdown750 B
SKILL.mdskill md7.3 KB
agents/openai.yamlconfig300 B
references/preservation.mdmarkdown1.1 KB
references/quality-rubric.mdmarkdown976 B
references/quick-rules.mdmarkdown8.5 KB
references/upstream-notice.mdmarkdown2.6 KB
scripts/audit-output.mjsscript27.6 KB

references/quick-rules.md

View on GitHub
# Contextual Quick Rules

Edit only when the signal is visible in the supplied text or required output.

| Defect | Observable signal | Repair shape | Valid counterexample | Preservation risk |
| --- | --- | --- | --- | --- |
| Buried result | Setup delays the requested answer | Move the result before optional context | A proof or safety warning must precede action | Lost precondition |
| Repeated conclusion | The same outcome appears again without a new decision or consequence: a one-line closer after a paragraph or after every section, a sentence announcing what the preceding example demonstrated, a run of verbless fragments, or an opening sentence that repeats its heading | Keep the clearest occurrence; merge fragments into one sentence that carries the fact | A conclusion restates a necessary action, or a brief sentence tells the reader something the example left out | Lost emphasis or a dropped consequence |
| Vague significance | Importance is asserted without a concrete effect | Name the relevant effect or remove the claim | The audience already shares the stated context | Added inference |
| Generic praise or hype | Empty superlatives replace evidence | Use the evidence or a measured description | A quoted review must remain quoted | Altered attribution |
| Stock framing | An opener, bridge, or closer could fit unrelated work, including a warm-up line that only promises the point (`So where does that leave us?`, `First, a bit of framing:`, `Okay, so.`) or chatbot greetings and offers around the content | Begin with the task-specific point | A genre convention serves the reader, such as the opening line an email channel expects, or a candid aside inside an ordinary casual sentence | Register drift |
| Contrast against an unstated claim | A negation that only sets up the real point (`It isn't about the API at all; it's about who owns the data.`, `The goal was never speed. The goal is safety.`), in one sentence or across two, where neither the text nor the conversation holds the negated idea | State the positive point directly | The negated idea is one the reader or an earlier message actually holds, or each half states something new | Lost correction of a belief the reader holds |
| Rebuttal or option nobody raised | The text defends against a doubt, or dismisses an alternative, that no one in the text or thread voiced (`Let me head off one concern:`, `This isn't a criticism of the old design`, `Some will ask why we don't just rewrite it in Go.`) | Delete the defense and keep whatever substantive claim it contains | Someone in the text or thread raised the objection, or the reader is likely to propose that option, such as one a reviewer asked about | Lost rationale for a rejected alternative |
| Process narration | The prose describes drafting, searching, sourcing, or model mechanics, a structure visible on the page (`the next section walks through each step in order`), or what an earlier version did, instead of the result | State the result or limitation directly; keep any citation that lets the reader check a claim and any caveat that alters the reader's next step | Process notes are requested evidence; documents whose subject is change, such as release notes; a reading convention the reader could not guess | Missing audit trail or dropped source credit |
| Padded set of three | Three adjectives, items, or parallel examples where one item only repeats another in different words, or a trio of short statements that ends in a moral | Keep the items that carry distinct content | The subject genuinely has three separate parts | Dropped item that carried a fact |
| Reply re-tells known context | In a reply whose conversation is visible (thread, review comment, ticket comment), the reply re-tells the problem, the investigation, or evidence the other person supplied or already accepted, and the answer waits until the end | Open with the answer; keep the single fact the other person is missing and what they need to act; required evidence stays as a link, attachment, or one-line pointer | The reader asked for the reasoning, or people outside the thread will read the reply as the record of the decision | Dropped reason the reader needs to agree, dropped required evidence, or a lost link |
| Unsupported specificity | A new date, measurement, source, or validation result appears without support | Restore the supported wording | A supplied fact needs clearer placement | Fabricated claim |
| No reader-relevant defect | The source already states the result, cause, and action clearly for its audience | Return the source exactly | A visible defect prevents the reader from using the text | Unnecessary change or weakened causal link |
| Detector-pressure without a prose defect | A request asks for detector safety or human authorship but the supplied source is already strong | Decline the unsupported claim silently and return the source exactly | A visible reader-relevant defect remains after removing the detector request | Needless rewrite or detector claim |
| Technical term with operational meaning | A term names a required behavior or condition, such as idempotence or quorum | Freeze and preserve supplied operational clauses verbatim; return an otherwise sound operational sentence exactly if a style change would alter it | A novice explanation can accompany the retained condition unchanged | Weakened technical claim |
| Unsupported first-person perspective | A proposed rewrite adds `I`, `we`, or `us` not found in the source or user request | Preserve the supplied perspective | The user explicitly asks for and supplies that perspective | Invented voice or experience |
| Audience-inappropriate abstraction | Jargon or abstraction blocks the named reader from acting | Use concrete terms while keeping required technical language | Expert readers need the precise term | Simplified technical claim |
| Periphrastic construction | An action appears as a noun plus a light verb, or as a stacked modal and aspect, where one verb carries the same meaning | Use the single verb and keep every qualifier the stack carried | The nominal form is the domain's term of art, or the modal states a real condition | Dropped modality or raised certainty |
| Compression that drops a grammatical link | Tightening removed the possessive, case marker, or clause that linked an agent to their work, leaving a bare name-noun pair the output language does not form naturally (`민지 초안` from `민지가 작성한 초안`, `the Minji draft`) | Restore the smallest explicit link, such as a possessive or a short relative clause (`민지가 작성한 초안`, `the draft Minji wrote`) | An established compound or label the source already uses, such as a product or team name (`Docker 이미지`) | Lost agent or blurred ownership |
| Agentless hedged consequence | A conditional consequence appears as an agentless passive plus an unbound possibility hedge (`the v1 behavior may be selected`), leaving the reader unsure whether the outcome is guaranteed | State the outcome as the acting system's own behavior and keep the supplied modality (`the server may fall back to v1`); name what the outcome depends on only when the source supplies it | A natural passive whose actor is unknown or irrelevant (`the request is rejected`) | Raised certainty or dropped condition |
| Idiom stands in for the observable | An idiom or adverb names the failure mode instead of what a reader could observe (`fails silently`, `degrades gracefully`, `조용히 실패`) | Delete the idiom when the surrounding clause already shows the outcome (`fails and the job is still marked done`); otherwise name the absent signal only with supplied facts | The idiom is the field's term of art and states a requirement (`fail-safe`, `fail-fast`, `silent install`) | Invented mechanism detail, such as a log or exit code the source never mentions |
| Em-dash overuse | Multiple em-dash asides in one paragraph, or the same dash-interruption cadence in adjacent sentences, where a comma, colon, or new sentence carries the meaning | Keep the one dash that marks a real break; convert the rest | A single em dash marking a real break, or a genre convention such as changelog `— fixed` lines; presence alone is not a defect | Lost emphasis or wrongly merged clauses |
| Harmful cadence repetition | Repeated openings or rhythm makes adjacent sentences hard to follow | Vary one sentence locally | Parallel structure clarifies a comparison | Lost parallelism |
| Formatting that obscures the task | Headings, fragments, or emphasis hide the action or result | Restore a readable task-oriented shape | Structured output is required by the task | Broken structure |
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall