본문으로 건너뛰기
cccskills
무료GitHub에 공개

second-brain-graph

Analyse the vault's link graph and report on its shape: orphan rate, average degree, components, hubs, bridges and clusters, with what each number means for retrieval. Use this skill when the user asks about the health or structure of their graph, wants metrics, asks which pages are most connected or most isolated, or asks whether the vault is fragmented. Do NOT use for fixing what it finds, which is second-brain-lint, or for answering a content question.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Analyse the graph

The graph is the search space every answer is drawn from. Its shape decides whether retrieval reaches the relevant material in a few hops or reaches nothing.

Core rule

Report shape and what it means, never fix anything. This skill is read-only.

Workflow

  1. Run the scripts rather than reading files: scripts/vault_stats.py for counts and degree, scripts/link_check.py for orphans and breaks, scripts/graph_export.py when deeper analysis is wanted.
  2. Compute the four metrics: orphan rate, average degree, component count, stale-page rate.
  3. Identify hubs (pages that have swallowed the graph) and bridges (pages connecting otherwise separate clusters).
  4. Name the clusters. These are what the vault is actually about, which is reliably different from what the user would say it is about.
  5. Say what each number means for answering questions, not just the value.

Output format

Pages <n> | links <n> | avg degree <n>
Orphan rate <n>%      (healthy under 5)
Components <n>        (main holds <n>%)
Stale concepts <n>%   (untouched 90+ days)

Hubs: <pages with outsized degree, and whether to split them>
Bridges: <pages connecting clusters, and what breaks if they are wrong>
Clusters: <what the vault is actually about>

What this means: <two or three sentences>

Calibration

Never report page count or word count as a health signal. Both rise whether the vault is improving or not.

A single reading says little. If the user has recorded previous numbers, compare against them; if not, suggest recording these.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit an agent's context layout against the four places: system prompt, tools, history, tail. Use when the user asks to audit, review or fix their agent's context, prompt caching, token spend per turn, or CLAUDE.md / AGENTS.md layout. Read-only: reports findings and a fix list, changes nothing. Do NOT use for writing evals (evals-bootstrap) or for loop design (goal-test).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

undefined-ui/second-brain-os1.1천2026년 10월 14일 업데이트

Scaffold a first eval suite for an agent: mine real failures into cases, write behavioural checks over traces, and generate the runner. Use when the user wants evals, regression tests for an agent, a golden set, or asks how to know a prompt/model change did not break things. Do NOT use for a single task's done-check (goal-test) or for auditing context (context-audit).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

undefined-ui/second-brain-os1.1천2026년 10월 14일 업데이트

Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

undefined-ui/second-brain-os1.1천2026년 10월 14일 업데이트

goal-test

무료

Turn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

undefined-ui/second-brain-os1.1천2026년 10월 14일 업데이트

Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

undefined-ui/second-brain-os1.1천2026년 10월 14일 업데이트

Import a large archive into the vault in controlled batches: triage what is worth ingesting, process oldest first, checkpoint after every batch, and keep cost visible. Use this skill whenever the user wants to import years of bookmarks, an export from another notes app, a downloads folder, a chat history dump, or says "backfill", "bulk import", "process my archive". Do NOT use for ingesting one or a few new sources, which is second-brain-ingest.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

undefined-ui/second-brain-os1.1천2026년 10월 14일 업데이트

undefined-ui의 스킬 모두 보기

이 스킬의 문제 신고