yinanli1917-cloud
UserSearch Apple Notes semantically with Claude Code. BGE-M3 embeddings, ChromaDB, fully local. Drop-in skill — no MCP setup, no API keys.
Categories
Indexed Skills (9)
codex-break-loop
Post-bug-fix retrospective — classify root cause, identify prevention, write the lesson into specs. Use after fixing any non-trivial bug, when a task involving 'fix', 'bug', 'debug', or 'diagnose' is being finished, or when the user asks 'what went wrong', 'why did this break', 'root cause', or 'lessons learned'. Also use when the lifecycle hook reminds you to run break-loop.
codex-spec-bootstrap
Analyze a codebase and generate durable spec files from existing patterns, architecture, and conventions. Use to initialize or refresh .codex/spec/ for a project. Also use when the lifecycle hook reminds you to run spec-bootstrap, when a project has empty or template-only specs, when the user says 'generate specs', 'initialize specs', 'bootstrap specs', or 'make the codebase context durable'.
grill-me
Brainstorm engine — interview the user about a plan/design, auto-write PRD and context manifests as answers resolve. Use when the user wants to stress-test a plan, brainstorm a feature, design architecture, or says 'grill me', 'brainstorm', 'let's plan', 'design this', or describes a new feature they want to build. Also use when the workflow phase is 'planning' and a task is active.
searching-apple-notes
Search, recall, and create Apple Notes via semantic vector search powered by Qwen3-Embedding-0.6B and ChromaDB. Use when the user asks to find notes, search memos, recall what they previously wrote, needs note content as context for an answer, or wants to save an insight from the current conversation into Apple Notes. Triggers on phrases like "find in my notes", "search my notes", "what did I write about", "recall my note on", "do I have notes about", "save this to notes", "save this insight", "查我的笔记", "找一下我写过的", "存到备忘录".
codex-before-dev
Load task PRD and project specs before writing code. Use before implementation, refactors, or harness changes.
codex-check
Verify recent Codex harness or project changes against task requirements, specs, tests, and rollout checks.
codex-continue
Resume the current Codex harness task. Use when returning to a task, when the user asks what state we are in, or when the conversation has shifted between planning, implementation, and checking.
codex-update-spec
Update durable project specs/docs when implementation changes architecture, workflow, conventions, or recurring lessons.
codex-finish-work
Finish a Codex harness task after implementation, checking, spec updates, and rollout verification.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.