Agent skill

Invoices Billing

by sickn33 in sickn33/agentic-awesome-skills

Invoice and billing register: invoice number, client, project, issue and due dates, subtotal, discount, tax and withholding, total, payments, balance and aging.

MITAuto-check passedDocuments & Office

Install Invoices Billing

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill invoices-billing -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills invoices-billing --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/invoices-billing .claude/skills/invoices-billing && 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
invoices-billing
GitHub stars
47k
Used in
1 other repo
Token cost
~4.4k tokens
SKILL.md length
1,518 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Invoice and billing register: invoice number, client, project, issue and due dates, subtotal, discount, tax and withholding, total, payments, balance and aging.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Billing follow-up
  • 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

Invoices Billing is an agent skill from sickn33/agentic-awesome-skills. Invoice and billing register: invoice number, client, project, issue and due dates, subtotal, discount, tax and withholding, total, payments, balance and aging. Use for billing follow-up.

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

It sits in Documents & Office, covering Forms and invoices. 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.

When your agent uses it

  • Billing follow-up
  • Tasks that involve Forms and invoices

Example prompts

  • “/invoices-billing”

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

Invoices Billing loads about 4.4k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 1,518 words of instructions outside code blocks.

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

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,518 words, ~4,405 tokens.

Download SKILL.mdSave it as .claude/skills/invoices-billing/SKILL.md (or your agent's skills folder).
name
invoices-billing
description
Invoice and billing register: invoice number, client, project, issue and due dates, subtotal, discount, tax and withholding, total, payments, balance and aging. Use for billing follow-up.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, operate
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Invoices & Billing

What it is: Invoices from billable time or fixed fees, with tax, due dates and aging.

Overview

Works out the smallest useful Invoices & Billing 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 8: Operate. Fits: Starter stage. Table code: n/a.

When to Use This Skill

  • invoice tracker
  • billing spreadsheet
  • invoice register
  • accounts receivable aging

Also use it when the user says "invoices from billable time or fixed fees, with tax, due dates and aging", 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: How do you bill clients today?

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.

  • Billing - How many clients? / Monthly, milestone or hourly? / Invoices raised by whom?
  • Terms - Payment terms? / Retainer or one-off? / Any late fees?
  • Tracking - How is status tracked? / Sent, due or overdue? / Who chases?
  • Current process - What tool today? / Accounting package or sheet? / What gets missed?
  • Outcome - What do you need? / An invoice record, a template 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: invoices-billing
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Billing": null
  "Terms": null
  "Tracking": 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 asking
Step 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: One invoice record with the client, the amount, the due date and the status, and let the accounting package handle the actual invoice document.

Why this one: Billing problems are chasing problems. A due date and a status per invoice is the minimum that makes chasing possible.

Workflow: Work recorded → Invoice raised → Status tracked → Chased → Paid or overdue

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.

csv
Invoice Number,Client,Project,Issue Date,Payment Terms (Days),Due Date,Currency,Time Entries,Subtotal,Discount,Tax Rate %,Tax Amount,Withholding Tax,Total,Payments,Amount Paid,Balance,Days Overdue,Aging,Payment Status,Status,Sent Date,Prepared By,Approved By,Notes,Invoice ID
INV-1041,Northwind Traders,Website Redesign,2026-08-15,30,2026-09-14,INR,"TIME-2026-011, TIME-2026-012",118000.00,4720.00,18,21240.00,20000.00,134520.00,PAY-2210,120000.00,14520.00,12,0-30 days,Part Paid,Issued,2026-08-15,Ananya Rao,Vikram Singh,"Follow-up sent in February; the client queried the retainer line, not the hours.",
sql
CREATE TABLE invoices_billing (
  invoice_number VARCHAR(255),
  client VARCHAR(255),
  project VARCHAR(255),
  issue_date DATE NOT NULL,
  payment_terms_days NUMERIC NOT NULL,
  due_date DATE NOT NULL,
  currency VARCHAR(255),
  time_entries VARCHAR(255),  -- relation -> target record
  subtotal NUMERIC(14,2) NOT NULL,
  discount NUMERIC(14,2) NOT NULL,
  tax_rate_pct NUMERIC NOT NULL,
  tax_amount NUMERIC(14,2) NOT NULL,
  withholding_tax NUMERIC(14,2) NOT NULL,
  total NUMERIC(14,2) NOT NULL,
  payments VARCHAR(255),  -- relation -> target record
  amount_paid NUMERIC(14,2) NOT NULL,
  balance NUMERIC(14,2) NOT NULL,
  days_overdue NUMERIC NOT NULL,
  aging VARCHAR(255),
  payment_status VARCHAR(100) NOT NULL,
  status VARCHAR(100) NOT NULL,
  sent_date DATE NOT NULL,
  prepared_by VARCHAR(255),
  approved_by VARCHAR(255),
  notes TEXT,
  invoice_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_invoices_billing_status ON invoices_billing (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Invoices & Billing",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Invoice Number": { "type": "string" },
      "Client": { "type": "string" },
      "Project": { "type": "string" },
      "Issue Date": { "type": "string", "format": "date" },
      "Payment Terms (Days)": { "type": "number" },
      "Due Date": { "type": "string", "format": "date" },
      "Currency": { "type": "string" },
      "Time Entries": { "type": "string" },
      "Subtotal": { "type": "number" },
      "Discount": { "type": "number" },
      "Tax Rate %": { "type": "number" },
      "Tax Amount": { "type": "number" },
      "Withholding Tax": { "type": "number" },
      "Total": { "type": "number" },
      "Payments": { "type": "string" },
      "Amount Paid": { "type": "number" },
      "Balance": { "type": "number" },
      "Days Overdue": { "type": "number" },
      "Aging": { "type": "string" },
      "Payment Status": { "type": "string" },
      "Status": { "type": "string" },
      "Sent Date": { "type": "string", "format": "date" },
      "Prepared By": { "type": "string" },
      "Approved By": { "type": "string" },
      "Notes": { "type": "string" },
      "Invoice ID": { "type": "integer" }
  },
  "required": [
      "Issue Date",
      "Payment Terms (Days)",
      "Due Date",
      "Subtotal",
      "Discount",
      "Tax Rate %",
      "Tax Amount",
      "Withholding Tax",
      "Total",
      "Amount Paid",
      "Balance",
      "Days Overdue",
      "Payment Status",
      "Status",
      "Sent Date"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Invoice Number | Title | Use as the database title |
| Client | Text | Leave as Text |
| Project | Text | Leave as Text |
| Issue Date | Date | Convert to Date |
| Payment Terms (Days) | Number | Convert to Number |
| Due Date | Date | Convert to Date |
| Currency | Text | Leave as Text |
| Time Entries | Relation (link to the target database) | Convert to Relation, link to the target database |
| Subtotal | Number (format: currency) | Convert to Number, set format to Currency |
| Discount | Number (format: currency) | Convert to Number, set format to Currency |
| Tax Rate % | Number | Convert to Number |
| Tax Amount | Number (format: currency) | Convert to Number, set format to Currency |
| Withholding Tax | Number (format: currency) | Convert to Number, set format to Currency |
| Total | Number (format: currency) | Convert to Number, set format to Currency |
| Payments | Relation (link to the target database) | Convert to Relation, link to the target database |
| Amount Paid | Number (format: currency) | Convert to Number, set format to Currency |
| Balance | Number (format: currency) | Convert to Number, set format to Currency |
| Days Overdue | Number | Convert to Number |
| Aging | Text | Leave as Text |
| Payment Status | Select (add options after import) | Convert to Select, add options: "Draft", "Sent", "Part Paid", "Paid", "Overdue", "Cancelled" |
| Status | Select (add options after import) | Convert to Select, add options: "Draft", "Issued", "Sent", "Part Paid", "Paid", "Void" |
| Sent Date | Date | Convert to Date |
| Prepared By | Text | Leave as Text |
| Approved By | Text | Leave as Text |
| Notes | Text | Leave as Text |
| Invoice 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
1Invoice NumbertextVARCHAR(255)stringTextINV-1041
2ClienttextVARCHAR(255)stringTextNorthwind Traders
3ProjecttextVARCHAR(255)stringTextWebsite Redesign
4Issue DatedateDATEstring, format: dateDate2026-08-15
5Payment Terms (Days)numberNUMERICnumberNumber30
6Due DatedateDATEstring, format: dateDate2026-09-14
7CurrencytextVARCHAR(255)stringTextINR
8Time EntriesrelationVARCHAR(255)stringRelation (link to the target database)TIME-2026-011, TIME-2026-012
9SubtotalcurrencyNUMERIC(14,2)numberNumber (format: currency)118000.00
10DiscountcurrencyNUMERIC(14,2)numberNumber (format: currency)4720.00
11Tax Rate %numberNUMERICnumberNumber18
12Tax AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)21240.00
13Withholding TaxcurrencyNUMERIC(14,2)numberNumber (format: currency)20000.00
14TotalcurrencyNUMERIC(14,2)numberNumber (format: currency)134520.00
15PaymentsrelationVARCHAR(255)stringRelation (link to the target database)PAY-2210
16Amount PaidcurrencyNUMERIC(14,2)numberNumber (format: currency)120000.00
17BalancecurrencyNUMERIC(14,2)numberNumber (format: currency)14520.00
18Days OverduenumberNUMERICnumberNumber12
19AgingtextVARCHAR(255)stringText0-30 days
20Payment StatusselectVARCHAR(100)stringSelect (add options after import)Part Paid
21StatusselectVARCHAR(100)stringSelect (add options after import)Issued
22Sent DatedateDATEstring, format: dateDate2026-08-15
23Prepared BytextVARCHAR(255)stringTextAnanya Rao
24Approved BytextVARCHAR(255)stringTextVikram Singh
25Noteslong_textTEXTstringTextFollow-up sent in February; the client queried the retainer line, not the hours.
26Invoice IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (495 more words)Show less

Select Options

Payment Status

Draft | Sent | Part Paid | Paid | Overdue | Cancelled

Status

Draft | Issued | Sent | Part Paid | Paid | Void

Relations

Link fields: Time Entries, Payments

Examples

Prompt

We invoice from three places and cannot tell what is overdue.

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

Q: How many clients? A: Fifteen.

Q: Billing type? A: Monthly retainer, mostly.

Q: Payment terms? A: Net 30.

Recommended next step - offered, not built:

One invoice record with the client, the amount, the due date and the status, and let the accounting package handle the actual invoice document.

Workflow: Work recorded → Invoice raised → Status tracked → Chased → Paid or overdue

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.
  • 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 payroll, tax, leave balances or KPIs.
  • 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.
  • Does not raise, send or collect any money.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details 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 sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

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: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • 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.

Reusable Prompt

I want to set up invoices from billable time or fixed fees, with tax, due dates and aging 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, a Notion property mapping or an Excel workbook. 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/invoices-billing 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

Invoices Billing 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.

Invoices Billing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Invoices Billing this skillsickn33/agentic-awesome-skills47k1 repos~4.4kAutomated safety check: PassMIT
PDFzai-org/ZCode7.7k—~18kAutomated safety check: NotesProprietary
Form Fillingplatonai/Browser41.2k—~1.1kAutomated safety check: PassApache-2.0
Code2mediatsingliuwin/autoclaw283—~985Automated safety check: PassMIT
Token ReceiptHchen1218/token-receipt126—~2.1kAutomated safety check: PassNone
Invoice Makertsingliuwin/autoclaw283—~619Automated safety check: PassMIT

Similar skills

  • PDF

    zai-org/ZCode

    Professional PDF toolkit covering four production workflows: reports, creative visuals, academic LaTeX, and existing PDF processing.

    7.7k GitHub stars~18k tokensUpdated yesterday
    Documents & OfficeAuto-check: notes
  • Form Filling

    platonai/Browser4

    Automatically fills web forms using provided field data and can optionally submit the form.

    1.2k GitHub stars~1.1k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Code2media

    tsingliuwin/autoclaw

    Universal media renderer with no fixed template — any custom layout, size or style becomes pixel-perfect images (PNG/JPEG/WebP), vector SVG, paged PDFs or animations (WebP/GIF).

    283 GitHub stars~985 tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Token Receipt

    Hchen1218/token-receipt

    A skill your agent uses when the user wants to view AI conversation token usage as a receipt, invoice, checkout slip, token bill, usage receipt, cost snapshot, or creative monospace thermal-paper…

    126 GitHub stars~2.1k tokensUpdated 4 mo ago
    Documents & OfficeAuto-check passed
  • Invoice Maker

    tsingliuwin/autoclaw

    开发票/生成发票/报价单/收据/采购单/对账单/账单/付款通知 — formal business documents as paged PDFs with proper tables, right-aligned amounts, tax lines, repeating headers and page-number footers.

    283 GitHub stars~619 tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Invoice Generator

    luzhenqian/ai-coding-lab

    从 Excel 时间表或手动输入生成专业发票。当用户提到生成发票、创建账单、invoice、billing、开发票、时间表转发票、账单生成时使用此技能。

    153 GitHub stars~955 tokensUpdated 4 mo ago
    Documents & OfficeAuto-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 Invoices Billing

What does Invoices Billing do?

Invoice and billing register: invoice number, client, project, issue and due dates, subtotal, discount, tax and withholding, total, payments, balance and aging. Invoices Billing is an agent skill from sickn33/agentic-awesome-skills. Invoice and billing register: invoice number, client, project, issue and due dates, subtotal, discount, tax and withholding, total, payments, balance and aging.

When should I use Invoices Billing?

Invoices Billing fits situations like: billing follow-up; tasks that involve Forms and invoices.

How do I install Invoices Billing in Claude Code?

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

How do I install Invoices Billing in Codex?

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

Can I use Invoices Billing 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 invoices-billing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/invoices-billing, .gemini/skills/invoices-billing, .github/skills/invoices-billing and .opencode/skills/invoices-billing in your project.

What does Invoices Billing need to run?

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

Does Invoices Billing 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 Invoices Billing 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 Invoices Billing use?

Invoices Billing 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 Invoices Billing use?

About 4.4k tokens (SKILL.md is roughly 18k 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 Invoices Billing?

Skills that share tags, products or a category with Invoices Billing: PDF (zai-org/ZCode, 7.7k stars), Form Filling (platonai/Browser4, 1.2k stars), Code2media (tsingliuwin/autoclaw, 283 stars) and Token Receipt (Hchen1218/token-receipt, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Invoices Billing?

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.