setup
Skill1 starsChanged 32 days agoMITView on GitHub
Help a lawyer, law firm owner, or practice manager get started with Law Firm Skills. Choose a first workflow, show a fictional result, and explain supplied-data and already-connected-tool modes. Use when installing this collection or asking how to start; not for unrelated software setup.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- openstory-so/openstorytheir own version, first seen Nov 16, 2026
- furkandvrc/conductortheir own version, first seen Nov 16, 2026
- futorio/red-greentheir own version, first seen Nov 16, 2026
- JCodesMore/jobs-for-ai-agentstheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
Used with
Projects with it also use add-atomic-chat-tool, add-dashboard and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-atomic-chat-tool
Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
Also in 8 projects that use this
MicrosoftSkilladd-dashboard
Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
Also in 8 projects that use this
- +10 more from microsoft
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- anthropics/knowledge-work-plugins★ 36ksame name
- garrytan/gbrain★ 33ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.4ksame name
- pytorch/executorch★ 5.2ksame name
- aws/agent-toolkit-for-aws★ 3.5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- blind-spotSkill
- buildSkill
- decideSkill
- emailSkill
- evaluate-teamSkill
- follow-upSkill
- fridaySkill
- link-reviewSkill
- meeting-prepSkill
- meetingSkill
- morningSkill
- nextSkill
- playbookSkill
- profit-planSkill
- scale-planSkill
- todoistSkill
- verifySkill
- watchSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use information already supplied.
- Distinctive: line 22
Do not ask for client names, credentials, financial records, or account access to demonstrate the collection.
- Distinctive: line 29
Use meeting-prep before a call and verify to check a completed result.
- Distinctive: line 60
If private workspace context is useful, propose a short record of role, goal, source coverage, timezone, and approval rules.
- Distinctive: line 63
Do not install tools, connect accounts, create automations, send messages, or modify business records during setup.
“Common” is measured: kept by at least 6 in 10 of the 169 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Get started with Law Firm Skills
Help the user get one useful result with minimal setup. This collection contains 18 practice-management workflows plus this onboarding skill. Installation grants no access to accounts, permission to act, or ongoing background work.
First conversation
Use information already supplied. Ask only for missing information that changes the first workflow: their role, the outcome they want, whether they will supply notes or use tools already authorized in this workspace, and applicable approval boundaries. Bundle these in one short question rather than a long questionnaire. Do not ask for client names, credentials, financial records, or account access to demonstrate the collection. If they want to try it immediately, use the fictional example below without blocking on configuration.
Choose decide or playbook for the first result. Use morning once source coverage is understood. Other entry points: meeting for notes to actions; follow-up for existing commitments; build for an idea requiring a specification and approval. Use meeting-prep before a call and verify to check a completed result. Explain that independent review needs a separate authorized provider and an approved evidence packet; missing access is reported, not silently substituted. Name the intended skill and load it using the host's skill selector when available. If it is not installed or available, say so and provide the explicit request the user can paste. Do not claim an unavailable skill was invoked.
Fictional first result
Example: A two-lawyer firm can improve appointment reminders or replace intake software this month. Missed appointments are the measured problem; the existing software already supports reminders. No cost, volume, or conversion data was provided. The user wants advice only.
Show a compact decision: test the existing reminder feature first; it addresses the observed issue with fewer implementation assumptions. Ask the responsible operator to confirm permission and baseline attendance before any pilot. Do not invent savings, a deadline, or a completed configuration. Reconsider if evidence shows the current software cannot deliver reliable reminders or the main cause lies elsewhere. Label this as fictional, not a client result.
Explain use and access
- Supplied-data mode: use permitted notes, exports, or a fictional example.
- Connected mode: use only tools actually available and authorized by the user. This collection bundles no inbox, CRM, calendar, task, or video connector.
- Claude Code standalone: /morning. Claude plugin: /law-firm-skills:morning.
- Codex: select the skill or use $morning. ChatGPT: select the installed plugin with the @ selector; a public directory listing is required for that route.
- A pasted workflow prompt is a fallback, not native installation.
If private workspace context is useful, propose a short record of role, goal, source coverage, timezone, and approval rules. Save only in a user-approved private location with permission, never inside the public plugin or repository. Do not install tools, connect accounts, create automations, send messages, or modify business records during setup. End with one suggested first request.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

