Explorar skills
69.576 skills encontradas
browseai-automation
Automate Browseai tasks via Rube MCP (Composio). Always search tools first for current schemas.
create-behat-context
Create the PHP feature context class that implements step definitions for a domain, and register it in behat.yml. Covers the PHP implementation side of Behat tests. Trigger: "create behat context for {Domain}".
algodocs-automation
Automate Algodocs tasks via Rube MCP (Composio). Always search tools first for current schemas.
frontend-code-review
Aciona quando o usuário solicita uma revisão de arquivos de frontend (por exemplo, .tsx, .ts, .js). Suporta revisões de mudanças pendentes e revisões de arquivos focadas, aplicando as regras da lista de verificação.
adyntel-automation
Automate Adyntel tasks via Rube MCP (Composio). Always search tools first for current schemas.
baserow-automation
Automate Baserow tasks via Rube MCP (Composio). Always search tools first for current schemas.
component-patterns
React component composition patterns including compound components, render props, HOCs, and controlled vs uncontrolled components. Use when the user is building React components, asking about component architecture, refactoring components, or designing reusable UI APIs. Trigger on mentions of compound components, render props, higher-order components, forwardRef, composition, or component design p
percolate
Realiza uma simulação e depois confirma a publicação dos arquivos do plugin coordenador para um repositório de destino nomeado. Envolve o publish.sh com um gate e testes de fumaça de CI.
skills
AI Skills for Reaviz Projects
piloterr-automation
Automate Piloterr tasks via Rube MCP (Composio). Always search tools first for current schemas.
using-superpowers
Meta-skill enforcing skill discovery and invocation discipline through mandatory workflows. Use when starting any conversation to check for relevant skills before any response, ensuring skill-first workflow before proceeding.
doccraft-story
Author or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under {{DOCS_DIR}}/stories/ with a YAML frontmatter contract (id, status, impact, urgency, depends_on, tags, openspec). Use this whenever the user is creating a story, reprioritising work, writing acceptance criteria, linking a story to OpenSpec or an ADR, or editing anything under {{DOCS_DIR}}/stori