Creates and queries agent expertise profiles in AGENT-EXPERTISE.md, increments file-familiarity counters after each task, and ranks candidate agents by recency and task-area match. Use when deciding which agent should handle a file, checking who last worked on a module, recording task outcomes, or assigning work based on past performance.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Location: .opencastle/AGENT-EXPERTISE.md — one section per agent with Strong Areas, Weak Areas, and File Familiarity tables.
Entry format: Area | Evidence | Last Updated — e.g. Server Components | Built TAS-42 | 2026-03-15. File familiarity: - src/lib/search/ — 3 tasks.
| Trigger | Action |
|---|---|
| First-attempt success | Update Strong |
| 2+ retries | Update Weak |
| File modified | Increment familiarity |
| DLQ failure | Add Weak with ref |
| >3 months stale | Mark as "stale" |
Query before delegating, then include a concise context block in the prompt:
grep -A5 "## Developer" .opencastle/AGENT-EXPERTISE.mdExample prompt block: Agent Context: Strong — Server Components (3 tasks); Weak — Component styling (2 retries); Familiar — src/lib/search/ (2 tasks)
Update after task completion:
# Append a Strong Area entry
printf '| %s | %s | %s |\n' "Server Components" "Built TAS-42" "$(date +%Y-%m-%d)" >> .opencastle/AGENT-EXPERTISE.md
# Increment file familiarity
awk '/src\/lib\/search\// { if (match($0, /[0-9]+/)) { n = substr($0, RSTART, RLENGTH) + 1; sub(/[0-9]+[[:space:]]*tasks?/, n " tasks") } found=1 } {print} END { if(!found) print "- `src/lib/search/` — 1 task" }' \
.opencastle/AGENT-EXPERTISE.md > tmp && mv tmp .opencastle/AGENT-EXPERTISE.md.opencastle/AGENT-EXPERTISE.md, check Strong/Weak areas, add concise Agent Context to the prompt..opencastle/KNOWLEDGE-GRAPH.md.Prune entries older than 6 months, remove familiarity for deleted paths, and consolidate duplicates.
rg "— [0-9]+ tasks" .opencastle/AGENT-EXPERTISE.md after pruning to confirm no stale paths remain.File dependency graph and cross-agent relationships. See KNOWLEDGE-GRAPH.md for entity types, templates, triggers, and queries.
f5c8508
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.