Library · Team · LangGraph · data-analysis
Data Analysis — LangGraph
Summarize pasted tables or CSV snippets into findings, caveats, and what to check next. Analysis only. (LangGraph stateful graph with a human checkpoint.)
Id: langgraph/data-analysis · Slug: data-analysis · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
What is this
Code for LangGraph. Summarize pasted tables or CSV snippets into findings, caveats, and what to check next. Analysis only. (LangGraph stateful graph with a human checkpoint.)
How this runtime fits
This LangGraph implementation is a graph-style runtime for the parent AI Team. Agent orchestration and multi-agent workflow language fit when nodes split work and gates; it is not automatically identical to every multi-agent system.
Parent AI Team: data-analysis · What is an AI Team?
What it does
Summarize pasted tables or CSV snippets into findings, caveats, and what to check next. Analysis only. (LangGraph stateful graph with a human checkpoint.)
Who for
Builders working on Analytics jobs who can run LangGraph themselves.
Need to run
- You will run this locally or on infra you control.
- No production credentials in prompts or committed files.
- Python 3.10+
- LangGraph in a venv
- Local model binder
How to use
- Install LangGraph in a venv (pin versions).
- Wire produce() to your local model client.
- Run the file once with Example in.
- Keep human_gate approval defaulting to False; enable revise only intentionally.
Limitations
- Not a substitute for professional legal, medical, or investment advice.
- Outputs can be wrong; human review required before publish or spend.
- Stage-1 Library items are free recipes — marketplace ready-to-use teams remain separate.
- Do not attach billing cloud LLM nodes without a human budget check.
Test status
Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
Files
graph_data_analysis.py— LangGraph nodes + interruptREADME.md— Run notes
Full prompt / config / code
Free. No sign-up. The full text is right here. Copy it, or take the file with you.
無料・登録不要。全文はこの下にあります。コピーするか、ファイルで持ち帰れます。
Download .md.md で持ち帰る How to run it動かし方 Fork itフォークする Results & questions結果・質問を書く
# graph_data_analysis.py — Data Analysis (LangGraph sketch)
# pip install langgraph langchain-core (pin yourself)
# Use a local chat model binder; do not embed secrets.
from typing import TypedDict, Literal
from langgraph.graph import StateGraph, END
SYSTEM = """You are a data analysis desk. Goal: findings from pasted numbers only.
RULES:
- Always emit ALL four OUTPUT sections.
- Never invent row values, dates, weekdays, or metrics not in the paste.
- Quote the exact cell values you use in each Key finding.
- Note blank/missing cells explicitly; do not fill blanks with guesses.
- Do not invent averages; if you cannot compute carefully write "not computed — needs human calc".
- Do not claim deploy/product events caused gold/market moves unless the paste states that link.
- If paste says SAMPLE/synthetic, say so in Dataset snapshot.
- Prefer max 5 accurate findings over 7 wrong ones.
- Do not invent rows. If math is approximate, say so.
- Call out sample size, missing fields, and selection bias.
- No trading/investment advice. No auto-spend recommendations.
- Charts described in text only unless user provides image.
OUTPUT:
1) Dataset snapshot
2) Key findings (max 7)
3) Caveats
4) Next checks / cuts to request"""
class State(TypedDict):
user_input: str
draft: str
approved: bool
notes: str
def produce(state: State) -> State:
# Pseudo: call your local model with SYSTEM + state["user_input"]
draft = "[MODEL OUTPUT PLACEHOLDER — wire your local LLM here]\n" + state["user_input"][:500]
return {**state, "draft": draft, "notes": "awaiting human"}
def human_gate(state: State) -> State:
# In real use: interrupt / input() / UI approval.
# Default False so nothing auto-publishes.
return {**state, "approved": False}
def route_after_gate(state: State) -> Literal["done", "revise"]:
return "done" if state.get("approved") else "done" # stage-1: always end after gate
g = StateGraph(State)
g.add_node("produce", produce)
g.add_node("human_gate", human_gate)
g.set_entry_point("produce")
g.add_edge("produce", "human_gate")
g.add_conditional_edges("human_gate", route_after_gate, {"done": END, "revise": "produce"})
app = g.compile()
if __name__ == "__main__":
out = app.invoke({"user_input": "PASTE_EXAMPLE_IN", "draft": "", "approved": False, "notes": ""})
print(out)
License as listed in the registry: free-use-at-own-risk. Use is at your own risk. BSV does not run it for you. What is open here
ライセンス(レジストリの記載どおり):free-use-at-own-risk。 利用は自己責任です。BSVが代わりに実行することはありません。何が開いているか
This job is also written for 6 other tools. See all 7 versions side by side.
この仕事は、ほかに 6 のツール向けの版があります。7 版を並べて見る。
Example in
Paste: day,signups,paid Mon,40,2 Tue,38,1 Wed,22,1 Thu,21,0 Fri,25,1 Note: Wed deploy.
Example out
Snapshot: 5 weekdays; Wed deploy coincides with signup drop. Findings: Signups fell ~45% Wed–Thu vs Mon–Tue; paid sparse (n small). Caveats: one week; no traffic denominator. Next: traffic + error logs around deploy.
Model / runtime notes
Graph includes an explicit human checkpoint. Stage-1 ends after gate (no infinite revise loop).
Canonical Team
Parent: data-analysis
· implementation_id: langgraph/data-analysis
GitHub source
teams/data-analysis/langgraph (path in the BSV team registry repository) · commit eb87e8e049fdf9908e438305ff827c7b617505b5
· license: free-use-at-own-risk
Structural check: PASS · env: structural (structural only — does not set Verified)
Related Library items
Related marketplace Team pages
Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.
- Numbers Desk (marketplace Team page — separate entity)
- Use Numbers (marketplace Team page — separate entity)
Run this task locally · LangGraph team runner
The BSV team runner runs this task on a local model (LM Studio or Ollama), checks the required sections and saves only after your approval. Paste the team prompt from the full-text page into prompts/data-analysis.txt.
BSVのチームランナーで、この仕事をローカルモデル(LM StudioまたはOllama)で動かせます。必要な項目を確認し、あなたが承認したときだけ保存します。全文ページのプロンプトを prompts/data-analysis.txt に貼り付けて使います。
python runner.py --task data-analysis --input notes.md
Not runtime tested by BSV.
BSVでは実行検証をしていません。