rye-source-context-intake

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.