Tools & Utilities
Essential command-line tools and system utilities.
feature-docs
Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".
web-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
doc-validator
Validate documentation files for completeness, accuracy, and consistency with the codebase. Use when user mentions "check documentation", "validate docs", "is the README up to date?", requests documentation review, says "docs are wrong" or "fix the docs", or is working on documentation improvements. Covers README files, API docs, CHANGELOG, and any markdown documentation.
linking-notes
Discover and add wiki-links between notes. Use when asked to "find connections", "link this note", "what should I link to", or "connect my notes".
life-os-knowledge
Personal knowledge base for Shapira family daily life. Use when querying or storing information about hotels, swim meet venues, travel logistics, restaurants, service providers, or any location-based preferences. Triggers on phrases like "remember this hotel", "where did we stay", "next time in [city]", "log this location", or references to past stays/visits.
research-documentation
Research topics and document findings in Notion with organized structure and sources
adding-notes
Add new notes to the Second Brain knowledge base. Use when the user provides a resource (URL, book, podcast, article, GitHub repo, Reddit thread) and asks to "add a note", "create a note", "save this", "add to my notes", "take notes on", or "capture this".
obsidian-plan-wiki
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", or "workstream". Specs are the source of truth - point an agent at a spec to update code.
code-review
Reviews code for best practices, bugs, security issues, and provides improvement suggestions
frontend-debug
Autonomously debug frontend issues through empirical browser observation using Chrome DevTools MCP. This skill should be used when debugging UI/UX issues, visual bugs, interaction failures, console errors, or network problems in web applications. Provides systematic 6-phase debugging workflow with GitHub integration, automated verification, and knowledge retention.
moai-docs-linting
Enhanced docs linting with AI-powered features. Enhanced with Context7 MCP for up-to-date documentation.
documentation-style
Apply consistent documentation standards and style guidelines when creating, reviewing, or improving project documentation (README, architecture docs, guides, references). This skill should be used when writing new documentation, reviewing existing docs for style consistency, or when users request documentation improvements or style guide compliance checks.
move-content
Move or rename files in knowledge base with directory governance. Use when user wants to move, relocate, or rename content. Reads RULE.md of both source and target directories.
debugging-methodology
Systematic debugging approach with tool recommendations for memory, performance, and system-level issues.
api-docs-generator
Automatically generates and updates API documentation from code changes with multiple format support
openapi-overlay-generator
Generate OpenAPI overlay files for Seqera Platform API documentation. Use when working with API documentation updates, analyzing comparison overlays from Speakeasy, creating operations/parameters/schemas overlay files, or updating API documentation for new Platform versions. Triggers include requests to generate overlays, document new API endpoints, analyze API changes, or work with Seqera Platform OpenAPI specifications.
test-endpoints
This skill automates API endpoint testing and documentation. It runs curl requests against specified endpoints, captures responses, validates against OpenAPI spec, and generates markdown documentation. Use after implementing new endpoints or when verifying API behavior.
reverse-engineer
Deep codebase analysis to generate 9 comprehensive documentation files. Adapts based on path choice - Greenfield extracts business logic only (tech-agnostic), Brownfield extracts business logic + technical implementation (tech-prescriptive). This is Step 2 of 6 in the reverse engineering process.
configuring-acquisition-system
Guides users through configuring a data acquisition system on the local machine. Covers working directory setup, acquisition system selection and parameter configuration, and Google credentials setup. Use when setting up a new acquisition PC, changing acquisition system type, or when the user asks about system configuration.
code-refactoring
Proactively monitors file sizes and suggests refactoring BEFORE editing. Auto-invoked when files exceed size thresholds (150/200/300 lines) or complexity patterns detected. Works across JavaScript/TypeScript, Python, and general codebases. Prevents accidental complexity growth.
ruby-refactoring-expert
Automatically invoked when analyzing code quality, refactoring, or maintainability. Triggers on mentions of "code smell", "refactor", "code quality", "technical debt", "complexity", "maintainability", "clean code", "SOLID", "DRY", "improve code", "simplify", "extract method", "extract class", "long method", "large class", "duplication". Provides Ruby refactoring patterns and code smell identification based on Ruby Science methodology for recently written Ruby/Rails code.
