skills.rest
BakerSean168
BakerSean168COMMUNITY
Explore all skills by this author →
WebsiteGitHub

thought-forest-note-refactor

Refactor legacy Thought Forest clusters into atomic concepts, syntheses, and MOC pages.

Updated Aug 27, 2026
Search Tags:#refactor#frontmatter#knowledge-base#note-management#migration-patterns#topic-cluster
One-click install
npx skills add https://github.com/BakerSean168/thought-forest --skill thought-forest-note-refactor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thought-forest-note-refactor
Source: https://github.com/BakerSean168/thought-forest/tree/main/config/skills/thought-forest-note-refactor
Command: npx skills add https://github.com/BakerSean168/thought-forest --skill thought-forest-note-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill cleans up and unifies an existing Thought Forest topic cluster by splitting oversized notes, merging duplicates, normalizing legacy frontmatter, and rebuilding concept, synthesis, and MOC layers without breaking existing entry points.

Core Features & Use Cases

  • Inventory and classify: map a topic cluster into atomic concepts, synthesis, and MOC structure.
  • Non-destructive migration: create or improve notes first and preserve legacy pages where backlinks exist.
  • Metadata repair and navigation: fix frontmatter, update tags, add related notes, and repair cross-links.

Quick Start

Use a staged, non-destructive migration by inventorying the cluster, creating atomic concepts, syntheses, and MOC pages, and applying the migration patterns.

Frequently Asked Questions about thought-forest-note-refactor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor oversized notes into atomic concepts without breaking existing backlinks?▼

You can refactor oversized notes by applying non-destructive migration patterns that create atomic concepts and syntheses first, preserving legacy pages where backlinks exist to maintain entry points. This ensures safe note management.

What is the best way to normalize legacy frontmatter across a knowledge base topic cluster?▼

Normalizing legacy frontmatter involves inventorying a topic cluster to map its structure, then repairing metadata, updating tags, and adding related notes without breaking cross-links. This metadata repair ensures consistent knowledge-base topology.

How do I merge duplicate notes while rebuilding MOC navigation in my knowledge base?▼

Merging duplicates and rebuilding MOC navigation requires classifying pages into atomic concepts, syntheses, and MOC layers. You apply migration patterns to normalize cross-links and update frontmatter safely across the topic cluster.

Can I use intake planning to guide non-destructive note migration for misclassified pages?▼

Yes, intake planning constrains note migration to safe, non-destructive changes guided by predefined migration patterns. It allows you to refactor misclassified pages, repair aliases, and update frontmatter without losing original entry points.

When should I avoid refactoring notes in my knowledge base?▼

You should avoid refactoring notes when a topic cluster is not undergoing intake planning or lacks a clear migration pattern. Changes are constrained to metadata repair and topology redesign, preventing unguided structural modifications.

Related Skills

Explore More Content & Communication Skills→
henkisdabrohenkisdabro
77

gtm-variables

Configure Google Tag Manager variables for data layer reading and value reuse.

Community
Basic
jay6697117jay6697117

agency-zk-steward

Organize atomic notes into a Luhmann-style knowledge network with validation loops.

Community
Advanced
abdu6666abdu6666
17

backlink-analyzer

Analyze backlink profiles to identify link authority and toxic links.

Community
Advanced
mattniedelmanmattniedelman

knowledge-organize

Identify orphan notes and propose relations in large note collections.

Community
Basic