Our review
Audits a personal "second brain" workspace by actually testing context retrieval, source access, workflow execution, and recurring routines, then writes a dated report.
Strengths
- Deliberately limited status vocabulary (PASS / PARTIAL / UNKNOWN / FAIL) that rules out vague scoring.
- Demands dated evidence rather than configuration screenshots: a declared source is not a reachable source.
- Four retrieval probes tied to the user's real work, each recording the declared route and any fallback search.
- Closes with at most three concrete next actions, each carrying a completion test.
Limitations
- Assumes an existing structure (SYSTEM.md, workspace/sources.md, decision journal, reviews/ folder) and does not apply to an arbitrary repo.
- Verification is bounded by what the agent can actually read and run in its environment.
- Produces a qualitative report with no metric or score, making runs hard to compare over time.
Run it periodically before relying on your second brain or its automations, to confirm everything still works.
Avoid it on a project without a documented second-brain workspace, or when you want a quantitative score instead of a diagnosis.
Security analysis
SafeThe skill instructs reading workspace files, running retrieval probes, and writing a dated markdown report. It does not include destructive commands, network exfiltration, credential handling, or obfuscated payloads. No declared tools are required beyond ordinary file access.
No concerns found
Examples
Run a healthcheck on my second brain and write the report to reviews/healthcheck-$(date +%Y-%m-%d-%H%M).md.Before I start this week, check whether a fresh session could figure out my current objective, an active project, a past decision, and where an important original file lives — and tell me which of those routes are broken.Go through workspace/sources.md and my scheduled jobs and tell me which sources I haven't successfully read recently and which recurring routines have no evidence of actually producing output.name: healthcheck description: Verify whether the second brain can retrieve current context, reach important sources, execute useful workflows, and support recurring behavior.
Healthcheck
This is a verification review, not a score-chasing exercise.
Read SYSTEM.md, the core workspace files, source registry, decision journal, installed skills, and recent healthcheck reports if present.
Create a new report under:
reviews/healthcheck-YYYY-MM-DD-HHMM.md
Review areas
Assess five areas using only these statuses:
PASS— directly verified with current evidence.PARTIAL— some useful behavior works, but meaningful coverage is missing.UNKNOWN— documented but not verified.FAIL— a required route or behavior is demonstrably broken.
1. Core context
Can a fresh session answer:
- who this is for,
- what matters now,
- who is served,
- important working preferences, without relying on this chat?
2. Retrieval
Run four realistic retrieval probes tied to the user's actual work:
- current objective or commitment,
- an active project or deliverable,
- a prior decision or lesson,
- an important original file or external record.
For each probe, record the declared route, evidence found, and whether fallback search was needed.
3. Source access
For each important source in workspace/sources.md, record:
- what it is authoritative for,
- access method,
- last successful read or dated evidence,
- known limitations.
Configuration alone is not proof of access.
4. Workflow execution
Select up to three workflows that matter to current objectives. Look for:
- clear trigger,
- inputs,
- useful output,
- validation,
- failure handling,
- evidence of an actual run.
5. Recurring behavior
Inspect any schedules, hooks, automations, or explicit human routines. Distinguish:
- documented intent,
- enabled trigger,
- evidence that the expected output actually happened.
Report format
Start with a one-paragraph conclusion.
Then include:
- status table for the five areas,
- four retrieval probes,
- source access table,
- up to three workflow checks,
- concrete issues grouped as:
- broken,
- unverified,
- optional improvement,
- up to three next actions with a clear completion test.
Do not manufacture problems to fill the report.
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.