Access Granted

    Second Brain
    Setup Health
    Check

    Run the existing health-check package, copy the safe summary, then use the template below to turn the result into one useful next fix.

    Quick Start

    1. 1. Open a terminal in the repo or folder where you use Claude Code.
    2. 2. Run the health-check package with the command below.
    3. 3. Copy only the scores, summary, and top recommendations.
    4. 4. Fill the diagnosis template and remove private data before sharing.
    5. 5. Fix the first missing layer before adding new workflows.

    Run the check locally

    terminal
    npx @iwo-szapar/second-brain-health-check --no-open

    The health check is meant to inspect your local setup. Keep secrets, raw customer data, private repo code, and API keys out of anything you paste elsewhere.

    Diagnosis Template

    Paste this into Claude Code after the check

    This keeps the follow-up structured. It asks for the state of the setup, not your private files.

    second-brain-health-check-diagnosis.md
    # Second Brain Setup Health Check

## My context
Role:
Audience type: founder/operator | consultant/agency | overloaded operator | other
Current AI setup:
Biggest workflow leak:
Urgency:

## Health check output
Overall score:
Setup Quality:
Usage Activity:
AI Fluency:
Brain maturity:
Context engineering patterns:
Top recommendations:

## What I need
1. Tell me the highest-leverage missing layer.
2. Pick the first fix I should make this week.
3. Convert that fix into a small checklist or skill.
4. Route me: DIY setup, MemoryOS, or Second Brain V2.

## Privacy confirmation
I removed secrets, customer data, raw private repo code, and API keys before sharing this.
    Read the Result

    What the scores mean

    0-39

    Build the spine first: CLAUDE.md, memory files, current projects, decision log, and one real workflow.

    40-69

    You have pieces. Now turn repeated work into skills and make the memory loop consistent.

    70+

    Optimize quality gates, evals, automations, and usage reporting before expanding the surface area.

    Share the smallest useful summary. The goal is diagnosis, not a full repo review.

    • Overall score and category scores
    • Brain maturity or setup maturity label
    • Top recommendations from the package
    • What you currently use Claude Code for
    • The recurring task that still feels clunky

    Fix the first layer before expanding

    If the check says your context, memory, or review loop is weak, adding more agents usually makes the setup noisier. Stabilize the spine first, then automate.

    Need memory maintenance?

    MemoryOS is the ongoing layer for health monitoring, decay detection, and memory improvement.

    See MemoryOS

    Want the full setup built?

    Second Brain V2 turns your role, workflows, and knowledge into a Claude Code operating system.

    See Second Brain