probanda-setup
Skill1 starsChanged 9 days agoLicence not identifiedView on GitHub
Set Probanda up on a device where it has never been set up: a practice_data tool reports probanda.json not found, or practice_data__config_status reports exists false. Finds the practitioner's 0. CASE DATA folder (or where to create one), writes this device's probanda.json, creates the practice database, records who uses this device, connects the folder suggestions are shown from, and records where the practitioner keeps each kind of document (their folder map). Also use it, on a device already set up, when another skill reports that Probanda does not yet know where the practitioner keeps each kind of document: it then runs only that step. Not for a settings file that exists but is broken (practice-data's repair), or for a tool that fails on a device already set up.
In this repository73 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .claude/skills/draft/CLAUDE.mdCLAUDE.md
- .claude/skills/drafting-data/CLAUDE.mdCLAUDE.md
- .claude/skills/matter-data/CLAUDE.mdCLAUDE.md
- apply-to-factsSkill
- ar-follow-upSkill
- assembleSkill
- bcsc-legal-basisSkill
- bill-clientSkill
- build-timelineSkill
- calculateSkill
- calendar-remindersSkill
- call-contactSkill
- case-briefSkill
- compare-documentsSkill
- CPRSkill
- deduping-emailSkill
- drafting-dataSkill
- draftSkill
- e-fileSkill
- executive-assistantSkill
- file-applySkill
- file-namingSkill
- file-review-prepSkill
- file-sortingSkill
- find-documentSkill
- fix-thisSkill
- hitl-triageSkill
- housekeepingSkill
- ingest-orchestratorSkill
- ingestSkill
- invoice-reviewingSkill
- invoice-trackingSkill
- issue-invoiceSkill
- job-planningSkill
- legal-commonsSkill
- legal-memo-extractorSkill
- legal-researchSkill
- localizeSkill
- matter-dataSkill
- matter-status-trackingSkill
- narratorSkill
- polish-substanceSkill
- practice-dataSkill
- precedentsSkill
- prepareSkill
- probanda-troubleshootingSkill
- publishSkill
- reflectSkill
- retainer-trackingSkill
- review-propositionSkill
- route-accountingSkill
- rule-migrateSkill
- rule-updateSkill
- safe-file-deletionSkill
- show-meSkill
- solverSkill
- streamline-skillSkill
- suggestionSkill
- task-prioritizationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

