cache

Cache Notion pages to local markdown and rebuild the QMD search index.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/RealXP-Lab/armory --skill cache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cache
Source: https://github.com/RealXP-Lab/armory/tree/main/claude-plugins/conversation-distill/skills/cache
Command: npx skills add https://github.com/RealXP-Lab/armory --skill cache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a local markdown cache of Notion pages and ensures the QMD search index is current so teams avoid stale search results and manual reindexing across repositories.

Core Features & Use Cases

  • Notion caching: Fetches accessible Notion pages and stores them as local markdown in a repository-scoped directory for offline access and versioned authoring.
  • QMD indexing: Adds repository-prefixed QMD collections, updates the index, and runs embeddings to make cached content searchable while avoiding global collection name collisions.
  • Preflight and graceful fallback: Verifies config.json and QMD availability, checks for an optional NOTION_TOKEN and skips Notion fetches if the token is absent, and reports status and summary.
  • Use Case: Run after setup or periodically to refresh documentation search for engineering or content teams that source docs from Notion.

Quick Start

Run the cache skill to download Notion pages into the local .distill directory and update the QMD collections for this repository.

Frequently Asked Questions about cache

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

FAQPage Schema
How do I cache Notion pages as local markdown for offline access?

Caching Notion pages as local markdown involves fetching accessible pages via the Notion API and storing them in a repository-scoped directory, providing versioned authoring and offline access for your team.

How do I rebuild the QMD search index after updating documentation?

Rebuilding the QMD search index requires adding repository-prefixed collections and running embeddings to make the content searchable, which prevents global collection name collisions across different repositories.

Do I need a Notion API token to update my documentation search index?

You do not strictly need a Notion API token to update the search index; the system checks for an optional NOTION_TOKEN and gracefully skips Notion fetches if absent, proceeding with existing local markdown.

What are the prerequisites for syncing Notion documentation to a local search index?

Prerequisites for syncing Notion documentation include having a config.json file in the repository, QMD installed on the system for indexing, and an optional NOTION_TOKEN for accessing the Notion API.

Why are my QMD search results stale after editing Notion pages?

Stale QMD search results occur when the local markdown cache and search index are not refreshed; you must periodically run a reindexing process to fetch new Notion content and update the embeddings.

Can I avoid collection name collisions when indexing multiple repositories with QMD?

You can avoid QMD collection name collisions by using repository-prefixed collections, which ensure that each repository maintains unique index names when updating the search database.