setup

Initialize a conversation-distill knowledge repository with MCP permissions and Notion caching.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines and automates initializing a conversation-distill knowledge repository, removing the manual steps of configuring channels, permissions, repo structure, and initial state so teams can quickly start capturing and indexing knowledge.

Core Features & Use Cases

  • Service Detection: Detects available MCP servers (GitHub, Discord, QMD) and Notion credentials, reporting status and required actions.
  • Permissions Management: Merges or creates .claude/settings.json permission allowlists for MCP tool usage, with safe merging and user confirmation.
  • Repo Initialization: Creates config.json from a template, preserves or initializes .distill/state.json, creates authored-docs folders, updates .gitignore, and optionally commits changes.
  • Use Case: A developer onboarding a new project can run this to prepare Notion caching, QMD indexing, and MCP permissions before running automated daily distillation.

Quick Start

Run /conversation-distill:setup and follow the interactive prompts to detect services, configure channels, merge permissions, initialize the repo structure, and commit any changes.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I set up a knowledge repository for daily conversation distillation?

To set up a knowledge repository, initialize the repo structure by creating config.json, preparing Notion caching, configuring MCP permissions, and creating .distill state and authored-docs folders for daily distillation workflows.

Do I need an existing git repository before configuring conversation-distill?

Yes, configuring conversation-distill requires an existing git repository. You must also have permission to update .gitignore, write config.json, merge .claude/settings.json allowlists, and commit changes.

How does MCP permissions management work when initializing a knowledge repo?

MCP permissions management merges or creates a .claude/settings.json allowlist for MCP tool usage. It performs safe merging of existing configurations and requires user confirmation before applying changes.

Can I use Notion caching and QMD indexing without manual configuration?

Yes, the setup process includes service detection that automatically identifies available MCP servers and Notion credentials, reporting status and required actions to prepare Notion caching and QMD indexing without manual configuration.

What happens to my existing .distill state file during knowledge repo initialization?

During knowledge repo initialization, the setup process preserves your existing .distill/state.json file. If it does not exist, it initializes a new state file to track daily distillation workflows.

Does the knowledge repo setup automatically commit changes to git?

Knowledge repo setup optionally commits changes to git. It updates .gitignore, creates folder structures and configuration files, and prompts you to confirm before committing the changes.