Agent skill

Tds Booking Payment

by sickn33 in sickn33/agentic-awesome-skills

TDS register: payee PAN, payment nature, rate and amount deducted, deposit date and challan reference, return filing and ledger variance.

MITAuto-check passed

Install Tds Booking Payment

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill tds-booking-payment -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills tds-booking-payment --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tds-booking-payment .claude/skills/tds-booking-payment && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tds-booking-payment
GitHub stars
47k
Used in
1 other repo
Token cost
~5k tokens
SKILL.md length
1,847 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

TDS register: payee PAN, payment nature, rate and amount deducted, deposit date and challan reference, return filing and ledger variance.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches json-schema.org

What it does

Tds Booking Payment is an agent skill from sickn33/agentic-awesome-skills. TDS register: payee PAN, payment nature, rate and amount deducted, deposit date and challan reference, return filing and ledger variance. Use for TDS compliance.

Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

Example prompts

  • “/tds-booking-payment”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, csv, sql, json and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • json-schema.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tds Booking Payment loads about 5k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 1,847 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,847 words, ~5,028 tokens.

Download SKILL.mdSave it as .claude/skills/tds-booking-payment/SKILL.md (or your agent's skills folder).
name
tds-booking-payment
description
TDS register: payee PAN, payment nature, rate and amount deducted, deposit date and challan reference, return filing and ledger variance. Use for TDS compliance.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, accounting, audit, finance, database, csv, notion, sql, tds
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

TDS Booking & Payment

What it is: Tax deducted at source, deposited on time, filed and reconciled to the ledger.

Overview

Works out the smallest useful TDS Booking & Payment 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.

Reconcile at least monthly. A deduction that is recorded at the time of payment and left unreconciled until the return is due is how a liability drifts away from the challan.

This skill does not determine the rate that applies, does not file returns, and is not tax advice. Rates and deadlines vary by country and change. The rate and the deadline come from a qualified tax professional; this only holds the record.

Layer: Layer 6: Statutory. Fits: Starter stage. Table code: n/a.

When to Use This Skill

  • tds register
  • tds deposit tracker
  • withholding tax log
  • tds return working

Also use it when the user says "tax deducted at source, deposited on time, filed and reconciled to the ledger", 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 payments are you deducting TDS on today?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

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.

  • Nature of payment - Which payment types are in scope? / How many vendors are affected? / Any thresholds?
  • Rates - Where do the rates come from? / Are PANs collected? / Who confirms the rate?
  • Deposits - How are you depositing? / Which account? / When is the next deadline?
  • Returns - Who files? / Which periods? / Is it monthly or quarterly?
  • Outcome - What do you need? / A deduction register, a deposit tracker 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.

yaml
module: tds-booking-payment
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Nature of payment": null
  "Rates": null
  "Deposits": null
  "Returns": 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 asking
Step 4 - Recommend the smallest workflow

Build an already requested artifact without asking again. For advice-only requests, give a short recommendation and offer the relevant artifact.

Recommended approach: One record per deduction and payee, carrying the gross, the rate applied, the tax deducted, the deposit, the return and the reconciliation result for the period.

Why this one: TDS is four separate obligations - deduct, deposit, file, reconcile - and they fail in different places. One record per deduction keeps all four on the same row so a missed deposit shows up as a status, not as a surprise at filing time.

Workflow: Transaction identified → Rate applied → TDS deducted → Ledger updated → Deposited before the deadline → Return filed → Ledger reconciled at least monthly

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.

csv
TDS Record Number,Tax Period,Nature of Payment,Payee Name,Payee PAN,Transaction Reference,Payment Date,Gross Payment/Base,TDS Rate %,TDS Deducted,Deducted On,TDS Payable Ledger,Deposit Date,Challan/Bank Reference,Amount Deposited,Return Filed Date,Return Reference,Ledger Reconciliation,Variance Amount,Reconciliation Frequency,Prepared By,Reviewed By,Status,Notes,TDS ID
TDS-2026-0194,2026-08,Professional Fees,Pixelworks Studio,29ABCDE1234F1Z5,EXP-2026-0338,2026-08-18,32500.00,10,3250.00,2026-08-18,TDS Payable - Professional Fees,2026-09-15,CHL-2026-0912,48200.00,2026-10-15,TDS-Q2-2026-PF,Variance,325.00,Monthly,Sneha Iyer,Vikram Singh,In progress,Deposit and return agree to the challan; ledger short by 325.00 and under investigation.,
sql
CREATE TABLE tds_booking_payment (
  tds_record_number VARCHAR(255),
  tax_period VARCHAR(255),
  nature_of_payment VARCHAR(100) NOT NULL,
  payee_name VARCHAR(255),
  payee_pan VARCHAR(255),
  transaction_reference VARCHAR(255),  -- relation -> target record
  payment_date DATE NOT NULL,
  gross_payment_base NUMERIC(14,2) NOT NULL,
  tds_rate_pct NUMERIC NOT NULL,
  tds_deducted NUMERIC(14,2) NOT NULL,
  deducted_on DATE,
  tds_payable_ledger VARCHAR(255),
  deposit_date DATE,
  challan_bank_reference VARCHAR(255),
  amount_deposited NUMERIC(14,2) NOT NULL,
  return_filed_date DATE,
  return_reference VARCHAR(255),
  ledger_reconciliation VARCHAR(100) NOT NULL,
  variance_amount NUMERIC(14,2) NOT NULL,
  reconciliation_frequency VARCHAR(100) NOT NULL,
  prepared_by VARCHAR(255),
  reviewed_by VARCHAR(255),
  status VARCHAR(100) NOT NULL,
  notes TEXT,
  tds_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_tds_booking_payment_status ON tds_booking_payment (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "TDS Booking & Payment",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "TDS Record Number": { "type": "string" },
      "Tax Period": { "type": "string" },
      "Nature of Payment": { "type": "string" },
      "Payee Name": { "type": "string" },
      "Payee PAN": { "type": "string" },
      "Transaction Reference": { "type": "string" },
      "Payment Date": { "type": "string", "format": "date" },
      "Gross Payment/Base": { "type": "number" },
      "TDS Rate %": { "type": "number" },
      "TDS Deducted": { "type": "number" },
      "Deducted On": { "type": "string", "format": "date" },
      "TDS Payable Ledger": { "type": "string" },
      "Deposit Date": { "type": "string", "format": "date" },
      "Challan/Bank Reference": { "type": "string" },
      "Amount Deposited": { "type": "number" },
      "Return Filed Date": { "type": "string", "format": "date" },
      "Return Reference": { "type": "string" },
      "Ledger Reconciliation": { "type": "string" },
      "Variance Amount": { "type": "number" },
      "Reconciliation Frequency": { "type": "string" },
      "Prepared By": { "type": "string" },
      "Reviewed By": { "type": "string" },
      "Status": { "type": "string" },
      "Notes": { "type": "string" },
      "TDS ID": { "type": "integer" }
  },
  "required": [
      "Nature of Payment",
      "Payment Date",
      "Gross Payment/Base",
      "TDS Rate %",
      "TDS Deducted",
      "Amount Deposited",
      "Ledger Reconciliation",
      "Variance Amount",
      "Reconciliation Frequency",
      "Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| TDS Record Number | Title | Use as the database title |
| Tax Period | Text | Leave as Text |
| Nature of Payment | Select (add options after import) | Convert to Select, add options: "Professional Fees", "Contractor Payment", "Rent", "Salary", "Commission", "Interest", "Contract Payment", "Other" |
| Payee Name | Text | Leave as Text |
| Payee PAN | Text | Leave as Text |
| Transaction Reference | Relation (link to the target database) | Convert to Relation, link to the target database |
| Payment Date | Date | Convert to Date |
| Gross Payment/Base | Number (format: currency) | Convert to Number, set format to Currency |
| TDS Rate % | Number | Convert to Number |
| TDS Deducted | Number (format: currency) | Convert to Number, set format to Currency |
| Deducted On | Date | Convert to Date |
| TDS Payable Ledger | Text | Leave as Text |
| Deposit Date | Date | Convert to Date |
| Challan/Bank Reference | Text | Leave as Text |
| Amount Deposited | Number (format: currency) | Convert to Number, set format to Currency |
| Return Filed Date | Date | Convert to Date |
| Return Reference | Text | Leave as Text |
| Ledger Reconciliation | Select (add options after import) | Convert to Select, add options: "Reconciled", "Variance", "Pending" |
| Variance Amount | Number (format: currency) | Convert to Number, set format to Currency |
| Reconciliation Frequency | Select (add options after import) | Convert to Select, add options: "Monthly", "Quarterly" |
| Prepared By | Text | Leave as Text |
| Reviewed By | Text | Leave as Text |
| Status | Select (add options after import) | Convert to Select, add options: "Not started", "In progress", "Blocked", "Done", "Cancelled" |
| Notes | Text | Leave as Text |
| TDS ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

#FieldTypeSQLJSON SchemaNotionCSV example
1TDS Record NumbertextVARCHAR(255)stringTextTDS-2026-0194
2Tax PeriodtextVARCHAR(255)stringText2026-08
3Nature of PaymentselectVARCHAR(100)stringSelect (add options after import)Professional Fees
4Payee NametextVARCHAR(255)stringTextPixelworks Studio
5Payee PANtextVARCHAR(255)stringText29ABCDE1234F1Z5
6Transaction ReferencerelationVARCHAR(255)stringRelation (link to the target database)EXP-2026-0338
7Payment DatedateDATEstring, format: dateDate2026-08-18
8Gross Payment/BasecurrencyNUMERIC(14,2)numberNumber (format: currency)32500.00
9TDS Rate %numberNUMERICnumberNumber10
10TDS DeductedcurrencyNUMERIC(14,2)numberNumber (format: currency)3250.00
11Deducted OndateDATEstring, format: dateDate2026-08-18
12TDS Payable LedgertextVARCHAR(255)stringTextTDS Payable - Professional Fees
13Deposit DatedateDATEstring, format: dateDate2026-09-15
14Challan/Bank ReferencetextVARCHAR(255)stringTextCHL-2026-0912
15Amount DepositedcurrencyNUMERIC(14,2)numberNumber (format: currency)48200.00
16Return Filed DatedateDATEstring, format: dateDate2026-10-15
17Return ReferencetextVARCHAR(255)stringTextTDS-Q2-2026-PF
18Ledger ReconciliationselectVARCHAR(100)stringSelect (add options after import)Variance
19Variance AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)325.00
20Reconciliation FrequencyselectVARCHAR(100)stringSelect (add options after import)Monthly
21Prepared BytextVARCHAR(255)stringTextSneha Iyer
22Reviewed BytextVARCHAR(255)stringTextVikram Singh
23StatusselectVARCHAR(100)stringSelect (add options after import)In progress
24Noteslong_textTEXTstringTextDeposit and return agree to the challan; ledger short by 325.00 and under investigation.
25TDS IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (720 more words)Show less

Select Options

Nature of Payment

Professional Fees | Contractor Payment | Rent | Salary | Commission | Interest | Contract Payment | Other

Ledger Reconciliation

Reconciled | Variance | Pending

Reconciliation Frequency

Monthly | Quarterly

Status

Not started | In progress | Blocked | Done | Cancelled

Relations

Link fields: Transaction Reference

Examples

Prompt

We deduct TDS on a few vendor payments and only find out at filing that the deposit is short.

Context first - one question per message, nothing already answered:

Q: Which payments are in scope? A: Professional fees and rent, mostly.

Q: Where do the rates come from? A: Our accountant sends them each year.

Q: Who files the return? A: The same accountant, quarterly.

Recommended next step - offered, not built:

One record per deduction and payee, carrying the gross, the rate applied, the tax deducted, the deposit, the return and the reconciliation result for the period.

Workflow: Transaction identified → Rate applied → TDS deducted → Ledger updated → Deposited before the deadline → Return filed → Ledger reconciled at least monthly

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • Record the rate that was actually applied, not the rate you expected. They are not always the same.
  • Link Transaction Reference to the expense or payment that carried the deduction. An unlinked deduction is the first thing a reviewer asks about.
  • Reconcile at least monthly, even when the return is quarterly. The monthly check is what makes the quarterly filing boring.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not compute TDS, deposit anything or file anything.
  • It does not determine the applicable rate, does not file returns, and it is not tax advice. Rates and deadlines vary by country and change.
  • It does not know the payment thresholds, the higher-rate conditions or the PAN exceptions. Those come from a qualified tax professional.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, payee PANs, bank details or challan data. Placeholders only.
  • Payee PAN data is sensitive. Collect only what the return needs, and mask it elsewhere.
  • Label example rows as synthetic, and keep account numbers masked.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If the user pastes real payee or employee data, generate the template and tell them to delete the pasted data from the conversation.
  • A missed deposit or a wrong rate needs a qualified tax professional before anything is filed or paid.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: the deduction was recorded but the deposit challan never attached. Solution: leave Deposit Date empty rather than guessing it, and set Status to Blocked until the challan exists.
  • Problem: Amount Deposited is copied from the challan for one payee onto several rows. Solution: deposited amounts are period totals. Keep them on the summary row, not repeated on every deduction.
  • Problem: the ledger reconciliation is marked Reconciled with a variance amount. Solution: a non-zero variance is Variance, not Reconciled, until it is explained.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.
  • @accounting-audit-system-builder - routes to this skill and the other accounting modules.
  • @expense-accounting - the expense and payment rows that carry the deduction.
  • @salary-wage-accounting - the source of salary TDS for the period.
  • @payment-accounting - the net payment actually released after the deduction.
  • @monthly-closing-statements - closes the payable account the deposit clears.

Reusable Prompt

I want to set up tax deducted at source, deposited on time, filed and reconciled to the ledger for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema and a Notion property mapping. Data only.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/tds-booking-payment of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Tds Booking Payment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tds Booking Payment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tds Booking Payment this skillsickn33/agentic-awesome-skills47k1 repos~5kAutomated safety check: PassMIT
Agent Paymentsruvnet/ruflo74k2 repos~960Automated safety check: PassMIT
BookingsBuilderIO/agent-native7.1k—~345Automated safety check: PassNone
Agent Payment X402affaan-m/ECC276k—~6.8kAutomated safety check: PassMIT
Agent Agentic Paymentsruvnet/ruflo74k2 repos~1.3kAutomated safety check: PassMIT
Iot Registerruvnet/ruflo74k—~263Automated safety check: PassMIT

Similar skills

  • Agent Payments

    ruvnet/ruflo

    Agent skill for payments - invoke with $agent-payments. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 2 repos~960 tokens
    Auto-check passed
  • Bookings

    BuilderIO/agent-native

    Booking lifecycle — pending, confirmed, rescheduled, cancelled — plus attendees, references, no-shows, and reminders.

    7.1k GitHub stars~345 tokensUpdated yesterday
    Auto-check passed
  • Agent Payment X402

    affaan-m/ECC

    Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets.

    276k GitHub stars~6.8k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Agent skill for agentic-payments - invoke with $agent-agentic-payments

    74k GitHub starsUsed in 2 repos~1.3k tokens
    Backend & APIsAuto-check passed
  • Iot Register

    ruvnet/ruflo

    Register a Cognitum Seed device by endpoint and establish agent bridge

    74k GitHub stars~263 tokensUpdated yesterday
    Auto-check passed
  • Agent Payment X402

    affaan-m/ECC

    タスクごとのバジェット、支出コントロール、ノンカストディアルウォレットを備えた x402 決済実行を AI エージェントに追加します。agentwallet-sdk を通じて Base を、OKX Payments / OKX エージェント決済プロトコルを通じて X Layer を、アップストリームの x402 パッケージとファシリテーターベースの決済を通じて Solana…

    276k GitHub stars~5.4k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Tds Booking Payment

What does Tds Booking Payment do?

TDS register: payee PAN, payment nature, rate and amount deducted, deposit date and challan reference, return filing and ledger variance. Tds Booking Payment is an agent skill from sickn33/agentic-awesome-skills. TDS register: payee PAN, payment nature, rate and amount deducted, deposit date and challan reference, return filing and ledger variance.

How do I install Tds Booking Payment in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill tds-booking-payment -a claude-code`. Or copy the skill folder (skills/tds-booking-payment in sickn33/agentic-awesome-skills) into .claude/skills/tds-booking-payment in your project. Claude Code loads it when a task matches its description.

How do I install Tds Booking Payment in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill tds-booking-payment -a codex`. Or copy the skill folder (skills/tds-booking-payment in sickn33/agentic-awesome-skills) into .agents/skills/tds-booking-payment in your project. Codex loads it when a task matches its description.

Can I use Tds Booking Payment in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill tds-booking-payment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tds-booking-payment, .gemini/skills/tds-booking-payment, .github/skills/tds-booking-payment and .opencode/skills/tds-booking-payment in your project.

What does Tds Booking Payment need to run?

SKILL.md names no scripts, command-line tools or credentials: Tds Booking Payment is instructions for the agent only.

Does Tds Booking Payment access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Tds Booking Payment safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tds Booking Payment use?

Tds Booking Payment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tds Booking Payment use?

About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tds Booking Payment?

Skills that share tags, products or a category with Tds Booking Payment: Agent Payments (ruvnet/ruflo, 74k stars), Bookings (BuilderIO/agent-native, 7.1k stars), Agent Payment X402 (affaan-m/ECC, 276k stars) and Agent Agentic Payments (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tds Booking Payment?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.