Savage Research
- Updated April 12, 2026
- AliBassam/savage-researcher
savage-research is a Claude Code skill in the AI & Agent Building category. Savagely self-critiquing research framework. Evaluates a local repo's product/idea claims against web evidence and emits a no-bullshit markdown report.
Key points
- savage-research
- AI & Agent Building
- AI-coding skill
Savage Research by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add AliBassam/savage-researcher/plugin install savage-research@savage-researcherAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | April 12, 2026 |
|---|---|
| Repository | AliBassam/savage-researcher ↗ |
What it does
Savagely self-critiquing research framework. Evaluates a local repo's product/idea claims against web evidence and emits a no-bullshit markdown report.
README.md
Savage Research Framework
A Claude Code plugin that runs a savagely self-critiquing, multi-agent research pipeline on a local repository and emits a no-bullshit markdown report.
What it does
Point it at a local repo. It reads the pitch, extracts every claim, dispatches five specialist agents in parallel (prior-art, claim-audit, failure-modes, traction, framing), synthesizes their findings, runs an adversary that tries to kill the synthesis, revises against the kill-list, self-audits against hard invariants, and emits a report to <repo>/.research/.
Usage
/research <local-path-to-repo>
Example:
/research ./test-fixtures/bullshit-repo
Install (Claude Code Plugin)
Add this repo as a plugin marketplace and install, directly from Claude Code:
# Inside Claude Code:
/plugin marketplace add AliBassam/savage-researcher
/plugin install savage-research@savage-researcher
That's it. No clone, no per-project setup. The /research command is available in every Claude Code session on your machine.
To uninstall:
/plugin uninstall savage-research@savage-researcher
To verify it's loaded:
/plugin
savage-research should appear in the plugins list, with /research available as a command.
How to tell it worked
After /research <path>, check <path>/.research/:
- The top-level
YYYY-MM-DD-HHMM-<repo>.mdis the final report. runs/YYYY-MM-DD-HHMM/contains the full working trail: ingest summary, claim list, all five scratchpads, every draft version, kill-list, and audit results.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10