ワンクリックでManusで任意のスキルを実行

relink-memory

スター2

フォーク1

更新日2026年5月21日 01:43

Retroactive wikilink pass over `<config-root>/memory/`. Scans every node file for plain-text mentions of known entities (people / clients / topics / workstreams / companies / domains), proposes converting them to `[[wikilinks]]`, and graduates heavily-mentioned persons into person pages. One-time migration per cortex v4.10+. Idempotent; gated by `memory/.migration-wikilink-relink-done` marker. Run once after upgrading; future memory writes use wikilinks natively per the canonical rule in cortex CLAUDE.md. Auto-fires when the user says: "relink my memory", "fix my wikilinks", "my graph is disconnected", "why isn't my obsidian graph showing edges", "back-fill the wikilinks", "graduate the people in my memory". Use `--rerun` to force re-scan after marker exists. Cost: 1-3 min for ~30 nodes. Token cost ~$0.10-0.50 per run.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

BrightWayAI

BrightWayAI/claude-cortex

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

relink-memory

See commands/relink-memory.md for the full workflow.

When to fire

Explicit: /relink-memory or /relink-memory --rerun.
Trigger phrases above.
Cortex auto-recall at conversation start MAY surface a one-line ping if it detects:
- memory/.migration-wikilink-relink-done doesn't exist
- AND there are ≥ 10 node files
- AND wikilink density is < 2× node count
- → suggest: "Heads up: your memory predates the v4.10 wikilink convention. Run /relink-memory once to back-fill plain-text entity mentions and graduate person pages."

Pre-flight

<config-root>/memory/ must exist with at least one node file.
Cortex v4.10+ installed (this skill assumes v4.10's wikilink discipline).

What this skill is NOT for

Editing entity content (entity files themselves aren't modified).
Modifying staged / archive / briefs / log directories.
Bulk text replacement of arbitrary strings — only known-entity plain-text mentions get converted.
Creating client / company / topic / workstream nodes — only person pages (via graduation backfill).

このリポジトリの他の Skills

同じリポジトリ

end-day

BrightWayAI/claude-cortex

End-of-day closing routine. Quick mode by default (v4.6+) — runs cortex auto-commit, reflective prompts, brief pre-stage, memory-index refresh, and close in 30 seconds to 3 minutes. Heavy steps (inbox triage, transcript review, mining of non-transcript sources) only run in `/end-day --full`, or when auto-offered because the day actually had transcripts (≥2) or inbox volume (≥5). Auto-fires on "/end-day", "wrapping up", "calling it a day", "done for today", "end of day", "closing out today". Quick mode is the default for every trigger; the user passes `--full` or accepts the auto-offer prompt to get the full chain. Reflection (Step 4) appends a `## Reflection` section to today's brief markdown — what tomorrow's `/brief` reads — AND to a longitudinal `memory/reflections.md` store (v4.13+). v4.13+ additions (End-Day Routine Improvement Spec): a per-source consent + cost gate (Step 0.7, Today's Brief required & first); Step 2c mines the brief artifact (task/outreach actions → memory write-backs + suppression lear

2026-06-082

sync-linked-entities

BrightWayAI/claude-cortex

Natural-language entrypoint for cross-artifact drift detection. Fires when the user has just made a meaningful change to a node (status flip, reframe, engagement wound down) and says "check the linked nodes," "sync linked artifacts," "make sure the related stuff is consistent," or similar. Resolves the source node from recent edit or context, then routes to /sync-linked-entities.

2026-05-282

start-workstream

BrightWayAI/claude-cortex

Create a new workstream node — cortex's primitive for ongoing initiative pipelines that span multiple projects, people, and topics. Walks a short interview (name, current state, pinned context, linked entities) and writes `<config-root>/memory/workstream/<slug>.md`. Auto-fires when the user says: "start a workstream", "begin tracking X as a workstream", "I'm starting a new initiative — X", "I'm working on a new initiative", "set up a workstream for X". Differentiation: - Project nodes (`client/<slug>`) capture a specific engagement. - Person pages capture a relationship. - Topic nodes capture a subject area. - Domain nodes capture a persistent area of work. - Workstreams capture an ongoing *initiative pipeline* with current state, pinned context, open loops, and linked entities — spans projects/people/topics. New in cortex v4.9.0. See `references/workstream-schema.md` for the full schema.

2026-05-212

indexer

BrightWayAI/claude-cortex

Regenerate `<config-root>/memory/index.md` — a deterministic, zero-LLM catalog of every memory node grouped by type with decay-state flags. Auto-fires in THREE scenarios: 1. CHAIN STEP: invoked as Step 6 of `/end-day` and as the final step of `/cleanup`. Runs after user-gated changes are committed so the index reflects current state. 2. DEFERRED: when `/remember` writes a new entry, it appends a line to `<config-root>/memory/staged/queues/reindex`. The next `/end-day` or `/cleanup` notices the queue and runs the indexer. 3. EXPLICIT: user runs `/reindex`, or says "regenerate the memory index", "rebuild the catalog", "refresh memory/index.md". This skill has zero LLM cost in steady state. It is a file-walk + string-extract + write. No reasoning, no synthesis — see references/memory-index.md for the deterministic spec.

2026-05-212

listen

BrightWayAI/claude-cortex

Nightly autonomous ingest pipeline. Pulls yesterday's calendar / Gmail / Slack / transcripts / Drive activity into `<config-root>/archive/YYYY-MM-DD/` (immutable substrate), runs the mining agents against the archive, stages all proposed memory commits to `staged/commit-drafts/YYYY-MM-DD.md`, and refreshes `memory/hot.md`. Designed for unattended scheduled execution — no user gates. Auto-fires when the user says: "ingest yesterday", "run nightly ingest", "what happened yesterday I haven't captured", "mine yesterday's calendar", "process yesterday's transcripts". Most users register it on a schedule (11pm or 5am) via core-ops `/register-schedules` and never invoke it by hand. Pair with `/morning` for the interactive review-and-merge of the staged draft.

2026-05-212

morning

BrightWayAI/claude-cortex

The JARVIS morning routine. Reads the most-recent overnight `/listen` draft at `<config-root>/memory/staged/commit-drafts/`, walks the user through each proposed memory commit (accept / reject / edit / defer), applies accepted proposals to active memory nodes with v4.4 drift-detection, refreshes `memory/hot.md` and `memory/index.md`, and optionally chains into `/brief`. Auto-fires when the user says: "good morning", "start my day", "what happened overnight", "morning routine", "merge overnight ingest", "review last night's proposals". Most natural trigger is just opening a session and saying "good morning" — the router suggests `/morning` and the chain begins. Read-write to active memory but only for user-accepted proposals. Never silently merges, even for high-confidence proposals.

2026-05-212

name

relink-memory

description

relink-memory

See commands/relink-memory.md for the full workflow.

When to fire

Explicit: /relink-memory or /relink-memory --rerun.
Trigger phrases above.
Cortex auto-recall at conversation start MAY surface a one-line ping if it detects:
- memory/.migration-wikilink-relink-done doesn't exist
- AND there are ≥ 10 node files
- AND wikilink density is < 2× node count
- → suggest: "Heads up: your memory predates the v4.10 wikilink convention. Run /relink-memory once to back-fill plain-text entity mentions and graduate person pages."

Pre-flight

<config-root>/memory/ must exist with at least one node file.
Cortex v4.10+ installed (this skill assumes v4.10's wikilink discipline).

What this skill is NOT for

Editing entity content (entity files themselves aren't modified).
Modifying staged / archive / briefs / log directories.
Bulk text replacement of arbitrary strings — only known-entity plain-text mentions get converted.
Creating client / company / topic / workstream nodes — only person pages (via graduation backfill).