Supporting material availability

This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:

• <support-root>/scripts/install.sh

Obtain the required material from the declared upstream source, or from a user-provided installation of that source. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.

Context Kit

When to Use

Use this skill when the user wants to:

• Set up durable personal context files for Claude Code or another coding agent
• Compare Context Kit's Personal Context Artifact pattern with an existing memory or project-notes system
• Adapt a context template structure without copying private details into the chat
• Review whether a one-line installer or downloaded skill pack is appropriate before running it
• Create a safer, local-first plan for CRM notes, open loops, session digests, or morning briefings

Overview

Context Kit is an external project that organizes personal context into Markdown artifacts and companion Claude Code skills. This skill helps the user decide what to adopt, where to store it, and how to avoid turning a useful context system into a pile of sensitive data.

Treat every personal context file as private by default. These files may contain identity details, family context, work history, contact notes, mental models, health constraints, or relationship information. Do not paste them into third-party tools, public repositories, issue trackers, or model contexts unless the user explicitly approves the exact subset.

Safety Rules

1. Do not run a remote install script until the user has seen the command, source repository, and target paths it will write to.
2. Prefer cloning or downloading the repository for inspection before executing any installer:

   git clone https://github.com/JDDavenport/context-kit.git
   cd context-kit
   sed -n '1,220p' scripts/install.sh
   

3. Never store passwords, API keys, recovery codes, private keys, session tokens, or payment details in personal context artifacts.
4. If the user wants contact notes or CRM files, store only information they are comfortable keeping in local plaintext Markdown.
5. Before adding these files to a repo, confirm .gitignore excludes the chosen private context directory.
6. If adapting Context Kit to a team or company setting, separate personal context from company-confidential or customer-confidential information.

Setup Workflow

1. Ask what the user wants Context Kit to improve: session startup context, voice consistency, relationship memory, open-loop tracking, daily briefings, or handoff summaries.
2. Inspect the upstream project and installer before running anything.
3. Choose a storage location:
   • Claude Code default: ~/.claude/context/ and ~/.claude/skills/
   • Project-local context: .agent/context/ or another ignored directory
   • Portable setup: a private notes repo with explicit sync rules
4. Create a minimal starter set before filling everything:
   • pca-wiki.md for durable identity and domains
   • pca-mental-models.md for decision rules
   • pca-voice.md for writing preferences
   • pca-protocols.md for hard rules and boundaries
5. Add only enough detail to make the next agent session useful. Leave sensitive, speculative, or outdated details out until there is a clear reason to include them.
6. Add a recurring review cadence. Personal context goes stale quickly; stale context is worse than no context when it drives decisions.

Installation Review Checklist

Before running an installer, verify:

• The repository URL is exactly the one the user intended
• The script writes only to expected local directories
• The script does not upload files, send telemetry, or edit shell startup files unexpectedly
• The target directories are not inside a public repo
• The user has a rollback path, such as removing the copied templates and skills

…