rye-onboarding

Define structured Rye onboarding scopes with policies, plugins, and review gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up Rye for organizational use without structured guidance leads to inconsistent graph state, missing policies, and ingested data that does not align with team workflows, creating costly rework and unreliable knowledge outputs.

Core Features & Use Cases

  • Structured Scope Definition: Guides creation of onboarding scopes tied to specific organizational workflows (not source channels) with clear boundaries, owners, and stated purpose.
  • Policy & Plugin Configuration: Sets up source context policies, human review gates, evidence rules, and enables required plugins for tracking provenance and organizational vocabulary.
  • Use Case: Use this skill when setting up Rye for a new team process like customer renewal tracking, or revising intake policies after repeated context gaps during source data ingestion.

Quick Start

Use the rye-onboarding skill to walk through setting up your first Rye onboarding scope for your team's customer renewal review workflow, including defining boundaries, source policies, and required plugins.

Frequently Asked Questions about rye-onboarding

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

FAQPage Schema
How do I set up a knowledge graph for organizational workflow adoption without creating inconsistent graph state?

Knowledge graph setup requires structured scope definition before source data ingestion to align team workflows. Defining onboarding scopes tied to specific organizational boundaries eliminates ad-hoc configuration and prevents costly rework from unreliable knowledge outputs.

What is structured scope definition for a knowledge graph and when do I need it?

Structured scope definition establishes onboarding boundaries, owners, and stated purpose tied to organizational workflows rather than source channels. It is needed when setting up new team processes or revising intake policies after repeated context gaps during source data ingestion.

How do I configure source context policies and plugin binding for knowledge graph ingestion?

Source context policies and plugin binding are configured during onboarding scope creation by setting human review gates, evidence rules, and required plugins for tracking provenance and organizational vocabulary within the defined workflow boundaries.

Can I use rye-onboarding to revise intake policies after repeated context gaps during source data ingestion?

Yes, rye-onboarding applies to scope revision after repeated context gaps by redefining onboarding boundaries, source policies, and required plugins to realign ingested data with team workflows and restore reliable knowledge graph outputs.

What is the best way to enforce review gates for evidence-backed knowledge graph promotion?

Evidence-backed knowledge graph promotion is enforced through scoped policy compilation that sets human review gates and evidence rules during onboarding setup, ensuring source data meets organizational workflow requirements before graph promotion.

Why does my knowledge graph setup produce missing policies and data that does not align with team workflows?

Knowledge graph setup produces missing policies and misaligned data when structured onboarding scope definition is skipped before source data ingestion, leading to inconsistent graph state and ingested data that fails to match team workflow requirements.