yourmechanic
Book mobile mechanics who come to you for car repairs and maintenance.
Find the perfect capability for your agent.
Book mobile mechanics who come to you for car repairs and maintenance.
Collects complete technical specifications from manufacturer sites, Amazon, and review sites with schema validation. Use when user asks to 'get specs', 'collect specifications', 'find technical details', 'product specifications', or when orchestrator needs detailed product specs. Validates data completeness against category requirements.
Use when LaTeX documents fail to compile, have undefined references, duplicate labels, or citation errors
Guide for the Spine TechBook domain - literate programming for progressive-build technical books. Covers concepts, snippets, checkpoints, tangle/weave pipeline, and validation.
Comprehensive reference documentation for all data structures in the VRP toolkit project. Use when needing to understand data structure definitions, attributes, formats, or representations to avoid repeatedly reading code. Covers Problem layer (Instance, Solution, Node), Algorithm layer (Solver, Operators, ALNS), Data layer (OSMnx, distance matrices), and runtime formats (routes as lists, time windows as tuples).
Create and maintain MADR-format Architectural Decision Records in Markdown under `docs/decisions`. Use when the user wants to document important decisions.
Creates problem-oriented migration guides following Diátaxis How-To pattern. Maps old APIs to new APIs with before/after examples, documents breaking changes, provides troubleshooting. Zero tolerance for fabricated APIs or unverified performance claims. Use when new system replaces old, breaking API changes occur, major version upgrades needed, service decomposition happens, deprecation notices required, or architectural changes documented.
Comprehensive reference for LLM agents to navigate and work with Odoo documentation. Use when working with Odoo-related documentation tasks like finding installation guides, locating application documentation, searching developer tutorials/reference materials, understanding documentation structure, and assisting with queries about Odoo features, development, and maintenance. This skill provides organized domain-based references and search strategies for efficiently locating information across the entire Odoo documentation tree.
Maintains detailed log of errors, bugs, and debugging sessions encountered during development. Use when encountering errors, debugging issues, or solving technical problems. Creates structured ERROR_LOG.md with error details, root causes, solutions, and prevention strategies. Complements project-logger (strategic decisions) with tactical debugging knowledge.
Follow and resolve Obsidian internal links ([[link]] syntax) to navigate interconnected notes within an Obsidian vault. Use when exploring note relationships, following references between documents, building knowledge graphs, or understanding how notes connect together. Supports recursive link traversal with configurable depth.
Validate wiki integrity using Kimi. Checks broken wikilinks, missing frontmatter, orphan pages, and structural issues in the Obsidian vault.
Validate wiki-links in an Obsidian vault. Finds broken links that don't resolve to real files, orphaned notes with no incoming links, and link health statistics. Use for vault maintenance and cleanup. Works with or without Obsidian MCP.
Real-time web search using Exa AI. Use when you need current information, fact-checking, researching unfamiliar topics, or finding documentation. Triggers on requests mentioning search, lookup, find online, current information, or research.
Expert incident responder specializing in security and operational incident management. Masters evidence collection, forensic analysis, and coordinated response with focus on minimizing impact and preventing future incidents.
Knowledge base for session continuity. Maintains project documentation with fixed directory structure (.pmc/docs/) and formats for PRDs, SOPs, tickets (T0000N), patterns, decisions, code maps, research, and status. CRITICAL BEHAVIORS: 1. LOOKUP FIRST - Before any task, check kb for existing docs (SOPs, patterns, code maps, status) that may guide the work. Don't reinvent what's documented. 2. LEARN = DOCUMENT - When user says "learn X", record it in appropriate doc: - Procedure? → 2-sop/ - Problem/solution? → 6-patterns/ (with Status: open|resolved) - Code flow? → 7-code-maps/ - Research/notes? → 8-research/ - Design decision? → 5-decisions/D###-{name}.md - User clarification? → capture in ticket 5-final.md 3. CAPTURE INTENT - When user clarifies requirements or expresses preferences, record in ticket's 5-final.md (Revealed Intent section). 4. INBOX - Direct user messages → 0-inbox/ for later processing by /pmc:dev or /pmc:plan. Use when: setting up docs structure, creating/managing t
Research product compositions using AI and web sources. Use when needing to find what products, substances, or objects are made of - including ingredients, materials, chemicals, and elements. Essential for building composition data.
Enhanced docs linting with AI-powered features. Enhanced with Context7 MCP for up-to-date documentation.
Create and validate skills. USE WHEN create skill, new skill, skill structure, canonicalize. SkillSearch('createskill') for docs.
Auditing and maintaining AGENTS.md documentation. Triggers include "audit AGENTS.md", "check agent docs", "verify documentation accuracy", "maintain agent instructions", or "check for drift".