Automated summary

Runs a verification audit of a "second brain" (core context, retrieval, source access, workflows, recurring automation) and writes a dated report using PASS/PARTIAL/UNKNOWN/FAIL statuses.

Strengths

Replaces subjective scoring with directly verified evidence, using four explicit statuses and keeping UNKNOWN separate from FAIL.
Requires four realistic retrieval probes tied to the user's actual work, recording the declared route and whether fallback search was needed.
Explicitly separates documented intent, an enabled trigger, and evidence that the expected output actually occurred, for both sources and automations.
Forbids inventing problems to fill the report and caps follow-up at three next actions, each with a completion test.

Limitations

Assumes a specific repository layout (SYSTEM.md, workspace/sources.md, decision journal, reviews/) and produces a thin or blocked report if those files are absent.
Output stays qualitative: no overall score or aggregate metric, so tracking health over time means re-reading prior reports.
It only diagnoses and recommends; it does not repair anything, so remediation remains manual.

When to use it

Run it periodically, or after restructuring your knowledge system, to confirm a fresh session can actually recover context and execute the workflows that matter.

When not to use it

Skip it on a workspace with no context files, source registry, or defined workflows, where there would be almost nothing to verify.

Security analysis

Safe

Quality score90/100

The skill instructs reading workspace files and generating a healthcheck report. It does not include any destructive commands, network calls, or exfiltration of data. All actions are local read/write operations within the workspace.

No concerns found

How this analysis is made

Examples

Routine periodic healthcheck

Run a healthcheck on my second brain and write the report to reviews/. I want to know if a fresh session could actually pick up my current objectives.

Post-restructure verification

I just reorganized workspace/sources.md and my decision journal. Verify that retrieval still works with four probes from my real work and tell me what's broken vs just unverified.

Automation reality check

Check whether my scheduled workflows and hooks actually produce output, not just whether they're documented, and give me up to three next actions with completion tests.

name: healthcheck description: Verify whether the second brain can retrieve current context, reach important sources, execute useful workflows, and support recurring behavior.

Healthcheck

Name: Second Brain Healthcheck
Author: Skills Guide Bot

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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/second-brain-healthcheck-muar2yyu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/second-brain-healthcheck-muar2yyu/download' --output '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md.part' && mv '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md.part' '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md' && test -s '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/healthcheck' && cp -R '.skill-downloads/second-brain-healthcheck-muar2yyu' '.claude/skills/healthcheck'

Cursor

test -f '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md' && test -s '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/healthcheck' && cp -R '.skill-downloads/second-brain-healthcheck-muar2yyu' '.cursor/skills/healthcheck'

Codex

test -f '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md' && test -s '.skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/healthcheck' && cp -R '.skill-downloads/second-brain-healthcheck-muar2yyu' '.agents/skills/healthcheck'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/second-brain-healthcheck-muar2yyu'

openskills read 'second-brain-healthcheck-muar2yyu'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/second-brain-healthcheck-muar2yyu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot