Loading...
Loading...
Found 914 Skills
Analyzes files modified with git commands and creates appropriately granular commits in logical units. Only activates when the skill name (committer) is explicitly specified, such as "/committer", "use the committer skill", or "commit with committer". Does not activate for general requests like "commit" or "git commit".
Explain code in detail - what it does, how it works, and why. Use when you need to understand unfamiliar code or explain code to others.
Launch the app and hands-on verify that changes work by interacting with it. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does it actually work". Not for unit/integration tests.
General web search and content extraction skill. It supports multi-source parallel search (WebSearch, MCP search tools, ctx7, agent-browser), web page main content extraction (defuddle/WebFetch) and structured article analysis. This skill is used when users need to search for information, research topics, find materials, obtain web content, read articles, or analyze web pages. Trigger scenarios include: search, research, investigation, fetch, check for me, help me find, read this link, analyze this article. Even if the user doesn't explicitly say "search", this skill should be triggered as long as it involves information acquisition and web content processing.
Analyze an unfamiliar repository and explain what it does, how it runs, what architectural choices define it, where the important code lives, and what deserves deeper inspection next. Use this whenever a user has just cloned a repo, wants onboarding help, asks for a repo walkthrough, or needs a reliable first-pass architecture analysis.
When the user wants to find patterns in what content works and what doesn't. Also use when the user mentions 'what's working,' 'content patterns,' 'best topics,' 'best format,' 'best time to post,' 'analyze my content,' 'do more of,' 'do less of,' or 'what should I change.' For raw metrics, see performance-analyzer-sms. For audience-specific analysis, see audience-growth-tracker-sms. For actionable recommendations, see optimization-advisor-sms.
Generate read-only MongoDB queries (find) or aggregation pipelines using natural language, with collection schema context and sample documents. Use this skill whenever the user asks to write, create, or generate MongoDB queries, wants to filter/query/aggregate data in MongoDB, asks "how do I query...", needs help with query syntax, or discusses finding/filtering/grouping MongoDB documents. Also use for translating SQL-like requests to MongoDB syntax. Does NOT handle Atlas Search ($search operator), vector/semantic search ($vectorSearch operator), fuzzy matching, autocomplete indexes, or relevance scoring - use search-and-ai for those. Does NOT analyze or optimize existing queries - use mongodb-query-optimizer for that. Does NOT handle aggregation pipelines that involve write operations. Requires MongoDB MCP server.
Guides Qdrant scaling decisions. Use when someone asks 'how many nodes do I need', 'data doesn't fit on one node', 'need more throughput', 'cluster is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', or 'need to add capacity'.
Audits a FastAPI project against architecture rules. Use when asked to "review routes", "check architecture", "audit this project", "does this follow fastapi rules", or "review my code structure".
Produces a design-plan (living document like an exec-plan) that maps an app domain to feature groups using Apple Design DNA patterns. Each feature group becomes a milestone buildable in one ios-taste session. Use when the user describes an app idea, domain, or workflow and needs a structured plan before building. Triggers on "plan this app", "what features does X need", "design plan", "feature breakdown", "what screens do I need", or any pre-build planning question. Also trigger when the user provides workflow notes or user interview results. CRITICAL: This skill produces a DESIGN-PLAN document only. It does NOT generate SwiftUI code, layouts, or visual design.
Apply pragmatist philosophy (Peirce, James, Dewey) to frame knowledge as instrumental for action, evaluate ideas by their practical consequences, and conduct inquiry as problem-solving. Use this skill when the user needs to bridge theory and practice, evaluate competing theories by their usefulness, employ abductive reasoning to generate hypotheses, or when they ask 'which theory is more useful here', 'how do I move from abstract ideas to actionable knowledge', or 'what practical difference does this distinction make'.
Operate Notion Public API through UXC with a curated OpenAPI schema for search, block traversal, page reads, content writes, and data source/database inspection. Use when tasks need recursive reads or structured writes that Notion MCP does not expose directly.