billable-time-stephane-boghossian
When your bar comes asking "show me how you billed AI-assisted work" — and ABA 512, Florida 24-1, California, New York, and DC all have opinions out — you need an artifact that survives review. billable-time produces it. From your Claude Code session logs, it drafts reviewable time entries plus a printable HTML audit packet with: SHA-256 chain of evidence (source files + matter.yml + active disclosure pack + verifiable artifact self-hash), attorney identity and signature block, a bar-opinion disclosure pack with starter language for five jurisdictions, and content-aware deterministic narrativ
npx skills add lawve-ai/awesome-legal-skills --skill billable-time-stephane-boghossian --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# billable-time — operating instructions (defense mode) You are running inside the **billable-time** skill. The user is a lawyer (or their support staff) who wants to turn raw Claude Code session logs into a reviewable, cryptographically-stamped audit artifact. The artifact you produce is **never billed automatically**. The lawyer accepts, edits, or rejects every row before anything reaches a billing system, and signs the audit packet by hand. The artifact you help produce will, in the worst case, sit in a bar grievance file. Behave accordingly. ## Hard refusals — do not negotiate these 1. **Never auto-bill.** The output is a markdown diff plus an HTML audit packet. If the user asks you to "just send these to Clio" or "upload directly," refuse and explain that the audit-surface contract requires attorney signoff before billing. Suggest exporting the accepted rows as CSV and uploading manually. 2. **Never infer matter assignment from file contents.** Use the cwd-prefix routing in `matter.yml` only. Do not read a `.docx` and decide "this looks like an Acme matter." That is the malpractice surface this tool was designed to avoid. 3. **Never rewrite narratives with an LLM.** Narratives
- Hard refusals — do not negotiate these
- Pre-flight checklist (before invoking the CLI)
- How to run
- What to say to the user, in this order
- When to escalate or refuse
- Web alternative
- Verifying the self-hash (for the audit-defense scenario)
- Invariants you must remember during the session
node <skill-base>/draft-entries.mjs \
What does the billable-time-stephane-boghossian skill do?
When your bar comes asking "show me how you billed AI-assisted work" — and ABA 512, Florida 24-1, California, New York, and DC all have opinions out — you need an artifact that survives review. billable-time produces it. From your Claude Code session logs, it drafts reviewable time entries plus a printable HTML audit packet with: SHA-256 chain of evidence (source files + matter.yml + active disclosure pack + verifiable artifact self-hash), attorney identity and signature block, a bar-opinion disclosure pack with starter language for five jurisdictions, and content-aware deterministic narrativ
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill billable-time-stephane-boghossian --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.