Loading...
Loading...
Found 2,057 Skills
Documentation of the project's standardized approach to using `@vueuse/integrations/useAxios`. Focuses on minimizing boilerplate, leveraging global error handling, utilizing built-in state management, and enforcing consistent naming conventions.
Expert guidance for Google Veo 3.1 video generation. Use when the user wants to (1) create text-to-video or image-to-video prompts, (2) optimize for cinematic quality and native audio syncing, (3) maintain character consistency via reference images, (4) structure multi-shot sequences with timestamp prompting, (5) use First/Last Frame interpolation, (6) select between standard and fast generation modes, or (7) troubleshoot physics, motion, or audio issues in generated video.
Use when evaluating individual Xiaohongshu post performance, identifying what makes content succeed or fail, extracting viral content patterns, recognizing underperforming content that needs optimization, or comparing performance across different content types and formats
Provides strategic insights on AI-driven software democratization and agent-based development trends from Replit's perspective. Use when discussing the future of software engineering, AI agent infrastructure requirements, democratization of coding, or when analyzing how AI will transform software creation from expert-only to universal access. Triggers include questions about software engineering automation trends, agent sandbox environments, SWE-bench benchmarks, or strategic implications of AI coding assistants for startups and enterprises.
PowerPoint翻訳機能の実装・デバッグ・改善を支援する。PPTXファイル処理、python-pptxライブラリ、 Claude API連携、テキスト抽出・挿入、翻訳ワークフロー全体をカバー。翻訳が動かない、 PPTXの処理でエラーが出る、テキスト抽出がおかしい、スライドのレイアウトが崩れるなど、 PPTX翻訳パイプラインに関わる問題が発生したら必ずこのスキルを使うこと。 Cloud Runバックエンドとの連携問題も対象。
Tech Stock Earnings Deep Dive Analysis and Multi-Perspective Investment Memo System (v3.0). Covers 16 major analysis modules (A-P), 6 investment philosophy perspectives, institutional-grade evidence standards, anti-bias framework, and actionable decision system. When users mention topics such as tech company earnings analysis, quarterly/annual report interpretation, earnings call, revenue growth analysis, margin changes, guidance, valuation models, DCF, reverse DCF, EV/EBITDA, PEG, Rule of 40, management analysis, competitive landscape, position sizing, whether to buy/sell/add to a tech stock position, how to interpret a company's latest earnings, doing a deep dive, multi-angle valuation, how investment masters view a company, variant view, key forces, kill conditions, ownership structure, executive team, partner ecosystem, macro policy impact, etc., this skill should be used. Even if the user simply asks "help me look at NVDA's latest earnings" or "how did META do this quarter" or "should I keep holding MSFT," this skill should be triggered to provide comprehensive earnings analysis and a multi-perspective investment memo. This skill complements the us-value-investing skill — us-value-investing focuses on long-term value four-dimensional scoring, while this skill focuses on in-depth dissection of the latest earnings, comprehensive judgment across multiple investment philosophies, and actionable position decisions.
Use when users provide vague, underspecified, or unclear requests where they need help defining WHAT they actually want - across ANY domain (writing, analysis, code, documentation, proposals, reports, presentations, creative work). Trigger aggressively when users express VAGUE GOALS ("make this better", "improve our X", "figure out what to include", "I don't know where to start", "kinda lost on what to do", "not sure what this means"), UNDEFINED SUCCESS ("should look professional", "explain this clearly", "make it convincing", "whatever works best", missing constraints/audience/format), COMMUNICATION UNCLEAR ("how do I explain/communicate this", "my team gets confused when I describe it", "help me figure out what to ask about X"), AMBIGUOUS REQUIREMENTS ("analyze the data" without saying what to look for, "improve documentation" without saying how, "make it more robust" without defining robustness, any request with multiple valid interpretations), or META-PROMPTING ("optimize this prompt", "improve my prompt", "make this clearer", "review my instructions", learning about prompt frameworks like CO-STAR/RISEN/RODES, understanding what makes prompts effective). Trigger for non-technical users and ANY situation where the request needs refinement, structure, or clarification before execution can begin. When in doubt about whether a request is clear enough - trigger.
Gate Exchange same-UID internal transfer skill. Use when user says 'transfer', 'move funds', 'spot to futures', 'USDT-margined', 'perpetual', 'margin'. Phase 1: internal transfer only (no main-sub). Execution requires explicit user confirmation and source balance pre-check.
Write, review, and adapt SQL for PolarDB-X 2.0 Distributed Edition (Enterprise Edition) in AUTO mode, properly handle differences between PolarDB-X and MySQL (such as partitioned tables, Global Secondary Index (GSI), Columnar Index (CCI), Sequence, distributed transactions, table groups, TTL tables, etc.). Suitable for scenarios where you need to generate SQL to run on PolarDB-X, migrate MySQL SQL to PolarDB-X, or debug PolarDB-X SQL compatibility issues.
6-phase PPTX presentation generation with visual QA: Gather, Design, Generate, Convert, QA, Output. Use when user needs a PowerPoint deck, slide presentation, pitch deck, or conference talk slides. Triggers: "create a presentation", "make slides", "pitch deck", "powerpoint", "pptx", "slide deck", "generate presentation". Do NOT use for Google Slides, Keynote, or PDF-only documents.
Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project
Query the official CrewAI documentation for answers. Use when the user has a CrewAI question that isn't fully covered by the getting-started, design-agent, design-task skills — e.g., specific API details, configuration options, advanced features, troubleshooting errors, enterprise features, tool references, or anything where the latest docs are the best source of truth.