tax-register – Marketing & SEO skill for AI agents
Tax register: sales and purchase tax, withholding deducted and received, net payable, filing due date and days remaining. Use for tax compliance.
Install the tax-register skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/tax-register-8b92f.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /tax-register – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/tax-register-8b92f.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $tax-register – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/tax-register-8b92f.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /tax-register – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/tax-register-8b92f.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /tax-register – then describe the task you want done.
SKILL.md content
Tax Register
What it is: Tax collected, tax paid, withholding and filing deadlines per period.
Overview
Works out the smallest useful Tax Register setup for the business in front of it, then
builds it only when asked. The default output is a short recommendation, not a
spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on
request, from one field list so they cannot drift apart.
Layer: Layer 7: Protect. Fits: Starter stage. Table code: n/a.
When to Use This Skill
- tax register
- gst tracker
- vat records
- tax filing calendar
Also use it when the user says "tax collected, tax paid, withholding and filing deadlines per period", or describes the same process happening in a
spreadsheet, a document or someone inboxes.
Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces
empty templates only - it never holds or processes real employee or customer data.
How It Works
Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.
Step 1 - Identify intent
Read the request and pick the intent before asking anything.
- "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
- "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
- "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
- "how do I ..." -> advice question; answer directly and offer the build only if it helps.
Ask only if this is the highest-value missing fact; otherwise proceed without an opener:
> Q: Which taxes are you registered for?
Step 2 - Ask only what is missing
Skip anything the user already answered, in any earlier message. Ask the rest one at a
time, and stop as soon as the remaining answers would not change the output.
- Taxes - Which taxes? / How many periods? / Which entities?
- Data - Invoice data available? / Where is it? / Any missing receipts?
- Filing - Who files? / Internal or accountant? / Deadlines recurring?
- Current process - Is it tracked now? / Accountant or spreadsheet? / What gets missed?
- Outcome - What do you need? / A register, a data extract or both?
Never invent an answer. If the user does not know, record it as unknown and carry on.
Step 3 - Hold the internal context
Hold the answers in this shape. It stays internal - it is not shown to the user unless
they ask, and it never carries a value the user did not give.
module: tax-register
intent: null # setup | advice | review | fix | build | convert | export
scale: null # Starter | Growth | Scale, only if the answer changes it
areas:
"Taxes": null
"Data": null
"Filing": null
"Current process": null
"Outcome": null
requested_outputs: [] # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: [] # only what the user actually said
open_questions: [] # the unanswered ones, in the order worth askingStep 4 - Recommend the smallest workflow
If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.
Recommended approach: Keep the tax register as a record of periods, amounts and filing status, and let the accountant or filing tool do the calculation.
Why this one: A register tracks evidence and status; it does not determine tax treatment, eligibility, rates or filing obligations. An accountant must validate those inputs as well as arithmetic.
Workflow: Period opened → Source data recorded → Amount entered → Filed → Reconciled
Step 5 - Build only on request
Once the user asks for it, derive the fields from the confirmed context and emit the
requested artifacts. For machine-readable text, keep prose outside the data; for files,
provide a usable link. Report material validation failures or limitations separately.
**A selected Notion output is rendered by notion-manual-import, so route the
Notion step there.** When the user selects Notion, hand that step to
@notion-manual-import: it holds the CSV, the property
mapping, the import steps and the verification checklist, and it renders the Field
Reference below instead of defining a table of its own. Do not restate the mapping
here and do not improvise the import steps. Manual CSV and mapping outputs need no
connection. For requested workspace changes, follow the shared contract: verify actual
tool access and the target before writing. A user saying "connected" is not tool evidence.
Never ask for a Notion password or token.
For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the
text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user
requests a workbook.
A CSV carries no types, so after it, name the columns
that need a number, date or currency format applied.
Tax Record,Tax Type,Tax Period,Period Start,Period End,Tax Collected on Sales,Tax Paid on Purchases,Withholding Tax Deducted,Withholding Tax Paid to Us,Net Tax Payable,Currency,Filing Due Date,Filed Date,Payment Date,Filing Reference,Prepared By,Reviewed By,Days to Due,Status,Notes,Tax ID
TAX-2026-03,GST,2026-03,2026-03-01,2026-03-31,354000.00,82000.00,2700.00,2700.00,272000.00,INR,2026-04-15,2026-04-15,2026-04-15,TAX-2026-03-Q1,Example Preparer,Example Reviewer,0,Filed,Filed with the accountant; working papers saved.,CREATE TABLE tax_register (
tax_record VARCHAR(255),
tax_type VARCHAR(100) NOT NULL,
tax_period VARCHAR(255),
period_start DATE NOT NULL,
period_end DATE NOT NULL,
tax_collected_on_sales NUMERIC(14,2) NOT NULL,
tax_paid_on_purchases NUMERIC(14,2) NOT NULL,
withholding_tax_deducted NUMERIC(14,2) NOT NULL,
withholding_tax_paid_to_us NUMERIC(14,2) NOT NULL,
net_tax_payable NUMERIC(14,2) NOT NULL,
currency VARCHAR(255) NOT NULL,
filing_due_date DATE NOT NULL,
filed_date DATE,
payment_date DATE,
filing_reference VARCHAR(255),
prepared_by VARCHAR(255),
reviewed_by VARCHAR(255),
days_to_due INTEGER,
status VARCHAR(100) NOT NULL,
notes TEXT,
tax_id SERIAL PRIMARY KEY,
created_at TIMESTAMP DEFAULT NOW(),
updated_at TIMESTAMP DEFAULT NOW()
);
CREATE INDEX idx_tax_register_status ON tax_register (status);{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "Tax Register",
"type": "object",
"additionalProperties": false,
"properties": {
"Tax Record": { "type": "string" },
"Tax Type": { "type": "string" },
"Tax Period": { "type": "string" },
"Period Start": { "type": "string", "format": "date" },
"Period End": { "type": "string", "format": "date" },
"Tax Collected on Sales": { "type": "number" },
"Tax Paid on Purchases": { "type": "number" },
"Withholding Tax Deducted": { "type": "number" },
"Withholding Tax Paid to Us": { "type": "number" },
"Net Tax Payable": { "type": "number" },
"Currency": { "type": "string" },
"Filing Due Date": { "type": "string", "format": "date" },
"Filed Date": { "type": "string", "format": "date" },
"Payment Date": { "type": "string", "format": "date" },
"Filing Reference": { "type": "string" },
"Prepared By": { "type": "string" },
"Reviewed By": { "type": "string" },
"Days to Due": { "type": "integer" },
"Status": { "type": "string" },
"Notes": { "type": "string" },
"Tax ID": { "type": "integer" }
},
"required": [
"Tax Type",
"Period Start",
"Period End",
"Tax Collected on Sales",
"Tax Paid on Purchases",
"Withholding Tax Deducted",
"Withholding Tax Paid to Us",
"Net Tax Payable",
"Currency",
"Filing Due Date",
"Status"
]
}| CSV column | Notion property | Set after import |
|---|---|---|
| Tax Record | Title | Use as the database title |
| Tax Type | Select (add options after import) | Convert to Select, add options: "GST", "VAT", "TDS", "TCS", "Service Tax", "Income Tax", "Withholding" |
| Tax Period | Text | Leave as Text |
| Period Start | Date | Convert to Date |
| Period End | Date | Convert to Date |
| Tax Collected on Sales | Number (format: currency) | Convert to Number, set format to Currency |
| Tax Paid on Purchases | Number (format: currency) | Convert to Number, set format to Currency |
| Withholding Tax Deducted | Number (format: currency) | Convert to Number, set format to Currency |
| Withholding Tax Paid to Us | Number (format: currency) | Convert to Number, set format to Currency |
| Net Tax Payable | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| Filing Due Date | Date | Convert to Date |
| Filed Date | Date | Convert to Date |
| Payment Date | Date | Convert to Date |
| Fil… (full content is in the download package)
Related skills
- telegram-channel-ads – Vet and price ad posts in Telegram channels: reach benchmarks by size, topic and…
- tools-page-seo-optimizer – Framework-agnostic SEO workflow for any site with multiple tool, product, or feature…
- unslop-commit – Rewrites commit messages so they sound like a careful human engineer wrote them. Strips…
- usage-based-pricing – Design pricing models that developers understand, accept, and can predict. Trigger…
- windows-ad – Authorized Active Directory and Windows identity attacks: Kerberos abuse, AD CS…
- wordpress-centric-high-seo-optimized-blogwriting-skill – Generate clean, human-sounding, SEO-optimized WordPress blog posts with optional Yoast…
- ad-creative – When the user wants to generate, iterate, or scale ad creative — headlines…
- ad-creative – When the user needs to generate, iterate, or scale ad creative for paid advertising. Use…