Loading...
Loading...
Found 10,387 Skills
Create product documentation with help pages, AI-generated screenshots, Remotion product videos with TTS narration and background music, and GitHub README visual documentation. Use when asked to create documentation, a help page, product tour video, generate screenshots, add user guides, or enrich a GitHub README.
Search and research enhancement skills. Use when performing web searches, looking up library documentation, or conducting research that requires multiple sources.
Use when research direction needs assessment, critical knowledge gaps must be identified, or priorities must be recommended based on impact, dependencies, and effort (especially at project milestones or when scope questions arise)
Take screenshots to see what's on screen. Triggers on 'screenshot', 'grab a screenshot', 'have a look', 'can you see', 'what does it look like', 'check the screen', 'did that work', 'verify it worked', 'what happened'. AFTER uncertain CLI operations (backgrounded processes, nohup, visual changes), consider capturing to verify state. Captures windows or full screen to files. (user)
Stops execution and fixes root cause when commands, builds, scripts, or tools fail unexpectedly. Triggers on workaround language: 'directly', 'instead', 'alternatively', 'skip', 'fall back', 'work around', 'isn't working', 'broken', 'manually'. Activates on any unexpected non-zero exit code or process failure.
Apply systematic code refactoring with small steps, clear boundaries, and proven techniques. Use when improving existing code, reducing technical debt, cleaning up legacy code, or when user mentions refactoring, code cleanup, or code improvement.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
General RPI (Research, Plan, Implement, Iterate) execution skill. It is used for engineering tasks where users require "research first, then plan, then implement, and finally iterate", or when tasks are highly complex, high-risk, or have unclear impact. This skill does not rely on specific command-line tools or platforms, and is applicable to any AI Agent that supports skill mechanisms.
This skill is used when users explicitly request "review NSFC proposals", "simulate expert review", or "evaluate NSFC applications". It simulates the perspective of domain experts to conduct multi-dimensional reviews of NSFC proposals, outputting graded issues and actionable modification suggestions. ⚠️ Not applicable: when users only want to write/modify a specific section of a proposal (use the nsfc-*-writer series skills instead), only want to understand review criteria (answer directly), or have no clear "review/evaluate" intent.
Automates the full code release pipeline — branch, commit, push, PR, wait for CI, merge, version bump, release, cleanup.
This skill should be used when users need to manage Linear issues, tasks, or projects via command line. Triggers on requests mentioning Linear issues, issue tracking, creating issues, updating issue status, managing Linear projects, or Linear CLI operations.
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>