Loading...
Loading...
Found 6,605 Skills
Use when adding or following the red/yellow/green final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions.
Build applications and agents with Exa's API: search, contents extraction, answer, context, Agent API, monitors, websets, OpenAI-compatible endpoints, and exa-py/exa-js SDKs. Use when choosing Exa endpoints, writing Exa API calls, integrating semantic web search or research into products, or debugging Exa request shapes.
Use when writing a complete SEO article. Includes the full anti-AI-slop ruleset (banned vocabulary, banned phrases, banned structural patterns) and voice rules. The agent researches the SERP itself if needed — no keyword data exports required.
Build standalone interactive HTML artifacts as the medium for agent↔designer conversation — review docs with approve/deny/discuss, N-way prototype variants, before/after motion comparisons, visual explorers for APIs/content, and inline-editable copy ecosystems. Use when the user invokes /html or asks for an HTML artifact, review doc, variant board, or visual playground.
Use when the user invokes $nerd-memory (Codex) or /nerd-memory (Claude/Cursor), or when Nerd Smart auto-enables it to learn, recall, inspect, deny, refine, correct, split, or forget recurring goal, task, action, result, boundary, verification, or agent-skill-tool-MCP routing patterns across tasks.
Use when explicitly invoked or when a concrete latency constraint requires minimizing wall-clock agent time without reducing accuracy.
Used for installing, updating, reinstalling or repairing the official qiqi, OAuth authorization, or separately accessing Qiqi Skills for the current Agent. Verify CLI, authorization, continuous invocation and Skills results respectively; test environment, joint debugging or acceptance are handled by internal test runtime adaptation.
Grades a repo's agent skills by scoring agent conversations against efficiency and code-quality rubrics, then drafts concrete skill edits and a shareable report. Use when the user wants their agent setup graded from real conversation history, or asks which of their installed skills are actually working.
Multi-agent shared blackboard: The current directory is .yomi/boards/<feature>.md, one board per feature, allowing parallel agents/subagents under the same feature to see each other's tasks, progress, and findings. Use when multi-agent collaboration requires peer visibility, sharing progress/findings, wanting to know what peers are doing before starting work, or when terms like "blackboard / board / peer progress" are mentioned. Task assignment/sign-off/state machine/acceptance are handled via task-tickets, not blackboard.
One-time bootstrap of a persistent memory + self-evolution system for an agent workspace. Use when setting up memory for a new agent or workspace, or configuring dream/janitor crons.
Comprehensive review of local uncommitted changes using specialized agents with code improvement suggestions
Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.