Menu
How to orient inside a client workspace - the directory layout, the manifest, provenance records, and which sources outrank which.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Required procedure for answering questions about the client - grounding, citation format, conflict handling, and how to say "not in the workspace".
How to record completed work in logs/agent-log.md so humans can inspect what the agent read, wrote, and concluded.
How to create deliverable artifacts (meeting prep briefs, draft emails, analyses) in artifacts/ with required structure and source manifests.
How to extract durable memories from sources and write them as reviewable candidate memory files with provenance, confidence, and sensitivity.
| name | workspace-navigation |
| description | How to orient inside a client workspace - the directory layout, the manifest, provenance records, and which sources outrank which. |
Every client workspace follows this structure:
manifest.json Inventory of every file: source system, sync time, sensitivity
client/ Structured metadata (profile.json, household.json, accounts.json)
emails/ Email threads as Markdown, one file per thread, dated filenames
transcripts/ Meeting transcripts as Markdown, dated filenames
notes/ Advisor meeting notes as Markdown
documents/ Summaries of source documents (estate plans, policies, statements)
tasks/ open-tasks.md - open items and unresolved questions
memory/durable/ Reviewed, durable memories (trusted)
memory/candidates/ Agent-proposed memories awaiting human review (untrusted)
artifacts/ Agent-created deliverables (briefs, drafts, analyses)
logs/ agent-log.md (your work log) and tool-calls.jsonl (automatic)
manifest.json first. It lists every file with its source system, last sync timestamp, and sensitivity label.listFiles to confirm what actually exists (the manifest may lag).bash with grep -rn to locate topics across files before reading whole files.client/*.json — canonical structured data for identity facts (names, DOBs, account numbers)transcripts/ — verbatim primary record of what was saidemails/ — primary record of what was writtennotes/ — advisor interpretation; secondarydocuments/ — summaries of source docs; secondarymemory/durable/ — reviewed distillations; convenient but always re-verify against primary sources when stakes are highmemory/candidates/ — unreviewed; never treat as factFilenames begin with ISO dates (2026-04-02-...). When two sources of the same rank disagree, the newer one wins — but you must mention the older statement and that it changed.
The manifest labels files public, internal, confidential, or restricted. Mention the sensitivity label when quoting from confidential or restricted files in artifacts.