Loading...
Loading...
Found 793 Skills
Douyin Rising Hot Topic Idea Assistant. Activate this skill when users ask questions like "what content will get traffic", "which topics are trending recently", "what to post next week", or "industry hot trends". Supports optional parameters: sorting method (popularity/change), hot topic category, search keywords. Even if users don't explicitly mention "Douyin" or "hot topics", this skill should be activated as long as the query involves content ideation, traffic prediction, or topic trends.
Xiaohongshu Comment Public Opinion Analysis and Operation Suggestions. Activate this skill when users provide links to Xiaohongshu notes/videos and need to analyze comment public opinion, user feedback, emotional tendencies, or operation suggestions. This skill should also be activated even if users only say "Help me check the comments on this Xiaohongshu note" or "Analyze how this post is performing".
Uncontrollable software development costs? We provide software cost estimation dashboard functionality.
Bilibili Comment Public Opinion Analysis and Creator Operation Suggestions. Activate this skill when the user provides a Bilibili video/live stream link and needs to analyze comment public opinion, bullet screen sentiment, user feedback, or operation suggestions for creators. This skill should also be activated even if the user only says "Help me check the comments of this Bilibili video" or "Analyze the bullet screens of this video."
Test the full Credyt billing cycle end-to-end for a specific product. Creates a test customer, funds their wallet, sends a usage event, and verifies fees were charged correctly. Use this to re-verify a product after making changes in the dashboard, to test a specific product independently, or to troubleshoot billing issues. Note that /credyt:billing-setup runs verification automatically — use this skill when you want to verify without re-running full setup.
Discover your billing model and configure products, assets, and pricing in Credyt via MCP. Run this after /credyt:init. Can be run multiple times to add products or adjust pricing. Automatically verifies the full billing cycle after configuration. Use when the user wants to set up billing, create products, configure pricing, add new billable activities, or change how they charge.
Guide users through defining their pricing strategy for an AI product or SaaS. Covers billing model selection (usage-based, subscription, hybrid), subscription tier pricing, credit/overage costs, real-time vs invoice billing trade-offs, existing PSP integration, custom currency vs fiat, and pricing dimensions. Ends with a personalised pricing strategy summary, MRR projection, visual output (HTML or PDF), and tool recommendations. Use when a user wants to define their pricing, figure out how to charge for their AI product, decide between billing models, understand the real-time vs invoice billing trade-off, or evaluate what tools to use for monetisation.
This skill should be used when the user asks to "edit a video to music", "create a beat-synced edit", "make a montage", "sync cuts to beats", "cut a video to the beat", "make a music video edit", "edit clips to a song", "build FFmpeg filters for video editing", or mentions combining video clips with audio tracks using timed cuts. Provides knowledge of the EditPlan format, FFmpeg filter_complex construction, and beat-sync editing workflows.
Select a consistent visual design system for PPT slides using radius/spacing style recipes. Use when users ask for overall style direction or component styling consistency. Includes Sharp/Soft/Rounded/Pill recipes, component mappings, typography/spacing rules, and mixing guidance. Triggers: style, style, radius, spacing, corner radius, spacing, PPT style, visual style, design style, component style.
Edit existing PowerPoint files or templates with XML-safe workflows. Use for template-based deck updates: analyze layouts, map content to slides, duplicate/reorder/delete slides safely, edit slide XML in parallel, clean orphaned assets, and repack validated PPTX output.
Reads documented bugs from bugs.md, analyzes root causes, implements fixes with regression tests, and validates the full test suite. Prioritizes fixes by severity (high to low). Updates bugs.md with correction status and generates a final bugfix report. Use when the user asks to fix bugs, resolve issues, or run the bugfix workflow for a feature. Do not use for new feature implementation, code review, or QA testing.
Comprehensive guide for electron-builder (v26.x) packaging, code signing, auto-updates, and release workflows. Use when: (1) configuring electron-builder builds (electron-builder.yml or config.js/ts), (2) setting up macOS/Windows code signing or notarization, (3) implementing auto-updates with electron-updater, (4) publishing to GitHub Releases, S3, or generic servers, (5) configuring platform targets (NSIS, DMG, AppImage, Snap, PKG, MSI), (6) working with build hooks (beforePack, afterSign, afterAllArtifactBuild), or (7) using the programmatic API. Triggers on: electron-builder, electron-updater, code signing, notarize, NSIS, DMG, AppImage, auto-update, publish releases, build hooks, electron packaging, electron distribution.