Clio Time & Billing skillA
Clio Time & Billing is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: Clio time and expense activities logged against a matter: the activities domain's create-only lifecycle, the billing-read / time-entry-write split, and why billing mutations are out of scope for v1..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Clio Time & Billing ## Overview Clio splits billing-adjacent work into two domains with very different permissions, and the split is deliberate: | Domain | Tools | Can you write? | |---|---|---| | **activities** | `clio_activities_list`, `clio_activities_get`, `clio_activities_create` | Create only — no update, no delete | | **bills** | `clio_bills_list`, `clio_bills_get` | Read-only | Both domains reference `matter_id` — activities are logged *against* a matter, and bills are generated from a matter's unbilled activities. See the [api-patterns skill](../api-patterns/SKILL.md) for the full matters-as-hub picture. ## Anti-triggers "Log time", "the invoice", and "the bill" are the most heavily overloaded phrases in this marketplace, and every one of them means something else outside Clio: - **Technician time against a ticket or project** — MSP time entries live in the PSA; use `autotask-time-entries`, `connectwise-psa-time-entries`, or `halopsa-tickets`. A Clio activity is billable legal work against a matter, not service-desk labour. - **An invoice on the accounting system** — a Clio bill is generated …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Clio Time & Billing@git:20260817.2671d27mdr add wyre-ai/msp-claude-plugins/Clio Time & Billing@sha256:30a1ab28ddc7cebaPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ozotibi72ph3eq4r)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260817.2671d27 latest | 2026-08-17 | 2671d27 | 5,783 B | A | view · diff |
| git:20260804.792c422 | 2026-08-04 | 792c422 | 5,797 B | A | view · diff |
| git:20260804.6747a52 | 2026-08-04 | 6747a52 | 5,790 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 4,811 B | A | view · diff |
| git:20260715.f892358 | 2026-07-15 | f892358 | 4,875 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5783 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wyre-ai/msp-claude-plugins · 46 stars · license Apache-2.0 · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ozotibi72ph3eq4r GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Clio Time & Billing GET https://markdownregistry.com/api/v1/blob/30a1ab28ddc7cebaa0a90f1b70f3b437af7160bcd2b57175459ecc191d0eb6bf
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.