SkillAgentSearch skills...

warranted

Make AI research agents accountable — give every conclusion a traceable argument graph. MCP server + Claude Code plugin for paper reproduction, hypothesis verification, and auditable scientific reasoning.

Install / Use

claude mcp add yqi96 -- npx -y github:yqi96/warranted

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

81/100

Supported Platforms

Claude Code
Claude Desktop

Our assessment of warranted

warranted scores 81/100 on our quality scale, 388th of 443 Education & Research skills we index.

Its MCP Server is 9.2 KB long, well organised into 11 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 5 days ago, so warranted is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-07. Automated pattern scan on 2026-11-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

warranted compared with similar skills

All 4 of these similar skills score higher than warranted; compare them before choosing.

SkillScoreStarsUpdatedFormat
warranted (this skill)by yqi968135d agoMCP Server
Agent-Reachby Panniantong100109.8k1d agoCLAUDE.md
headroomby headroomlabs-ai10079.1ktodayCLAUDE.md
last30days-skillby mvanhorn10066.9k1d agoCLAUDE.md
CowAgentby zhayujie10047.8ktodayCLAUDE.md

Frequently asked questions

How do I install warranted?
Run claude mcp add yqi96 -- npx -y github:yqi96/warranted. The install tabs above show the steps for each supported agent.
Which AI agents does warranted work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is warranted safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is warranted still maintained?
The repository was last updated 5 days ago, so warranted is actively maintained.

Warranted

Make AI research agents accountable — give every conclusion a traceable argument graph.

Release License: MIT MCP Server Claude Code Plugin Stars

English | 简体中文

Code has compilers and tests. Research needs failure signals too.

What it does

Warranted gives a research agent a persistent, auditable argument graph. The graph has one node type: a proposition. Every proposition has five slots:

| Slot | Meaning | |---|---| | content | the statement being judged | | evidence | attached files and references to other propositions | | warrant | why that evidence supports the content, inline or promoted to its own proposition | | rebuttals | propositions that attack the content or warrant | | qualifier | one credibility scale: refuted → unestablished → possibly → probably → certainly |

Ground, backing, claim, and rebuttal are viewpoints, not node types. The same proposition can be evidence for one conclusion, a conclusion in its own right, and a rebuttal somewhere else.

Structural checks are deterministic and automatic. They return non-blocking warnings for incomplete evidence, missing attachments, changed dependencies, and similar conditions. They do not rewrite qualifiers or prevent the agent from recording a judgment. An explicit review call can ask a separate LLM for a semantic second opinion about source faithfulness and inference validity. Findings are advisory; they remain pending until a later review replaces them or they are dismissed with a reason.

After checking a small fix, rejecting a mistaken objection, or accepting a limitation for the stated use, the primary agent can dismiss with a specific reason. Dismissing every finding in the latest valid review records acceptance of the current input as passed by the agent, without rewriting the reviewer's verdict or changing credibility. Later input or protocol changes make that acceptance stale. Finishing does not require every node to pass or every warning to disappear.

Documentation

| Doc | What it covers | |---|---| | The Argument Graph | propositions, five slots, qualifiers, warnings, findings, and the 11-tool surface | | Reproducing a Paper | rebuild a paper's evidential chain using independently produced evidence | | Writing a Paper | write LaTeX whose \cite{prop_N} citations trace to propositions and attached papers | | Research Framework | how the primary agent, specialists, graph, and object-layer work divide responsibility |

The detailed contracts live in docs/design.md and docs/api.md. Release history is in CHANGELOG.md.

0.6.0 upgrade compatibility: version 0.6.0 replaces the 0.5.0 three-node/compile model with the proposition model described above, introduced in commit 90c7acb. Old .toulmin/argument.db files remain read-only historical archives; current runs use .toulmin/graph.db and do not mechanically migrate old verdicts. The 0.5.0 terminology remains in the changelog only as release history.

Setup with Claude Code

Install Bun (>= 1.0.0), Node.js, and a Chrome/Chromium browser, then:

git clone https://github.com/yqi96/warranted
cd warranted

# Optional: enable explicit third-party LLM review
cp review.json.example review.json
# Edit review.json and fill in apiKey; baseUrl is optional.

The plugin launchers run bun install --frozen-lockfile. The browser MCP uses the pinned chrome-devtools-mcp dependency and starts isolated browser sessions on demand.

Register and install the plugin:

claude plugin marketplace add $(pwd)
cd your-project
claude plugin install warranted@warranted --scope local

On launch, toulmin-researcher becomes the primary agent. Two stdio MCP servers start automatically:

  • toulmin stores the current graph at <project>/.toulmin/graph.db and exposes the 11 graph tools.
  • browser provides process-isolated Chrome sessions for browser-assisted research.

Review is never triggered merely by creating or editing a proposition. It runs only when the agent deliberately calls review, and only when review.json supplies a usable apiKey.

Review attempts have independent timeoutMs (default 600000, 10 minutes) and effort (default low), rather than inheriting the main agent's effort or sharing a node-wide budget. Three consecutive incomplete reviews within 30 minutes produce an advisory, not a lockout; a completed review with findings is not an execution failure. Identical completed or in-flight requests may be reused within the server process; refresh: true requests a new review. PDF page-range coverage needs Poppler's pdfinfo and the SDK's PDF reading support (pdftoppm for page rendering). Missing metadata or incomplete page coverage never counts as a completed read.

Audit is compact by default: input/attachment hashes, attempt outcome, elapsed time, and SDK-reported model/usage/cost when available (otherwise null). Set debug: true for diagnosis to additionally retain the actual prompt, SDK-visible event stream and hash-deduplicated immutable attachment bytes under the audit directory's debug/ subdirectory. Credentials are redacted; unreturned internal reasoning is not observable. Debug must be enabled before the attempt and can use substantial disk space. Normal mode does not guarantee exact-input replay. auditDir: null disables both modes. See review configuration and audit.

Hitting install or version issues? See known-working versions.

Tool surface

| Group | Tools | |---|---| | Write | create_propositions, update_proposition, set_qualifier, promote_warrant, delete_proposition | | Read | get_argument, find_propositions, get_stats, get_history | | Opinion | review, dismiss |

Writes validate content, referenced ids, and attachment existence. Structural warnings and review findings remain visible on reads; they advise rather than gate writes.

Visualizer

bun run viz

Open http://localhost:3456. The visualizer reads .toulmin/graph.db, colors propositions by qualifier, shows warning/finding badges, and can switch to another project's graph.db.

| Action | Effect | |---|---| | Click a node | select it | | Double-click a node | open its detail panel | | Shift + click | add to or remove from the selection | | Drag in box mode | select several nodes | | Drag in pan mode | move the canvas | | Scroll | zoom | | Click empty space | clear the selection |

The UserPromptSubmit hook injects the current visualizer selection into later Claude prompts when the visualizer is running on its default port.

Agents

| Agent | Role | |---|---| | toulmin-researcher | primary agent; controls the graph, coordinates research, and makes qualifier judgments | | toulmin-explorer | fast read-only graph lookup and navigation | | code-experimenter | bounded implementation, reproduction, and experiment execution | | code-optimizer | makes full-scope experiments feasible without changing their semantics | | discrepancy-auditor | audits one mismatch or claimed blocker before graph consequences are accepted | | rigor-auditor | completion-level audit of whether the overall research is exhausted and worth reporting | | literature-scout | performs one bounded browser-assisted literature search move and writes a durable search artifact | | paper-reader | reads specified papers against one inquiry question and writes evidence notes | | literature-extractor | records paper findings as propositions with source attachments; does not judge qualifiers |

Skills

| Skill | Trigger | Role | |---|---|---| | literature-survey | /literature-survey | iterative, question-driven critical literature review | | paper-reproduce | /paper-reproduce | independent reproduction and graph-based judgment of a paper's claims | | literature-writing | /literature-writing | literature-backed LaTeX writing with \cite{prop_N} citations | | cite-review | /cite-review | checks citation content and strength against propositions and qualifiers | | overleaf-setup | /overleaf-setup | one-time Overleaf sync and proposition-citation enforcement | | browser | /browser | safe operation of an isolated Chrome session through the browser MCP | | paper-download-browser | /paper-download-browser | authorized browser-assisted paper download when direct HTTP is insufficient |

Development

There is no separate build artifact: Bun executes the TypeScript sources directly, while TypeScript is configured for strict, no-emit checking.

bun test
bun ./node_modules/typescript/bin/tsc --noEmit
bun run agent-eval             # dry-run; add --live only when model cost is intended

Related Skills

View on GitHub
GitHub Stars3
CategoryEducation
Updated5d ago
Forks0

Languages

TypeScript

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low