generate-invoice

Included with Lifetime

$97 forever

Generate a PDF invoice from Toggl time data. Use when the user wants to create an invoice, generate a bill, or mentions invoicing a client.

Writing & Docs

What this skill does


# Generate Invoice

Generate a PDF invoice by pulling hours from Toggl and rendering to PDF. The tool lives at `/home/czue/src/personal/agent-tools/invoice-gen/`.

## Arguments

- `$0`: (optional) end date (YYYY-MM-DD)
- `$1`: (optional) client config name (default: "peregrine")
- `$2`: (optional) start date (YYYY-MM-DD, defaults to day after last invoice)

## Workflow

1. **Resolve the end date**:
   - If `$0` is provided, use it.
   - Otherwise, use `AskUserQuestion` to ask: "What end date for the invoice?" with options for today's date and end of last month.

2. **Resolve the client**:
   - If `$1` is provided, use it.
   - Otherwise, default to `peregrine`.

3. **Dry run first** to confirm hours and amount:
   ```bash
   cd /home/czue/src/personal/agent-tools/invoice-gen && uv run python generate.py --end <end_date> --client <client> --dry-run
   ```
   If `$2` (start date) is provided, add `--start <start_date>`.
   Show the user the hours, amount, working days, and average hours per working day, and ask for confirmation before generating.

4. **Generate the invoice**:
   ```bash
   cd /home/czue/src/personal/agent-tools/invoice-gen && uv run python generate.py --end <end_date> --client <client>
   ```
   Add `--start` and `--description` if provided by the user.

5. **Report results**: Show the output path and the invoice summary (hours, rate, amount, working days, avg hours/working day).

## CLI Options

- `--start`: Start date. Defaults to day after last invoice end date for that client.
- `--end`: End date (required).
- `--client`: Client config name matching a file in `invoice-gen/clients/`.
- `--description`: Work description (default: "Ongoing bolt assistant work.").
- `--output-dir`: Output directory (default: `/home/czue/Dropbox/Personal/Elodin/invoices`).
- `--dry-run`: Preview without generating.

## Client Configs

Client TOML files live in `invoice-gen/clients/`. Each has: name, country, rate, currency, toggl_project_name, line_item_description. To add a new client, copy `example.toml`.

## Notes

- Invoice numbers auto-increment via `invoice-gen/counter.json`.
- Last end date per client is tracked, so `--start` is usually not needed.
- Suppress `uv` warnings in output (they're noisy but harmless).

Files: 1

Size: 2.5 KB

Complexity: 10/100

Category: Writing & Docs

Source: https://github.com/czue/agent-tools/tree/main/skills/generate-invoice

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts