Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
npx claudepluginhub etoyama/insight-blueprint --plugin insight-blueprintGuides Claude through creating analysis design documents for hypothesis-driven EDA. Use when the user wants to create, manage, or review analysis designs. Triggers: "create analysis design", "hypothesis document", "new hypothesis", "分析設計を作りたい", "仮説を立てたい", "新しい仮説", "仮説ドキュメント".
Explores existing data and analyses to help frame a hypothesis. Triggers: "framing", "何を分析する", "分析テーマ", "仮説を考えたい", "データを探して", "既存分析を確認", "analysis framing".
Records reasoning steps during hypothesis-driven analysis as an Insight Journal. Supports observation logging, evidence tracking, method decisions, question management, and hypothesis branching. Journal data is stored as YAML alongside design files. Triggers: "journal", "記録して", "ジャーナル", "推論を残す", "分析ログ", "分析の経緯", "なぜこの結論に至ったか記録", "evidence log".
Guides structured reflection on an analysis design using its Insight Journal. Helps draw conclusions, identify gaps, and decide whether to conclude, refine, or branch. Triggers: "振り返り", "reflection", "まとめ", "結論を出す", "分析を振り返る", "この仮説どうなった", "wrap up analysis".
Guides structured revision of an analysis design based on review comments. Reads review feedback via MCP, tracks progress per comment, and helps fix each issue. Triggers: "レビューを直して", "指摘を反映して", "revision対応して", "fix review", "address comments", "レビュー修正".
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Self-documenting, self-improving framework for analytical repositories
Data science and ML workflow tools. 9 agents, 8 commands, 19 skills, 9 templates for problem framing, preprocessing, validation, EDA, experimentation, review, deployment, and knowledge compounding.
Computational-science methodology for Claude Code: research framing, pre-registration, reproducible analysis, anomaly investigation, and red-team review
Quick insights from dlt pipeline data. Connect to a pipeline, profile tables, plan charts, and assemble marimo dashboards.
Design experiments, profile datasets, build models, and audit them for bias before shipping
Explore, query, model, embed, and manage Omni Analytics through the REST API and embed SDK. Includes 9 skills, 3 specialized agents, and 3 context rules for model exploration, querying, model building, content browsing, content building, embedding, AI optimization, AI eval, and administration.
Persist session context and decisions across Claude Code sessions via GitHub Issues
A Python MCP server for hypothesis-driven data analysis. Manage analysis designs, data catalogs, and review workflows through Claude Code or any MCP-compatible client.
# Option 1: From the official marketplace
claude plugin install etoyama/insight-blueprint
# Option 2: Via custom marketplace (permanent install)
/plugin marketplace add etoyama/insight-blueprint
/plugin install insight-blueprint@insight-blueprint-marketplace
# Option 3: From a local clone (session only)
git clone https://github.com/etoyama/insight-blueprint.git
claude --plugin-dir ./insight-blueprint
All options provide 8 analysis skills and auto-configure the MCP server. A WebUI dashboard opens automatically at http://127.0.0.1:3000.
Tip: Option 3 loads the plugin for the current session only. Add a shell alias for convenience:
alias claude-ib='claude --plugin-dir /path/to/insight-blueprint'
# Start the server without plugin (zero-install)
uvx insight-blueprint --project /path/to/my-analysis
# Or install permanently
uv tool install insight-blueprint
insight-blueprint --project /path/to/my-analysis
When a new version is published, run the following from within Claude Code to pull the latest plugin (auto-update is off by default for third-party marketplaces):
/plugin marketplace update insight-blueprint-marketplace
/plugin update insight-blueprint@insight-blueprint-marketplace
See CHANGELOG.md for release notes.
For data-lineage tracking with tracked_pipe in your notebooks/scripts:
uv add insight-blueprint
This is optional but recommended for analysis pipeline transparency. MCP tools work without it.
insight-blueprint exposes 18 tools via the Model Context Protocol, allowing AI assistants to manage your analysis workflow:
| Category | Tools |
|---|---|
| Analysis Design | create_analysis_design, update_analysis_design, get_analysis_design, list_analysis_designs |
| Data Catalog | add_catalog_entry, update_catalog_entry, get_table_schema, search_catalog |
| Domain Knowledge | get_domain_knowledge, extract_domain_knowledge, save_extracted_knowledge, suggest_knowledge_for_design, suggest_cautions |
| Review Workflow | transition_design_status, save_review_comment, save_review_batch, get_review_comments |
| Project | get_project_context |
A browser-based dashboard (http://127.0.0.1:3000) with two tabs:
The plugin provides 9 analysis skills that are automatically available after installation:
/analysis-framing -- Explore available data and existing analyses to frame a hypothesis direction/analysis-design -- Guided workflow for creating hypothesis documents/analysis-journal -- Record reasoning steps during analysis (observations, evidence, decisions, questions)/analysis-reflection -- Structured reflection to draw conclusions or branch hypotheses/analysis-revision -- Guided revision workflow for addressing review comments/catalog-register -- Step-by-step data source registration/data-lineage -- Track data transformations and export lineage diagrams (Mermaid)/batch-analysis -- Overnight batch execution of queued designs (headless notebooks, self-review, journal recording)/premortem -- Pre-flight risk evaluation of queued designs with approval token issuance (gates /batch-analysis)Skills support both English and Japanese trigger phrases.
Skills chain together to support the full hypothesis-driven analysis lifecycle: