From takshashila-scholar
Guides analysts through Indian government budget analysis: document identification, data extraction, ratio computation, chart specs, and story angles. Hands off to writing skills.
How this skill is triggered — by the user, by Claude, or both
Slash command
/takshashila-scholar:budget-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide an analyst through an Indian budget analysis — from identifying the right documents to producing a structured data summary with computed ratios, chart specifications, and story angles. The writing step is handled by the op-ed, policy brief, or discussion document skills.
Guide an analyst through an Indian budget analysis — from identifying the right documents to producing a structured data summary with computed ratios, chart specifications, and story angles. The writing step is handled by the op-ed, policy brief, or discussion document skills.
Do not use for revenue/tax analysis (use causal-loop-analysis or hypothesis-development for fiscal policy arguments).
Budget documents are large, inconsistently formatted, and written for auditors, not analysts. The skill adds value at three points:
The CLI version additionally integrates with:
/parliament-search — for CAG reports, Finance Committee findings, and PAC reports that contextualise the budget datadefuddle — to fetch and parse budget documents directly from government URLsPresent these after gathering scope. Analyst picks the one that fits their question.
| Frame | Core question | Typical use |
|---|---|---|
| Time Series | Is spending growing or shrinking? Is budgeted money actually spent? | Track a ministry or scheme across 5–7 years; BE vs Actuals trend |
| Component Breakdown | Within this budget head, what are the sub-parts? What share does each hold? | Decompose a ministry into schemes, or a scheme into object heads (salary / capital / transfers) |
| Scheme Tracking | Is a specific scheme receiving and utilising its promised allocation? | PLI, MGNREGS, PM-KISAN, Jal Jeevan Mission, PM Awas Yojana |
| Cross-State Comparison | How does one state compare to peers on the same sector? | Education spend as % of GSDP: Karnataka vs Tamil Nadu vs UP |
Multi-tier modifier: Health, education, agriculture, water, and other Concurrent List subjects draw spending from both Union and State budgets. If the analyst names such a domain, ask: Union-only, State-only, or combined? For combined, guide extraction from both sources and compute the consolidated picture (Union transfers + State own funds).
Ask in one message:
Show the table above. Ask which frame fits their question. Wait for their choice.
Tell the analyst exactly where to find the data. Use defuddle to fetch and preview the relevant government page if the analyst does not have the file.
Union Budget (indiabudget.gov.in):
| Need | Document | Location |
|---|---|---|
| Ministry-wise totals BE/RE/Actuals | Expenditure Profile | Budget documents → Expenditure Profile |
| Scheme-level breakdown | Statement 14 | Expenditure Budget Vol 2 → Statement 14 |
| Revenue side | Receipt Budget | Budget documents → Receipt Budget |
| Quick aggregates, % of GDP | Budget at a Glance | Budget documents → Budget at a Glance |
State Budgets (state finance department websites):
| Need | Document |
|---|---|
| Aggregates + % of GSDP | Budget at a Glance |
| Department + object-head breakdown | Detailed Demands for Grants |
| Previous years' actuals | Annual Financial Statement |
Key state URLs: Karnataka (finance.karnataka.gov.in), Maharashtra (finance.maharashtra.gov.in), Tamil Nadu (tnbudget.tn.gov.in), Rajasthan (finance.rajasthan.gov.in), Uttar Pradesh (budget.up.nic.in). For others: search "[state name] state budget finance department".
CLI advantage — fetch directly: If the analyst provides a URL, use defuddle parse <url> --md to extract the table rather than asking them to copy-paste.
Run /parliament-search [domain] budget to find:
These often contain the most analytical content: not just what was spent but whether it was spent effectively.
Say: "Paste whatever you have — raw PDF copy-paste, an Excel table, CSV figures. Any format is fine."
Extract a clean structured table. Present it: "Here is what I understood from your data:" followed by the table. Ask: "Does this look right? Is anything missing?" Do not compute ratios until the analyst confirms.
For large files: extract the relevant section only. Government budget spreadsheets can be 50,000+ rows — ask the analyst to paste only the ministry or scheme rows they need.
| Ratio | Formula | What it reveals |
|---|---|---|
| BE → RE revision | (RE − BE) / BE × 100 | Mid-year reprioritisation — a large negative means the ministry lost funds |
| RE → Actuals utilisation | Actuals / RE × 100 | Implementation capacity — below 85% is a consistent underperformer |
| YoY nominal growth | (This year − Last year) / Last year × 100 | Whether allocation is growing in real terms |
| % of total budget | Amount / Total budget × 100 | Political priority signal |
| % of GDP / GSDP | Amount / GDP × 100 | International comparability; use nominal GDP from Economic Survey |
| Capital vs revenue split | Capital / Total × 100 | Investment vs consumption; critical for infrastructure ministries |
Flag anomalies:
Recommend 2–3 charts. State exact axes, units, and what to annotate. The analyst builds these in R, Excel, or Datawrapper.
| Frame | Recommended chart | Key details |
|---|---|---|
| Time Series | Grouped bar (BE/RE/Actuals per FY) + line overlay (% of GDP) | Dual y-axis; annotate policy events (scheme launch, budget cut) |
| Component Breakdown | Horizontal bar sorted descending; or stacked bar across years | Label largest component; show % not just absolute |
| Scheme Tracking | Line chart per scheme across years | Annotate years with sharp changes |
| Cross-State | Dot plot or horizontal bar with national average marked | Label state names; sort by value |
For R users, suggest ggplot2 with geom_col() + geom_line() for the dual-axis time series. For Datawrapper, the grouped bar chart type handles BE/RE/Actuals grouping well.
Produce 3–5 evidence-grounded story angles. Each should be one sentence that could become a headline or lead paragraph. Be specific to the numbers:
Not: "Defence spending increased." Yes: "Defence capital expenditure grew 18% YoY in FY2025 but utilisation fell to 78%, the lowest in five years — suggesting India is budgeting ambition it lacks the capacity to execute."
End with: "Take this data summary and story angles to the op-ed-writing skill for a newspaper piece, the policy-brief-writing skill for a structured recommendation memo, or the discussion-document-writing skill for a longer analysis. Store budget document sources in Zotero before you close the files."
| Tool | When to use |
|---|---|
defuddle parse <url> --md | Fetch and parse a government budget page or PDF URL directly |
/parliament-search [domain] budget | Find CAG reports, PAC findings, Finance Committee reports |
zotero-obsidian-bridge | Store extracted budget data as a citable source |
hypothesis-development | After identifying the story angle, sharpen it into a testable claim |
causal-loop-analysis | If the budget pattern reveals a structural problem (chronic underspending), map the causal loops |
op-ed-writing | Draft the newspaper piece from the story angles |
policy-brief-writing | Draft the structured recommendation memo |
discussion-document-writing | Draft the longer analytical piece |
A structured data summary containing:
The skill does not produce the final written piece.
npx claudepluginhub pranaykotas/takshashila-scholar --plugin takshashila-scholarAnalyzes YTD actuals vs budget workbook for pacing and variance. Pulls actuals from Carta MCP. Read-only analysis triggered by 'how are we doing' or 'pacing' queries.
Answers economic and financial data questions using FactIQ (worlddb) data: US indicators, international data, stocks, commodities, forex, and earnings-call transcripts. Generates charts, maps, reports, or direct answers.
Verifies facts, numbers, quotes, and statements against primary sources. Handles truthfulness checks, out-of-context quotes, metric decomposition, negative statements, and multi-source conflicts.