Explorar skills

SEO diagnostics combining Google Search Console + Ahrefs MCP data with codebase analysis. Detects crawl errors, indexing issues, missing meta tags, broken canonicals, sitemap problems, structured data gaps, and more. Use when the user wants an SEO audit, technical SEO review, indexing diagnostics, or search performance analysis.

Aprendizado de máquina em bioinformática, abordando engenharia de características para sequências, classificação de promotores, divisões de treino/teste, regressão logística, floresta aleatória e armadilhas bioespecíficas.

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Next.js SEO + GEO specialist. Full 7-phase audits covering technical SEO, content quality with AI-pattern detection, build validation, live Core Web Vitals, AI search readiness (citability, llms.txt, 14 AI crawlers), schema deprecation sweep, and composite scoring. Auto-builds per-project cached profile for faster repeat audits. Trigger keywords: SEO audit, technical SEO, structured data, meta tag

Trigger with "run self-audit", "test the analyzer", "regression test the plugin analyzer", "audit the agent-scaffolders", or "verify the analyzer works correctly". Runs the analyze-plugin skill against the agent-scaffolders itself and its test fixtures as a regression smoke test. Use this after making changes to the analyzer to verify nothing broke.

Tracks and reports token usage and dollar cost across every level of a vibe-* project — per task, per session, per feature, per phase, and total project spend. Auto-runs at the end of every session with estimates. When invoked manually with "cost:" accepts pasted Claude Code /cost output for precise numbers. Detects eight waste patterns: CP-01 context overhead, CP-02 repeated reads, CP-03 unstruct

Spec quality gate — audits planning documents before any code is written. Automatically triggered by vibe-brainstorm (after BRIEF.md), vibe-agent (after AGENT_ARCH.md), vibe-new-app and vibe-init (after vibe/ folder), and vibe-add-feature (after FEATURE_SPEC.md). Audits all documents that exist: BRIEF.md, AGENT_ARCH.md, SPEC.md, ARCHITECTURE.md, FEATURE_SPEC.md. P0 findings are critical gaps that

Generates complete documentation for vibe-* projects — inline code docs, README.md, CHANGELOG.md, API reference, and component library docs. Scans all source files and documents everything in one session. Triggers on "document:" prefix, "write docs for", "generate documentation", "add JSDoc", "add docstrings", "document this feature", "we need a README", "generate a changelog", "document the API",

Use this skill after Phase 1 Plan to create or intake requirements for a task. Produces requirements with stable IDs (REQ-001, REQ-002, ...), validates each requirement against the project's scope statement, and — critically — halts and asks for UX designs and brand guidelines whenever the work touches a frontend or user interface. Trigger whenever a plan has been approved and requirements are not

Diagnose the Qualflare setup for this project. Checks CLI installation, authentication, config validity, test-state.md freshness, live file-count drift, and framework tooling availability. Use when the user runs /qf-doctor, asks "is Qualflare set up correctly?", or encounters unexpected behavior from other qf commands.

Comprehensive software testing skill covering unit tests, integration tests, TDD/BDD, mocking strategies, and test automation across multiple languages. Use this skill when writing test cases, designing test strategies, implementing test automation, or need guidance on testing frameworks and best practices. Ideal for ensuring code quality through comprehensive testing approaches.

Explain a GitHub Pull Request (PR) or GitLab Merge Request (MR) to the user in plain, easy-to-understand language: WHAT was done, WHY/what for, and HOW — with the relevant code snippets embedded. Invoke this proactively and automatically right after creating or finishing a PR/MR (e.g. after running `gh pr create`, `glab mr create`, or pushing a branch and opening a PR/MR), even if the user did not