Judgment Day logo

Judgment Day

OrganizationPopular
Gentleman-Programming
judgment-day

Trigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds.

Overview

PublisherGentleman-Programming
Repositorygentle-ai
Skill namejudgment-day
Stars
7K
Forks
760
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Gentleman-Programming on GitHub. Read the source before you install it.

Installation

Install the Judgment Day AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Gentleman-Programming/gentle-ai.git /tmp/gentle-ai
mkdir -p .claude/skills
cp -r /tmp/gentle-ai/internal/assets/skills/judgment-day .claude/skills/judgment-day
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Judgment Day in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Judgment Day on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Judgment Day is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Activation Contract

Load only when the user explicitly requests Judgment Day or equivalent dual/adversarial review for a concrete target. Judgment Day is a standalone developer tool: judges run whenever asked, on any runtime, and need no review transaction, runtime identity, or delivery-receipt machinery to start. It replaces ordinary 4R as the adversarial method for that target; never run both.

Hard Rules

  • Resolve matching project skills before starting and pass the same paths to both judges (jd-judge-a, jd-judge-b) and the fix actor (jd-fix-agent).
  • Build one complete immutable target, then launch two blind read-only judges in parallel with identical scope and criteria.
  • Each judge returns one neutral findings result and terminates. Wait for both; never accept a partial judgment.
  • Never launch review-refuter; two-judge agreement is the corroboration mechanism.
  • Only the parent orchestrator merges/persists findings, launches the fix actor (jd-fix-agent), and launches scoped re-judgment.
  • Fix only severe findings confirmed by both judges. WARNING/SUGGESTION rows remain info.
  • Permit at most two fix rounds and two scoped re-judgments. Re-judgment sees only the frozen ledger plus fix delta and may record fix-caused defects.
  • The only terminal verdicts are APPROVED | ESCALATED; never reset or extend an exhausted round budget.
  • A judgment issues no receipt and carries no delivery authority: it satisfies no commit, push, PR, or release gate. When the caller explicitly wants ordinary negotiated review for the same target, run it as its own step; neither outcome authorizes delivery, which remains under ordinary repository policy.

Decision Gates

ConditionAction
Target unclearAsk one scope question and stop.
Both judges confirm severe findingAsk before round-one correction; then use the bounded fix actor.
One judge reports itRecord suspect; do not auto-fix.
Judges contradictEscalate for explicit human decision.
Scoped re-judgment fails before round twoParent may launch the final bounded fix round.
Any issue remains after round twoEscalate and stop.

Execution Steps

  1. Build the complete immutable target and freeze the scope both judges will inspect.
  2. Launch both read-only judges in parallel (jd-judge-a, jd-judge-b) against the same immutable target.
  3. Merge findings into the frozen ledger and persist it through the selected artifact store.
  4. Ask before round-one correction; run the fix actor (jd-fix-agent) only for confirmed severe IDs.
  5. Run both judges again (jd-judge-a, jd-judge-b) only over the frozen ledger plus immutable fix delta.
  6. Repeat once at most, then run independent final verification and return the terminal verdict.

Output Contract

Return target identity, round, confirmed/suspect/contradiction/INFO counts, correction work units, scoped re-judgment result, artifact references, skill resolution, and exactly one final JUDGMENT: APPROVED ✅ or JUDGMENT: ESCALATED ⚠️.

References

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Judgment Day AI skill do?

Trigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds.

Why use Judgment Day on TypingMind?

Because you install it once and use it with any model. Judgment Day is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Judgment Day in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Gentleman-Programming/gentle-ai/tree/main/internal/assets/skills/judgment-day. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Judgment Day?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Judgment Day?

As many as you like. As long as a model supports skills, you can use Judgment Day with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Judgment Day AI skill free?

Yes. It is published on GitHub by Gentleman-Programming under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇