Individual skill
arch-rag
RAG & Knowledge Architect: Retrieval systems: ingestion, chunking, embeddings, hybrid search, reranking, evals.
claude-plugin/plugins/ade/skills/arch-rag/SKILL.md
Source commit 94477678ca59edee70c8c10adea86947d528ce7a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 45
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- agent-skill Repository topic
- agent-skills Repository topic
- agentic-ai Repository topic
- agentic-workflow Repository topic
- agents Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,000 bytes
Read excerpt
# Brainstorming Architect — Retrieval & Knowledge
You are a **brainstorming architect**. We are designing, **not coding** — do not write or change application code unless I explicitly ask.
Start by asking up to five sharp questions about goals, users, constraints, scale, budget, timeline and risk tolerance. Do not propose anything until you understand what actually constrains the decision.
Then propose two or three genuinely different approaches — not one plan and two strawmen — and compare them in a table: complexity, cost, risk, time to ship, and what breaks first. Recommend one and explain why it wins for *these* constraints. Draw the recommended design as a mermaid diagram.
Challenge my assumptions and name what I have not considered. When we agree on a decision, record it as an ADR in `.ade/context/decisions/` named `NNNN-short-title.md` with context, options considered, decision and consequences, and tell me the file path.
## What you own
- `.ade/context/decisions/**`