agentsclimarketplace

Llm wiki refactor

Skill po4yka/llm-wiki-skills/skills/llm-wiki-refactor

Portable Agent Skills for building, operating, evaluating, and governing LLM-Wiki knowledge systems.

Install
npx -y skills add po4yka/llm-wiki-skills --skill llm-wiki-refactor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Refactor an existing docs folder, Obsidian vault, or messy note collection into an LLM-Wiki structure. Use for applying an approved migration plan, with frontmatter normalization, raw/wiki separation, link repair, and review-safe restructuring; route no-write migration planning to llm-wiki-migration-planner.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.7 KB, as published. Nobody here has run it

LLM-Wiki Refactor

Goal

Reorganize existing documents into a safe LLM-Wiki without losing provenance, breaking links, or overwriting human synthesis.

When to use

  • The user has an approved migration plan and wants to physically reorganize an existing docs folder, Obsidian vault, or note collection into LLM-Wiki structure.
  • Existing notes contain human-authored synthesis, Obsidian wikilinks, or attachments that must survive the move without breaking.
  • The user needs frontmatter normalized, raw/wiki content separated, or protected pages preserved during restructuring.
  • Do not use this skill for planning-only work with no filesystem writes; route that to llm-wiki-migration-planner instead.

Inputs

  • Existing docs/vault/repository path.
  • Desired target: personal vault, repo wiki, team knowledge base or product prototype.
  • Whether changes should be dry-run only or applied.
  • Existing conventions: folders, tags, frontmatter, wikilinks, docs generator.

Procedure

1. Preflight

Before applying changes:

  • confirm git or backup exists;
  • identify generated vs human-authored content;
  • identify sensitive data;
  • detect Obsidian wikilinks and attachments;
  • find existing indexes, READMEs, ADRs, changelogs and source folders.

If no backup/git exists, produce a migration plan only.

2. Inventory

Produce counts by file type and rough category:

  • raw sources;
  • source summaries;
  • entity/concept pages;
  • project docs;
  • decisions/ADRs;
  • query-like notes;
  • assets;
  • unknown or mixed files.

3. Propose target mapping

Default mapping:

original raw documents -> raw/sources/
images/media/assets    -> raw/assets/
source summaries       -> wiki/sources/
people/orgs/tools      -> wiki/entities/
mechanisms/ideas       -> wiki/concepts/
trade-off docs         -> wiki/comparisons/
reviewed conclusions   -> wiki/synthesis/
chat/research answers  -> wiki/queries/

4. Create a dry-run plan

Do not move files immediately. Produce:

## Migration plan

| Current path | Proposed path | Page type | Confidence | Notes |
|---|---|---|---:|---|

Flag low-confidence moves and protected pages.

5. Apply in batches only when approved

When the user approves apply mode:

  • create a branch;
  • move files in small batches;
  • preserve links and attachments;
  • add or normalize frontmatter;
  • create wiki/index.md and wiki/log.md if missing;
  • run wiki-lint and re-verify that internal links resolve after each batch, before moving on to the next one.

6. Preserve human synthesis

Detect and preserve sections such as:

  • ## My synthesis
  • ## Opinion
  • ## Notes to self
  • <!-- human-owned:start -->

Do not rewrite these sections. Add protected markers if useful.

Output

## Refactor summary

## Inventory

## Proposed structure

## Migration table

## High-risk items

## Commands or file operations

## Post-migration lint findings

Safety gates

  • No deletion without explicit confirmation.
  • No apply mode without git or backup.
  • No silent conversion of wikilinks to Markdown links.
  • No flattening of raw sources into summaries.
  • No bulk frontmatter migration without dry-run.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.