← ClaudeAtlas

rnd-local-expertslisted

Use when discovering and surfacing project-local agents and skills from the target project's .claude/ directory — scan, read frontmatter, and present a structured summary for the Planner to reference in pre-registrations
oleksify/rnd-framework · ★ 0 · AI & Automation · score 78
Install: claude install-skill oleksify/rnd-framework
# R&D Local Expert Discovery ## Overview Some projects ship their own Claude Code agents and skills in `.claude/agents/` and `.claude/skills/`. These "local experts" are specialists tailored to the project's domain — a security reviewer, a domain-specific formatter, a testing harness builder. Surfacing them during planning allows pre-registration documents to route appropriate tasks to the right expert instead of a generic build phase. **Core principle:** Local experts are optional project-level assets. Their presence enriches the pipeline; their absence never blocks it. ## When to Use - Phase 0 (Discovery) of `/rnd-framework:rnd-start` — before the Planner runs - Anytime you need to know what project-specific agents or skills are available - When the Planner is assembling pre-registration documents and wants to delegate to a local specialist ## Discovery Process ### Step 1 — Scan for local agents Use Glob to enumerate agent files in the target project: ``` .claude/agents/*.md ``` Each `.md` file in that directory is a potential local agent. Read the YAML frontmatter of each file to extract: - `name` — the agent identifier - `description` — what the agent does and when to use it ### Step 2 — Scan for local skills Use Glob to enumerate skill files in the target project: ``` .claude/skills/*/SKILL.md ``` Each `SKILL.md` file is a potential local skill. Read the YAML frontmatter of each file to extract: - `name` — the skill identifier - `description` — what the ski