DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to expose the unstated premises in a draft argument with Misaka Agent

Use a red-team review to find what a conclusion leaves unsaid yet relies on.

  • Research
  • Intermediate
  • 60 minutes
  • From the README
  • Any agent

Who it is forA social scientist whose draft argument may depend on assumptions it never states, and who wants them tested before peer review.

The problemCo-authors and reviewers often miss the premises a conclusion takes for granted.

The outcomeA set of recorded gaps and presuppositions, each answered as a revision, rebuttal, conceded cost, referral, parked point or decision for you.

What you need first

  • uv, git, ripgrep, fd and poppler installed, or the prebuilt release archive for macOS, Linux or Windows
  • Access to a model provider: an API key, or a ChatGPT or GitHub Copilot subscription
  • A working folder under Documents, not the root directory

Steps

  1. Run uv tool install "misaka[providers] @ git+https://github.com/Luciole-Studio/Misaka-Agent.git".
  2. Run mkdir ~/Documents/my-research and then cd ~/Documents/my-research.
  3. Run misaka, then type /research with your draft argument stated as the question.
  4. Read the red-team review and the divergence review recorded in each node's files.
  5. Answer any decision MISAKA raises in conversation, because it seeks your consent before altering the question you asked.

Prompt for your agent

Use the Luciole-Studio/Misaka-Agent repo to run /research on this draft argument: <draft argument>. Expected output: a red-team review and a divergence review listing unstated premises and gaps in the conclusion. Verify that each listed presupposition has a recorded response in the node's files.

Caveat. Each Sister brings her own model, so the strength of the red-team review depends on which model you assign to that Sister.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page