skills.rest
jamieadams-nerd
jamieadams-nerdCOMMUNITY
Explore all skills by this author →
GitHub

knowledge-mgmt-rules

Define and enforce knowledge management rules for the UMRS reference library.

Updated Dec 4, 2025
Search Tags:#rag#ingestion#knowledge-management#reference-library#familiarization#refs-manifest#collection-naming
One-click install
npx skills add https://github.com/jamieadams-nerd/umrs-project --skill knowledge-mgmt-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-mgmt-rules
Source: https://github.com/jamieadams-nerd/umrs-project/tree/main/.claude/skills/knowledge-mgmt-rules
Command: npx skills add https://github.com/jamieadams-nerd/umrs-project --skill knowledge-mgmt-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Knowledge management rules for the UMRS reference library ensure consistent acquisition, ingestion decisions, naming, storage, version tracking, and decommissioning across a growing corpus.

Core Features & Use Cases

  • Acquisition rules for documenting sources and ensuring provenance.
  • Decision framework for RAG ingestion vs familiarization to optimize resources.
  • Storage layout and naming conventions to keep references organized and auditable.
  • Decommissioning and version-tracking processes to maintain lifecycle discipline.

Quick Start

Follow these rules when acquiring new reference documents or managing RAG collections to ensure consistent metadata.

Frequently Asked Questions about knowledge-mgmt-rules

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

FAQPage Schema
What are knowledge management rules for a RAG reference library?▼

Knowledge management rules for a RAG reference library define structured guidelines for acquisition, ingestion decisions, naming, storage, versioning, and decommissioning to ensure auditable and organized reference management.

How do I decide between RAG ingestion and familiarization for new documents?▼

A decision framework for RAG ingestion versus familiarization evaluates resource optimization, applying process constraints to determine whether to ingest documents for retrieval or keep them for contextual familiarization only.

What naming conventions should I use for a reference library collection?▼

Reference library collection naming conventions enforce structured guidelines and manifests to keep references organized, auditable, and consistently stored across growing RAG workflows.

How do I track provenance and versioning when acquiring reference documents?▼

Acquisition rules for documenting sources ensure provenance, while lifecycle governance specifies version tracking and storage layout constraints to maintain discipline across the reference corpus.

When should I decommission references from a RAG knowledge base?▼

Decommissioning processes specified by lifecycle governance rules determine when to remove outdated references, maintaining collection discipline and ensuring the RAG knowledge base stays auditable and current.

Related Skills

Explore More Education & Research Skills→
bbolek-apbbolek-ap

read-documents

Inventory, read, and synthesize source documents from .project/input/ folders.

Community
Intermediate
jamieadams-nerdjamieadams-nerd

corpus-familiarization

Automates initial familiarization of new RAG reference material into knowledge artifacts.

Community
Advanced
333-333-333333-333-333

flutter-design-tokens

Define centralized Flutter design tokens for spacing, sizes, and radii.

Community
Intermediate
dmarinsdmarins

deprecation-and-migration

Generate migration plans for legacy APIs with database schema evolution strategies.

Community
Advanced