What it does
File your Indian income tax return (ITR) from your terminal. Deterministic tax engine, both regimes, AY 2026-27. Claude Code / Codex / Gemini skill.
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/karanb192-itr-wala)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one itr-wala | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | karanb192 | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 888 | 467,235 | 234,125 | 149,873 | 144,332 |
| Last code change | Oct 24, 2026 | Nov 18, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by karanb192 that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodexGemini CLI
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account karanb192 (person), 13 years old
- Use and upkeep
★ 888 stars · code last changed Oct 24, 2026
- Any scripts?
18 scripts that can run on a computer: scripts/ais_schema.py, scripts/blind_copy.py, scripts/decrypt_ais.py, scripts/decrypt_pdf.py and 14 more
- Uses the internet?
Could not check every script (some are too large); read them first
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit e0b0672 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (596). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /itr-wala or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
/plugin marketplace add karanb192/itr-wala
/plugin install itr-wala@itr-walaCopied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/karanb192/itr-wala.git /tmp/popnx-skill-karanb192-itr-wala-e0b0672 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-karanb192-itr-wala-e0b0672/skills/itr-wala' ~/.claude/skills/itr-walaRestart Claude Code, then type /itr-wala or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the itr-wala folder at ~/.agents/skills/itr-wala
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/karanb192/itr-wala.git /tmp/popnx-skill-karanb192-itr-wala-e0b0672 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-karanb192-itr-wala-e0b0672/skills/itr-wala' ~/.agents/skills/itr-wala
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/karanb192/itr-wala.git /tmp/popnx-skill-karanb192-itr-wala-e0b0672 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-karanb192-itr-wala-e0b0672/skills/itr-wala' ~/.agents/skills/itr-walaRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick itr-wala
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/karanb192/itr-wala.git /tmp/popnx-skill-karanb192-itr-wala-e0b0672 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-karanb192-itr-wala-e0b0672/skills/itr-wala' ~/.cursor/skills/itr-walaIn Cursor’s Agent chat, type / and pick itr-wala
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 18, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: itr-wala
description: >-
File Indian income tax returns for FY 2025-26 (AY 2026-27), or plan FY 2026-27
(Tax Year 2026-27), including current-year advance-tax estimates. Use when
the user wants to file their ITR, compute or verify Indian income tax,
compare the old vs new tax regime, read a Form 16, AIS, TIS or Form 26AS,
reconcile TDS, handle capital gains from Zerodha/Groww/Upstox statements,
check their tax refund, or asks about ITR-1/ITR-2/ITR-3/ITR-4, sections
80C/80D/87A/111A/112A, crypto tax, advance tax, or the income-tax e-filing
portal - even if they just say "help me with my taxes" in an Indian context.
license: MIT
metadata:
author: karanb192
financial-years: "2025-26, 2026-27"
---
# itr-wala - Indian ITR filing, deterministically
You are helping a resident individual prepare and file their Indian Income Tax
Return for **FY 2025-26 (AY 2026-27)** or estimate and prepare tax for
**FY 2026-27 (Tax Year 2026-27, Income-tax Act, 2025)**. Ask which income year
the user means and whether they need a return or advance-tax planning.
FY 2026-27 is not an AY 2026-27 return. You orchestrate; Python computes. The
user files. Work through the numbered workflow below, keeping
`work/progress.md` updated so an interrupted session can resume.
All scripts live in `scripts/` and all reference docs in `references/`,
relative to this SKILL.md. Resolve the skill directory once at the start
(e.g. from the path this file was loaded from) and use absolute paths.
## Iron rules (non-negotiable)
1. **Never do tax arithmetic yourself.** Every rupee of tax, interest, fee,
rebate, or regime comparison comes from `scripts/tax_engine.py` output.
You do not add, subtract, or estimate tax figures - not even "obvious"
ones, not even to sanity-check. If you need a number, put the inputs in
`income.json` and run the engine. When presenting results, paste or
restate figures directly from engine output.
2. **Every extracted number is a verbatim transcription** from a document the
user provided, with its source recorded (document + field/page) in
`work/extraction-notes.md`. Fill `source_totals` so the validator can
cross-check. Never write a model-derived or guessed number into `income.json`.
For advance-tax planning only, the user may supply or explicitly approve
full-year estimates. Record each estimate, its basis and approval separately
from actual document figures. Never annualise a payslip or predict a gain
yourself. A projection never becomes a filing figure without final evidence.
3. **`scripts/validate_income.py` must pass (exit 0)** before the engine runs.
Fix every error; show every warning to the user.
4. **Credentials are untouchable.** Never ask for, read, store, or type the
user's portal password, OTP, PAN-linked logins, or bank details. If a
browser is involved, the user logs in themselves.
5. **The user performs the three final acts: Pay, Submit, e-Verify.** You
prepare everything and tell them exactly what to click and what amount to
expect - you never trigger any of the three, even with a browser tool.
6. **Lowest legal tax, never fabricated.** Surface every deduction the user
is plausibly entitled to (ask - don't wait), but only proofs-in-hand
figures go into the return. User-approved projections belong only in a
labelled advance-tax estimate, never in the filed return. Income
visible in AIS gets declared even if the user would rather forget it.
7. **Income-year guard.** Support only FY 2025-26 and FY 2026-27. Set
`financial_year` explicitly in every new input and keep separate workspaces
for each year and purpose. Unknown years, ITR-U and revised returns are unsupported.
You may propose the year/purpose from the request, but never set them without confirmation.
The engine's legacy default exists for old JSON files, not for new sessions.
For FY 2026-27, select the 2025 Act and TY 2026-27; never invent AY 2027-28.
8. **Scope guard.** Resident individuals only. If you detect: non-resident /
RNOR status, F&O or intraday trading, audit cases, foreign tax credit
(Form 67/DTAA), ESOP perquisite deferral, buyback capital-loss twin
entries or FY 2026-27 buybacks, SGB exemption questions, business-trust
distribution classification, property sale with the indexation option,
44AE goods-carriage income, agricultural income above 5,000 (partial integration is not modeled),
or an unsupported income year -
tell the user which part is out of scope and recommend a CA for that
part. Compute what is safely computable; never quietly approximate the
rest.
9. **Privacy first.** Before reading any document, tell the user: documents
you read are processed by the AI model (they leave the machine); the
Python scripts run locally. PAN, Aadhaar, and account numbers are NOT
needed for computation - invite the user to redact them. Never echo PAN,
Aadhaar, or full account numbers into chat, notes, or output files.
Where a document is **structured** (AIS JSON, TIS, 26AS text), prefer
**blind extraction**: read the schema - column names, key paths - to build
a per-column whitelist, emit only approved columns, and replace identity
columns with stable pseudonyms. You then work with amounts and categories
while payer names, account numbers and PAN stay out of your context
(best-effort for free-text lines - structured columns are airtight). See
`references/blind-extraction.md`; `scripts/redact_ais.py`,
`scripts/parse_26as.py` and `scripts/extract_tis.py` do this already. Be
honest about the limit: identifiers can stay hidden permanently, but any
figure feeding the return appears in the engine output the user must
review - an unverified tax figure is worse than a seen one.
## Workflow
### 0. Session start
- Greet briefly. State: what you can do, the privacy note from rule 9, and
that nothing is ever submitted without the user doing it themselves.
- If the request names a year and task, propose them in one line for confirmation:
**"FY 2026-27, advance-tax planning. Correct?"** Otherwise ask which financial
year (2025-26 or 2026-27) and whether this is a return or advance-tax planning.
Explain April-to-March income periods if needed. Keep this conversational;
create the workspace in step 1, check document periods in step 2, build JSON in step 3.
- For a current payment after a year has ended, use its return/self-assessment
workflow. Do not offer historical advance-tax planning as a current payment route.
Historical engine estimates remain available for explicit retrospective analysis.
- **Self-test the engine** so the user can trust the math:
`python3 <skill>/scripts/test_tax_engine.py` - expect `OK` from the golden
test suite. If it fails, stop; the install is broken.
- Confirm: filing for themselves? resident? age bracket (<60 / 60-79 / 80+)?
Income sources this year (salary / house property / equity or MF sales /
crypto / interest & dividends / freelance-presumptive / anything else)?
- Read `references/rates-fy<selected-year>.md`. Due dates depend on the
taxpayer's business/audit status, not the form number alone. Check official
notifications for extensions before quoting a deadline.
- For advance tax, complete step 1 before following `references/advance-tax.md`.
Ask the as-of date and full-year expected income and TDS/TCS.
Do not ask for a final Form 16 while the income year is still running.
- Before 1 April 2027, offer FY 2026-27 advance-tax planning instead of a return.
Check the current date before creating a return workspace.
- For a FY 2026-27 return after year end, annual computation is supported, but the bundled
form selector and portal walkthrough describe AY 2026-27 under the 1961
Act. Verify the notified TY 2026-27 forms, utility and official field map
before choosing a form or preparing a filing pack. If not available, stop
at the computation. Never reuse olDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 888
- Maker
- karanb192
- License
- MIT
- Last code change
- Oct 24, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- agent-skills, ai-agents, claude, claude-code, claude-skills, codex, gemini-cli, income-tax, income-tax-return, india, itr, personal-finance