Discover databases project management skills, compare source repositories and read the instructions for each workflow.
GitHub Issue-based task execution workflow with project management. Use when user says "work on issue", "implement issue", "start issue", or "/issue-driven-dev {issue-url}". Includes project status management,...
Quick GitHub Issue creation workflow. Use when user says "create issue", "register issue", "bug report", "TODO registration", or "/issue-create {repo}". Requires repository as argument (e.g., owner/repo).
Storybook expert for Angular 21+ component development, visual testing, and design system documentation
GitHub Issues expert for gh issue create, gh issue list, labels, milestones, epics, features, tasks, bugs, priorities, mvp-blocker, critical, high-priority, issue tracking, project management, issue queries, wo...
Breaks down requirements into iterations and tasks
Create user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features.
Presentation creation, editing, and analysis. When Copilot needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Add...
Manages project todos via REST API. Use when the user asks to create, view, update, or delete todos, list tasks by project, check task status, or filter by due date. Requires the Noetect app to be running.
Manages daily notes with M-D-YYYY format (e.g., 1-1-2026.md). Use when the user asks to view recent notes, create daily notes, read today's notes, summarize the week, or references @notes/ or dates. Can fetch l...
Daily check-in to decide what to focus on. Use when user says "today", "what should I do", "what's on my plate", "morning review", or at the start of a conversation.
Add well-formed, actionable tasks to Trello. Use when user says "add task", "remind me to", "I need to", or "put on the board".
Surface forgotten, stale, or neglected tasks. Use when user says "review", "what have I forgotten", "weekly review", "clean up the board", or when the board seems cluttered.
Monitor Bob The Skull operation and debug issues. Use when checking system health, diagnosing problems, analyzing logs, monitoring state transitions, or troubleshooting component failures. Covers web monitor, l...
Conducts structured requirements interviews for spec documents. Use when gathering requirements, writing specs, planning features, creating PRDs, or when user mentions "interview", "requirements", "spec", "PRD"...
This skill should be used when the user asks to "handle bot comments", "fix PR review feedback", "address CodeRabbit/Greptile/Copilot issues", "respond to review bot suggestions", "process automated review comm...
Fix implementation plans through iterative gap analysis. Use when user wants to verify a plan, fix a plan, check for gaps, validate an implementation plan, or ensure a plan is complete.
Guidelines for creating task-oriented how-to guide documentation. Use when writing content that helps users accomplish specific goals.
Generate quarterly sales reports with executive summary, regional breakdown, and trend analysis. Use for formal business reporting.
Provides detailed guidance on how to implement a single plan step while adhering to architecture and quality standards.
Breaks high-level goals into an incremental, prioritised plan using the plan template.
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented...
Spec-Driven Development workflow using VibesPro conventions
Extracts structured requirements, acceptance criteria and risks from user requests and existing product documentation.
Validates complete requirements traceability across EARS requirements → design → tasks → code → tests. Trigger terms: traceability, requirements coverage, coverage matrix, traceability matrix, requirement mapp...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.