etylsarin/agent-memory
src/orchestrator/skills/agent-memory/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add etylsarin/opencastle agent-memoryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 17, 2026, 3:04 AM171.4s2 files scanned
SKILL.md
- name:
- agent-memory
- description:
- 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.
Agent Memory Protocol
Expertise File
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.
Update Triggers
| 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" |
Retrieval & Delegation
Query before delegating, then include a concise context block in the prompt:
grep -A5 "## Developer" .opencastle/AGENT-EXPERTISE.md
Example 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
Workflow
- Before delegating: Read
.opencastle/AGENT-EXPERTISE.md, check Strong/Weak areas, add conciseAgent Contextto the prompt.
- Validate: the selected agent has a Strong area matching the task or no conflicting Weak entries.
- After task completes: Update expertise (success → Strong, 2+ retries → Weak, files → Familiarity) and append file relationships to
.opencastle/KNOWLEDGE-GRAPH.md.
- Validate: the expertise file contains the new entry and the timestamp is today's date.
- On DLQ failure: Add Weak Area with reference to the failure ID and link to logs.
- Validate: failure ID and link appear in the Weak Area entry.
Pruning
Prune entries older than 6 months, remove familiarity for deleted paths, and consolidate duplicates.
- Validate: run
rg "— [0-9]+ tasks" .opencastle/AGENT-EXPERTISE.mdafter pruning to confirm no stale paths remain.
Knowledge Graph
File dependency graph and cross-agent relationships. See KNOWLEDGE-GRAPH.md for entity types, templates, triggers, and queries.
Related Skills
etylsarin/validation-gates
development
VerifiedTrustedCommunity
Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, and smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.
44SKILL.mdUpdated May 17, 2026
etylsarin/testing-workflow
development
VerifiedTrustedCommunity
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, and flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
44SKILL.mdUpdated May 17, 2026
etylsarin/team-lead-reference
development
VerifiedTrustedCommunity
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, and defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting a delegation session, running a multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.
44SKILL.mdUpdated May 17, 2026
etylsarin/session-checkpoints
testing
VerifiedTrustedCommunity
Saves and restores session state including task progress, file changes, and delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.
44SKILL.mdUpdated May 17, 2026