From awareness-memory
Search Awareness memory for past implementations, decisions, or relevant context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/awareness-memory:recallThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search Awareness Memory for relevant context.
Search Awareness Memory for relevant context.
Query: $ARGUMENTS
Try MCP tools first (awareness_recall).
If MCP tools are NOT available, use Bash to call the local daemon HTTP API directly:
# F-053: single-parameter — daemon picks scope/mode/detail/weights.
curl -s -X POST http://localhost:37800/mcp -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"awareness_recall","arguments":{"query":"why did we pick pgvector?","limit":10}}}'
The response is JSON-RPC: result.content[0].text contains the tool output as JSON string.
REWRITE the user query into a complete natural-language question with context. Example: "auth bug" → "authentication bug in login flow, JWT token handling, session management"
Call awareness_recall with ONE parameter:
query: the rewritten natural-language questionlimit: default 6, max 30token_budget: 5K (default, card-heavy) / 30K (mixed) / 60K+ (raw-heavy)Daemon auto-routes across memories + knowledge cards + workspace graph and picks the right detail level for your token budget. You do NOT need to choose scope, recall_mode, detail, ids, or weights.
Present results clearly:
Rules:
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub everest-an/awareness-sdk --plugin awareness-memory