.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/av/mi
home/skills/av/mi
av avatar

av/mi

22 skills · 3 total installs

View on GitHub
$npx skills add av/mi
SkillInstalls
exploreAnswer "how does X work", "where is X defined", or "trace through Y" questions about a codebase using parallel subagent searches with cited summaries.1new-skillWrite a new SKILL.md to teach yourself a procedure for a recurring task.1selfAnswer questions about how 'mi' works, write new tools, or modify the harness.1agent-integration-testingannealbugbashbughuntdebugFix bugs, crashes, errors, or failing tests. Use when "it's broken", "getting an error", "test is failing", or the cause isn't obvious.—delegateRun parallel or isolated subagents for independent subtasks (research, parallel analysis, one-shot transforms) to avoid bloating the main context.—disciplinefactsManage .facts files — atomic, validatable truth statements about a project. Install, check, list, add, edit, remove, and lint facts via the CLI.—facts-discoverScan the codebase and classify every fact by lifecycle stage — tag @draft, @spec, or @implemented based on what the code actually shows.—facts-implementOperate on @spec facts — implement them in code, then tag @implemented.—facts-refineOperate on @draft facts — collaboratively refine them into precise, actionable @spec facts.—ideateplanWrite a strategy doc before starting multi-step, multi-file, or unclear work.—refactorRestructure code without changing behavior. Triggers: "rename X to Y", "move X to Y", "extract X into Y", "clean up / split / deduplicate code" — one…—reviewReview code, a PR, branch, or staged diff. Use when asked to "review", "give feedback", "check this PR", or "what's wrong with this diff".—tasksTrack a numbered list of steps to completion. Use when the user gives explicit numbered steps ("1) do X 2) do Y"), says "I need to do N things", or when a…—tddAdd new behavior test-first (write failing test → make it pass → refactor).—timeboxed-iteratingverifyRun lint, typecheck, tests, or build — and fix any failures found.—