Client Ctx Sys
Keep per-client project context in a file-first wiki that auto-primes your coding agent and turns meetings into linked notes.
Overview
client-ctx-sys is an agent skill most often used in Build (also Operate, Grow) that maintains a file-first client wiki with auto-priming and meeting ingestion linked in an Obsidian-style knowledge graph.
Install
npx skills add https://github.com/Rugved-Rakebma/client-mgt-market --skill client-ctx-sysWhat is this skill?
- File-first client wiki you own in the repo or vault
- Project-scoped auto-priming so agents load the right client context
- Meeting ingestion into structured notes
- Obsidian-compatible knowledge graph linking
- Works across engagements without a separate CRM database
Adoption & trust: 1 GitHub stars.
What problem does it solve?
You lose hours re-explaining client history to your agent because context lives in scattered calls, chats, and ad-hoc notes.
Who is it for?
Freelancers and small studios managing multiple client repos who want agent-ready context without a heavy CRM.
Skip if: Teams that already enforce a single source of truth in a managed CRM with no local files, or builders with no client-facing work.
When should I use this skill?
Starting work on a client project, after a client meeting, or when the agent needs project-scoped client wiki context.
What do I get? / Deliverables
Each project session starts with primed client context, ingested meetings, and linked wiki files your agent can cite on the next task.
- Updated client wiki pages
- Ingested meeting note files
- Knowledge-graph links between client entities
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Client delivery and scope live in the build phase; this skill is the canonical shelf for project-scoped context while you ship work for clients. PM subphase fits file-first wikis, meeting ingestion, and knowledge graphs that support planning and handoffs—not a one-off doc generator.
Where it fits
Prime the agent with prior discovery notes before estimating a new client milestone.
Link sprint tasks to stakeholder decisions ingested from the last client call.
Pull delivery checklist context from the wiki for final client handoff messaging.
Re-open a retainer engagement with graph-linked history instead of searching email.
How it compares
Use instead of dumping client notes into generic chat memory—structured wiki + priming beats one-off pasted threads.
Common Questions / FAQ
Who is client-ctx-sys for?
Solo builders and indie agencies who deliver client projects with AI coding agents and need durable, searchable client context on disk.
When should I use client-ctx-sys?
During Build PM when scoping sprints; in Ship launch prep when aligning deliverables; in Operate support when revisiting decisions; in Grow lifecycle when updating retainers—all tied to project-scoped priming.
Is client-ctx-sys safe to install?
It is file-first and may read or write project directories; review the Security Audits panel on this page and restrict paths that hold client secrets.
SKILL.md
READMESKILL.md - Client Ctx Sys
Client context system — file-first wiki with project-scoped auto-priming, meeting ingestion, and Obsidian-compatible knowledge graph. # client-ctx-sys Source: ./client-ctx-sys/ { "name": "client-ctx-sys", "source": "./client-ctx-sys/", "description": "Client context system — file-first wiki with project-scoped auto-priming, meeting ingestion, and Obsidian-compatible knowledge graph." }