invoice-generator
Generate professional PDF invoices from JSON data. Use when the user needs to create an invoice, billing document, or payment request with company/client details and line items.
Best use case
invoice-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate professional PDF invoices from JSON data. Use when the user needs to create an invoice, billing document, or payment request with company/client details and line items.
Teams using invoice-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/invoice-generator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How invoice-generator Compares
| Feature / Agent | invoice-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate professional PDF invoices from JSON data. Use when the user needs to create an invoice, billing document, or payment request with company/client details and line items.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Invoice Generator
Generate PDF invoices from structured JSON data.
## Setup
1. Install Node.js dependencies:
```bash
cd invoice-generator && npm install
```
2. Set `INVOICE_DIR` environment variable (or in `skills.entries.invoice-generator.env`):
```bash
export INVOICE_DIR="/path/to/your/invoices"
```
This creates the directory structure:
```
$INVOICE_DIR/
├── configs/ # Optional: saved invoice configs
└── invoices/ # Generated PDF output
```
## Usage
```bash
# From stdin (on-the-fly)
cat invoice-data.json | {baseDir}/scripts/generate.sh
# From a full file path
{baseDir}/scripts/generate.sh /path/to/invoice-data.json
# From a saved config (looks in $INVOICE_DIR/configs/)
{baseDir}/scripts/generate.sh client-template
# Loads: $INVOICE_DIR/configs/client-template.json
# Output goes to: $INVOICE_DIR/invoices/invoice-{number}.pdf (auto-versions if exists)
```
## Input Data Format
The JSON input must contain these fields:
```json
{
"company": {
"name": "Your Company",
"address": "123 Main St",
"cityStateZip": "City, State, 12345",
"country": "Country"
},
"client": {
"name": "Client Name",
"address": "456 Client Ave",
"cityStateZip": "City, State, 67890",
"country": "Country",
"taxId": "TAX123"
},
"invoice": {
"number": "INV-2025.01",
"date": "Jan 15 2025",
"dueDate": "Jan 30 2025"
},
"items": [
{
"description": "Service description",
"rate": "1000.00",
"currency": "USD"
}
],
"totals": {
"currency": "USD",
"total": "1,000.00"
}
}
```
See [references/data-schema.md](references/data-schema.md) for complete field documentation.
## Output
The script outputs the path to the generated PDF file on success:
```
$INVOICE_DIR/invoices/invoice-INV-2025.01.pdf
# If that filename already exists, the script will write:
# $INVOICE_DIR/invoices/invoice-INV-2025.01-2.pdf (then -3, etc.)
```
## Error Handling
- Exits with code 1 if JSON is invalid or missing required fields
- Exits with code 2 if weasyprint fails to generate PDF
- Error messages are written to stderrRelated Skills
content-ideas-generator
Generates structured post outlines from reference materials for wisdom-style social posts. Use when someone wants to extract compelling concepts from newsletters, scripts, notes, or other content and transform them into engaging post outlines with paradoxes, transformations, and powerful insights.
content-draft-generator
Generates new content drafts based on reference content analysis. Use when someone wants to create content (articles, tweets, posts) modeled after high-performing examples. Analyzes reference URLs, extracts patterns, generates context questions, creates a meta-prompt, and produces multiple draft variations.
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".