By FuZhiyu
Disciplined AI Research Assistant for economists: plan-implement-integrate workflow with implementer–reviewer pair, data-analysis discipline, and drift-test-verified integration.
Prototype implementer agent. Used throughout the superRA workflow from implementing to refactoring.
Prototype reviewer agent. Verifies work independently using a two-verdict APPROVE/REVISE protocol with CRITICAL/MAJOR/MINOR severity levels on findings. Used at every stage of superRA workflow. Adversarial by design.
Requires `superRA:using-superra` loaded first. Use when dispatching agents in the superRA workflow. Triggers include "dispatch N agents", "run these in parallel", "who should do the review", a multi-step workflow that needs coordination across roles, or a session handoff where workflow state must survive. Usable in any phase of the superRA workflow (PLAN / IMPLEMENT / INTEGRATE).
Use when installing or refreshing superRA's named Codex agents in project scope (.codex/agents) or global scope (~/.codex/agents).
Use PROACTIVELY whenever performing data analysis on economic, financial, or panel datasets — importing raw data, cleaning, merging, filtering, constructing variables, aggregating, computing summary statistics, producing regression inputs, building figures, or writing analysis scripts. Triggers include panel data, "merge these datasets", "run regression", "clean this data", "construct variable X", "check the summary stats", or any data file with unknown structure. Language-agnostic (Python, Julia, R, Stata).
Use whenever creating a PLAN.md / RESULTS.md from scratch, maturing RESULTS.md into its permanent record at INTEGRATE, or when you need the full editing discipline for a task-block-structured handoff document. Carries the four document principles, the inline-edit rule, the stale-content checklist, and pointers to full PLAN.md / RESULTS.md anatomy templates. Usable standalone by a single author with no subagents — the author plays all roles and reads this skill directly. Doc-creation call sites: `superplan` Phase 2 (new plan + RESULTS.md skeleton) and `superintegrate` Step 3 doc-writer (Stage 2 maturation).
Convert PDFs to Markdown using Mistral OCR API with image extraction. Use when you need to extract structured text and images from PDFs, especially for scanned documents or documents with complex formatting. Outputs Markdown with embedded images.
Executes bash commands
Hook triggers when Bash tool is used
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
⚠️ Breaking change (0.2.0): the three workflow phase skills were renamed —
planning-workflow→superplan,implementation-workflow→superimplement,integration-workflow→superintegrate— to avoid colliding with Claude Code's Workflow tool //workflows. Update any savedSkill(superRA:planning-workflow|implementation-workflow|integration-workflow)calls to the new ids, and refresh globally-installed Codex agents by rerunningcodex-superra-setup. See RELEASE-NOTES for the migration note.
superRA turns AI coding agents into disciplined Research Assistants. It ships:
superRA is inspired by the Superpowers plugin, which centers on test-driven software development. superRA adapts the same spine to scientific research, which is exploratory, iterative, and fluid.
superRA is compatible with Claude Code, Codex, and any other harness that supports skills and subagents. See below for installation.
AI agents are fast but undisciplined:
superRA brings discipline to the agent on three fronts. An implementer–reviewer pair sits at every step so no result ships without adversarial review. Domain skills teach the agent the right protocol for the work at hand (for data analysis: always describe before you transform; for theory-modeling: define objects and assumptions before you manipulate the equations; for slide design: reason from the audience's context before optimizing the slide). And an explicit integration phase folds each task into the existing codebase and maturing documentation, so what lands on main is coherent rather than a pile of single-shot outputs.
This workflow assumes basic familiarity with git branch/PR workflow; worktrees help but are optional.
superRA organizes work into three phases: PLAN → IMPLEMENT → INTEGRATE. Each phase corresponds to a workflow skill to teach agents how to carry out in order, and a using-superra skill serves as the shared disciplines and knowledges across agents. The phases are domain-agnostic; the domain skill supplies the discipline that applies inside each phase. The phases form a cycle, not a pipeline: a discovery during IMPLEMENT, a reviewer request during INTEGRATE, or a scope change after merge all route back through superplan §User Feedback and Changing Plans, which walks the task DAG and resumes at the right re-entry point.
flowchart TB
PLAN["<b>PLAN</b><br/>scope · task decomposition<br/>PLAN.md + RESULTS.md"]
IMPLEMENT["<b>IMPLEMENT</b> (per task)<br/>implementer ⇄ reviewer loop<br/>APPROVE advances · REVISE loops back"]
INTEGRATE["<b>INTEGRATE</b><br/>Protect results <br/>Sync with base<br/>Integrate/refactor<br/>Document<br/>Finish"]
FINISHED(["finished"])
PLAN --> IMPLEMENT
IMPLEMENT --> INTEGRATE
INTEGRATE --> FINISHED
IMPLEMENT -. "plan change" .-> PLAN
INTEGRATE -. "plan change" .-> PLAN
classDef phase fill:#eef7ff,stroke:#0366d6,color:#000
classDef terminal fill:#e8f5e9,stroke:#2e7d32,color:#000
class PLAN,IMPLEMENT,INTEGRATE phase
class FINISHED terminal
To invoke the workflow, use the keywords: using superRA, make a plan on..., implement according to the plan, integrate it with the update on the main, ... — or name a phase skill directly: superplan, superimplement, superintegrate.
npx claudepluginhub fuzhiyu/superra --plugin superRAConvert PDFs to Markdown using Mistral OCR API with image extraction
Working journal entries and markdown report generation for academic research
Read and analyze academic papers from Zotero library
Review code, update documentation, and create well-organized topical git commits
Multi-agent academic paper review with mathematical, writing, consistency, and proofreading analysis
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.