Loading...
Loading...
Found 8,852 Skills
Create a pull request following project conventions
Generate a personalized follow-up sequence for any creator chasing scenario — missing info, unsigned contract, late content, missing metrics, or incomplete whitelisting setup. This skill should be used when chasing a creator for a response, writing a follow-up message to an influencer, nudging a creator about a late deliverable, following up on an unsigned contract, requesting missing campaign metrics, chasing whitelisting or ad access setup, escalating a non-responsive creator, writing a reminder to a creator who ghosted, building a follow-up cadence for overdue items, drafting a polite but firm nudge to an influencer, or managing creator communication when deadlines slip. For writing initial outreach messages, see creator-outreach-sequence-generator. For classifying and triaging creator replies, see reply-triage-classifier. For negotiating rates after a creator responds, see creator-negotiation-assistant.
Use this skill whenever the user asks to analyze, understand, or survey an entire project, codebase, or any collection of files. Trigger phrases include "analyze a large file", "process multiple files", "comprehend this problem", "take a look at these files", "familiarize yourself with this project", or any similar request, however phrased. Also activate when the task involves processing context that exceeds what can be reasoned about in a single pass, when encountering any input larger than ~50KB that requires detailed analysis, or when the user mentions "context comprehension" or "recursive comprehension". This skill TAKES PRIORITY over your default explore subagents for any project-wide or codebase-wide analysis task.
Analyze existing PRD to identify and recommend the single highest-priority task to work on next
Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.
Track industry news, competitor announcements, analyst reports, and market developments. Use when a PM needs to stay current on market trends and competitive moves.
M3-compliant UI components (buttons, cards, forms, inputs). USE WHEN: creating components <300 lines, M3 migrations, Design System work. NOT FOR: complete screens, features with business logic (use flutter-developer). Always validate M3 components with MCP tools before creating custom. Examples: <example> Context: Need to migrate a button component to M3. user: "Migrate BukeerButton to Material Design 3" assistant: "I'll use flutter-ui-components to migrate BukeerButton to M3." <commentary>UI component migration is flutter-ui-components specialty.</commentary> </example> <example> Context: Create a new reusable form field. user: "Create a new date picker input component following M3" assistant: "I'll use flutter-ui-components to create the M3-compliant date picker." <commentary>Single UI components should be handled by flutter-ui-components.</commentary> </example>
Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.
Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.
Execute approved implementation plans from scratchpad. Use when implementing a previously planned feature.
Can be used when understanding, creating or modifying an RWX CI/CD config.
Build an iOS feature using ShipSwift component recipes. Use when the user says "build", "create", "add a feature", or describes an iOS feature they want to implement.