← RAG & GenAI CopilotCONTENT HISTORY
WHAT CHANGED
Update to RAG & GenAI Copilot
Snapshot Nov 3, 2026 · 00:12 UTC · version 0.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save RAG & GenAI Copilot and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Implement or scaffold a RAG pipeline from requirements or existing repository using available coding tools and actual test evidence.",
"included_files": [],
"name": "build-rag-system",
"skill_md_contents": "---\nname: build-rag-system\ndescription: Implement or scaffold a RAG pipeline from requirements or existing repository using available coding tools and actual test evidence.\n---\n\n\n# Build or extend a RAG system\n**Trigger:** User asks for runnable source, implementation, integration or a working prototype rather than a written proposal.\n\n1. Check actual filesystem/repository access, programming language/framework, authenticated providers, test facilities and execution permissions. If absent, deliver precise source/examples and clearly identify unexecuted steps.\n2. Inspect the existing repository, versions, tests, deployment constraints and auth model before modifying code. Preserve behavior and avoid unrequested rewrites.\n3. Freeze the vertical slice: one authorized source, deterministic parsing, metadata+document IDs, idempotent ingestion, one retrieval method, grounded response with source IDs, graceful no-answer behavior.\n4. Implement interfaces for ingestion, indexing, retrieval, optional reranking and generation. Avoid hardcoding versions, credentials, vector dimensions or model names without checking provider compatibility.\n5. Include safe defaults: per-tenant authorization before retrieved content reaches models; timeouts; bounded batch sizes; retry discipline; idempotency; secret redaction; source deletion/update propagation.\n6. Test each boundary separately using fixtures. Then test end-to-end with no-answer, duplicate document, unauthorized user and injected document cases.\n7. Record commands actually run, result summaries and failures. Require approval for deployment or changes to live indexes.\n\nOutputs: source diff or project structure, configuration examples (no secrets), commands, tests, sample trace and limitations. Read `../../references/implementation-contracts.md`, `../../references/evidence-contract.md`, `../../references/security-boundaries.md`.\n"
}SHA-256 of public snapshot: c47c733e2b30ef05456ac97452b31dc113e697649a4966aadc960a182394f0f7