rye-source-context-intake

Register external sources and classify items before creating Rye knowledge edges.

2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/BLTGV/project-rye --skill rye-source-context-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rye-source-context-intake
Source: https://github.com/BLTGV/project-rye/tree/main/skills/rye-source-context-intake
Command: npx skills add https://github.com/BLTGV/project-rye --skill rye-source-context-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @modelcontextprotocol/sdk, zod, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the risk of creating incorrect, unverified semantic connections in Rye from external source material like Slack messages, emails, or meeting recordings by enforcing a neutral registration and mandatory confirmation workflow before any knowledge is promoted.

Core Features & Use Cases

  • Connector-Neutral Source Registration: Register source accounts, containers, and items from any external provider (Slack, Fathom, email, API records, files) without assuming business meaning from connector metadata alone.
  • Mandatory Confirmation Gate: Require explicit user or admin confirmation of source purpose, allowed review contexts, default routing context, and never-infer rules before creating semantic Rye edges.
  • Evidence-Based Item Classification: Classify each source item as evidence, context signal, low signal, or noise, preserving provenance and audit trails for low-signal or noisy material. Use case: When ingesting Slack channel history for a new operational workflow, this skill ensures you do not incorrectly link channel members to company roles or create task edges from unconfirmed channel content until the source's purpose is explicitly validated.

Quick Start

Use the rye-source-context-intake skill to register your external source accounts and containers, classify incoming source items by evidence value, and collect confirmation decisions for source purpose before creating any semantic Rye knowledge connections.

Frequently Asked Questions about rye-source-context-intake

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

FAQPage Schema
How do I prevent incorrect semantic knowledge edges from unconfirmed Slack or email sources?

To prevent incorrect semantic knowledge edges, enforce neutral source registration and mandatory confirmation workflows before promoting external material. This validates source purpose, allowed contexts, and provenance, ensuring unverified Slack or email content does not create false connections.

How does connector-neutral source context intake work for external data?

Connector-neutral source context intake works by registering source accounts, containers, and items from any external provider without assuming business meaning from connector metadata. It mandates explicit confirmation of purpose and routing contexts before creating semantic edges.

What is evidence-based item classification in knowledge management?

Evidence-based item classification categorizes each ingested source item as evidence, context signal, low signal, or noise. This preserves provenance and audit trails, preventing low-signal or noisy material from being promoted into semantic knowledge graphs.

Do I need to confirm source purpose before creating semantic Rye edges?

Yes, mandatory confirmation of source purpose, allowed review contexts, default routing context, and never-infer rules is required before creating semantic Rye edges. This gate prevents unverified external source material from generating incorrect knowledge connections.

What's the best way to track provenance for external API records ingested into a knowledge base?

The best way to track provenance is to use a source context intake workflow that enforces connector-neutral registration and evidence-based classification. This preserves audit trails for API records, ensuring only confirmed sources generate knowledge edges.