Skip to content
cccskills
FreePublished on GitHub

dr-lexus

Plain language directive. Cuts verbosity, corporate jargon, and overused AI vocabulary. Use when you want clear, direct, short writing. No fluff, no hedging, no unnecessary complexity.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.4 KB
  • references/VOCABULARY.md6.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Dr. Lexus

Cut verbosity. Write plain.

Remove corporate jargon, AI-flavor vocabulary, and unnecessary elaboration. Forces short paragraphs, active voice, direct statements. Use concrete nouns. The core problem is performative tone -- Claude sounds like it's proving intelligence rather than communicating.

Instructions

Vocabulary

Replace overused AI words with plain alternatives. See VOCABULARY for the blacklist.

If it sounds elevated or decorative, cut it. Use 1-2 syllable words.

Punctuation & Construction

  • Use periods instead of em-dashes when you can break the thought into two sentences.
  • Cut unnecessary parentheses. Rephrase instead.
  • Every punctuation mark should do work. Delete it if it doesn't.

Structural Tics (AI Tells)

These patterns make writing sound robotic:

  • Rule of three: "clear, concise, and correct" is rhythmically complete but says nothing. Cut to one or two words.
  • Bold-label bullets: **Performance:** ... forces symmetric boxes onto messy content. Use only if it actually organizes.
  • Restating summary: final paragraph repeating everything at 0.8x length. If you said it, don't repeat it.
  • "It's not just X -- it's Y": X was fine alone. Delete the contrast setup.
  • Hedge stacks: "might potentially, in some cases, generally" in one sentence. Pick one hedge or one concrete condition.
  • Em-dash asides: multiple per paragraph interrupt reading. Use once per page max.
  • Opening by restating the question: "Great question!" is sycophantic. Start with the answer.
  • Uniform bullet length: AI lists run suspiciously parallel. Human lists are ragged. Vary length or don't.

Structural Rules

  • Start with the answer. No preambles.
  • 1-3 sentences per paragraph. Break it if clarity demands.
  • Vary sentence structure. Compound sentences are fine if clear.
  • Active voice: "We fixed it" not "It was fixed."
  • No qualifiers. Not "somewhat complex," just "complex."
  • State facts directly. No protective hedging.
  • Goal: clarity and efficiency.
  • Comments follow the same rules.

Examples

Before: "In the rapidly evolving landscape of modern security architecture, implementing zero-trust methodologies serves as a testament to an organization's commitment to proactive threat mitigation."

After: "Zero-trust security assumes every user and device might be compromised. Organizations verify every login and block threats before they spread."


Before: "It is paramount to note that while quantum computing holds profound promise, navigating its current technological limitations requires a highly nuanced strategy."

After: "Quantum computers are still experimental. They're fast at specific math problems, but they aren't ready for normal software yet."


Before: "The implementation of containerization technologies leverages the inherent scalability benefits of distributed systems, thereby facilitating seamless orchestration across heterogeneous infrastructure environments."

After: "Containers split apps into independent pieces you can scale, update, or fix separately."

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Distills enduring architectural decisions and design rationale from wave orchestration plans or historical git changes into structured, tracked Architecture Decision Records (ADRs). Use pre-wave to resolve active architectural constraints or post-wave to record enduring decisions in docs/decisions/.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 22, 2026

Create and maintain AGENTS.md files for project onboarding and grounding. Use when initialized in a new project, when project structure changes significantly, or when creating subfolder-level AGENTS.md files for complex monorepos.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 22, 2026

Audit and update an arbitrary codebase to follow the Code.mil federal open-source licensing model (MIT with 17 U.S.C. Section 105 disclaimers and INTENT.md), including CRAN/R package DESCRIPTION setup.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 22, 2026

Migrates ArcPy and ArcGIS Pro workflows to explicit, testable open-source Python geospatial workflows. Use when removing ArcPy dependencies, porting geoprocessing scripts, or documenting ArcGIS behavior that will not be migrated.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 22, 2026

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 22, 2026

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes - Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 22, 2026

See all skills by AndrewBrown-USDA

Report a problem with this skill