term-interrogation

Unpacks jargon and assumed-knowledge phrases in documents into plain language with a term ledger.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/lyndonkl/hermesworld --skill term-interrogation-lyndonkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: term-interrogation
Source: https://github.com/lyndonkl/hermesworld/tree/main/packages/product-strategist/skills/strategy/term-interrogation
Command: npx skills add https://github.com/lyndonkl/hermesworld --skill term-interrogation-lyndonkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished reports and explainers often hide whole concepts inside ordinary-sounding phrases like "moat", "flywheel", or "at scale", leaving non-expert readers nodding along without understanding. This Skill audits a draft line by line, explains every concept-bearing term where it first appears, and recurses on its own explanations until everything bottoms out in plain language. ## Core Features & Use Cases - Five-kind term detection: Flags assumed-knowledge phrases, domain terms, acronyms, named entities, and vague boosters, then applies a keep-or-cut test to each. - Recursive explanation: Re-reads every gloss it writes, unpacks any new term the explanation introduced, and counts passes per term until only ordinary language remains. - Term ledger and glossary: Emits a checkable ledger recording each term's kind, location, handling, source (document or imported fact), status, and pass count, plus an alphabetical plain-language glossary. - Use Case: After drafting a strategy report for a general audience, run this pass to turn "Figma's moat is its multiplayer canvas" into prose a reader with no background can restate, with every imported fact marked for verification. ## Quick Start Review this draft and unpack every jargon term and assumed-knowledge phrase until a complete beginner could follow it, then give me the term ledger and glossary.

Frequently Asked Questions about term-interrogation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a business report readable for non-experts?

Run a term-interrogation pass over the finished draft: flag every concept-bearing phrase, explain each one at first use with an appositive, setup sentence, or concrete example, and recurse on your own explanations until only ordinary language remains.

How to decide whether to keep or cut jargon in writing?

Apply the reuse test: keep and teach a term if the reader will meet it again outside the document and it has a settled definition, like gross margin or churn. Cut and restate writer shorthand like at scale, best-in-class, or leverage that the reader never needs to carry forward.

What is the difference between term-interrogation and a readability check?

Term-interrogation is an audit and repair pass that explains hidden concepts in finished prose, while readability-check only scores the result afterward. Run term-interrogation first, then score the revised document without lowering the profile to make it pass.

When should I not explain a term in place?

When a passage exceeds roughly one flaggable term per sentence, inline glosses pile up and collapse the rhythm. Write a short orienting paragraph covering what the thing is and how it makes money first, then rerun the pass; beyond three terms per sentence, rewrite from the underlying claim.

Can I add facts the original document never stated when explaining terms?

Yes, importing facts is allowed and often necessary, but every imported fact must be marked in the term ledger with source set to imported and listed under the ledger. If you cannot vouch for a detail, use a non-specific gloss rather than inventing a confident one.