Loading...
Loading...
Found 7,976 Skills
Use when you have specifications or requirements for multi-step tasks before touching code
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - Guides the completion of development work by providing packaged options for merging, PR, or cleanup
Used when implementing any feature or bug fix before writing production code
This skill should be used when the user requests actions such as 'review code', 'do a code review', 'review my branch', 'review MR !1234', or 'review PR'
Use at the start of any conversation - Determine how to find and use skills, requiring the skill tool to be invoked before any response (including clarification questions)
Creates Jira epics for large features following Prowler's standard format. Trigger: When user asks to create an epic, large feature, or multi-task initiative.
Gmail via Composio API. Use when: (1) Sending emails with optional CC/BCC (2) Listing, searching, or reading inbox messages (3) Replying to messages (4) Creating drafts or managing labels Use Composio HTTP API only.
Управление ботами, входящие/исходящие вебхуки, разворачивание ссылок (unfurling). Используй когда нужно: настроить бота, обработать вебхук, обработать нажатие кнопки, периодический дайджест, алерты, polling событий, развернуть ссылку. НЕ используй для: отправки сообщений от бота (→ pachca-messages), интерактивных форм (→ pachca-forms).
State-machine driven iterative planning and execution for complex coding tasks. Cycle: Explore → Plan → Execute → Reflect → Re-plan. Filesystem as persistent memory. Use for multi-file tasks, migrations, refactoring, failed tasks, or anything non-trivial.
Template for creating new skills. Copy this file and customize for your use case.
Implement a project from its documentation and specification. Use when asked to "implement project", "continue implementation", "build from docs", "implement from spec", or when the user wants to progressively implement a documented project following a todo checklist. Reads docs/, creates implementation plans and todo lists, and implements incrementally with tests and commits.
Systematic documentation audit and maintenance. This skill should be used when documentation may be stale, missing, or misorganized — after feature work, refactors, dependency upgrades, or as a periodic health check. It prescribes folder structure for docs/ and manual/, dispatches haiku subagents for codebase/doc scanning, and routes doc creation to specialized agents (reference-builder, technical-writer, learning-guide) with docs-architect as quality gate.