corpus-fileback

Convert explicitly confirmed decisions into durable wiki pages in a Lorekit corpus.

5|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/GYF0311/lorekit --skill corpus-fileback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corpus-fileback
Source: https://github.com/GYF0311/lorekit/tree/main/skills/corpus-fileback
Command: npx skills add https://github.com/GYF0311/lorekit --skill corpus-fileback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents accidental or unverified content from being written into the central Lorekit corpus while still letting you turn confirmed decisions and syntheses into durable, cross-referenced knowledge.

Core Features & Use Cases

  • Confirmation gate for writing: Only files into 知识库/ when the user explicitly confirms specific fileback phrases.
  • Corpus-aware filing workflow: Resolves subjects using corpus filing rules, searches for existing pages, and appends or creates pages accordingly.
  • Provenance and verification safeguards: Preserves source backlinks and runs the required local verification (typically sync and quick lint) before reporting changes.

Quick Start

Confirm what should be written using the required confirmation phrase, then ask the AI to file it into the central Lorekit corpus.

Frequently Asked Questions about corpus-fileback

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

FAQPage Schema
How do I safely write AI-generated conclusions into a persistent wiki corpus?

To write AI-generated conclusions into a persistent wiki corpus safely, use a confirmation gate that requires explicit user authorization before filing content into the central corpus under specific knowledge directories.

What is a confirmation gate for wiki filing and how does it prevent data loss?

A confirmation gate for wiki filing prevents unverified content persistence by requiring explicit user confirmation phrases before appending or creating wiki pages, ensuring only authorized syntheses enter the central corpus.

How do I preserve backlinks when appending new decisions to existing wiki pages?

To preserve backlinks when appending decisions to existing wiki pages, the filing workflow searches for existing pages using corpus filing rules, appends confirmed content, and maintains source provenance throughout the local sync verification process.

Does wiki filing require running lint verification before reporting changed paths?

Yes, wiki filing requires running local sync and quick lint verification before reporting changed paths, ensuring that newly created or updated pages in the knowledge base pass corpus-local verification checks.

Can I create new pages in a central corpus without explicit user confirmation?

No, creating new pages in a central corpus requires explicit user confirmation phrases, preventing accidental or unverified content from being written into the durable knowledge base while preserving source backlinks.

What's the best way to manage knowledge base updates for reusable syntheses?

The best way to manage knowledge base updates for reusable syntheses is to resolve subjects using corpus filing rules, locate or create pages under the knowledge directory, and run local verification before reporting changes.