Loading...
Loading...
Found 10,619 Skills
Plan Southeast Asia market entry including mode selection, regulatory requirements, cultural research, and go-to-market timeline. Use this skill when the user is considering expansion to SEA, evaluating entry modes (marketplace vs direct vs distributor), or conducting market feasibility studies — even if they say 'should we enter Vietnam', 'how to sell in Indonesia', 'SEA expansion plan', or 'find a local distributor'.
Active HODLMM position manager that monitors bin drift, estimates accrued fees, and re-centers liquidity around the active bin when profitable.
Use this skill when the user wants a systematic literature review, survey, or synthesis across multiple academic papers on a topic. Also covers annotated bibliographies and cross-paper comparisons. Searches arXiv and outputs reports in APA, IEEE, or BibTeX format. Not for single-paper tasks — use academic-paper-review for reviewing one paper.
Use when the agent wants to define, list, inspect, or execute GUI macros via the OpenClaw Macro System CLI. Macros are parameterized, CLI-callable workflows — the agent invokes `macro run <name>` and the system handles backend routing (plugin, file transform, accessibility, compiled GUI replay).
All-in-one WeCom CLI Suite covering 6 core business domains: Contacts, Messages, Documents (including three types: Document, Smart Sheet, Smart Document (formerly Smart Homepage)), Schedules, Meetings, and Tasks. It supports searching contacts by name/alias, sending and receiving messages (text/image/file/voice/video), creating/reading/editing documents in Markdown format, managing Smart Sheet structures and records, creating Smart Documents and exporting their content as Markdown, creating/modifying/canceling schedules and checking availability, booking/managing meetings, and creating/tracking/assigning tasks. This skill should be triggered even if users do not explicitly mention 'WeCom' as long as scenarios involving messages, schedules, tasks, etc., are involved.
This skill should be used when the user asks to start a new research project, import an existing code-plus-Markdown repository into Obsidian, or bind the current repository to a compact research knowledge base for future syncing.
Build standalone custom pages using Amis low-code framework, independent of object records. Pages are defined as paired .page.yml (metadata) and .page.amis.json (UI schema) files in main/default/pages/. Covers page types (app, list, record), render_engine configuration, pageAssignments for desktop/mobile, and Amis schema with components like service, crud, chart, form, wizard, tabs. Includes examples for dashboards, reports, and custom forms.
Developer Experience (DX) review and advisory skill for CLI tools, shell scripts, developer tooling, and automation. Analyzes code against established CLI design guidelines (clig.dev, Heroku CLI Style Guide, 12 Factor CLI), composability principles, error handling best practices, and developer ergonomics. Triggers on: "dx review", "review dx", "check cli", "improve the cli", "dx audit", "review this tool", "is this usable", "check ergonomics", "dx feedback", "review the script", "improve usability", "check error handling", "review output", "dx writing", "improve help text", "review flags", "make this more intuitive", "dx best practices", "/dx".
Multi-framework intelligence brief. Takes any business situation, investment thesis, career decision, or strategic problem and runs it through 4-7 of 11 analytical frameworks (Feynman, Kahneman, Shannon, Tetlock, Duke, Munger, Thiel, Helmer, Christensen, Meadows, Taleb, Bezos). Each framework runs as a distinct sub-analysis producing concrete claims. Contradictions between analyses are surfaced explicitly. Synthesizes into a single brief: Core Argument, Key Insight, load-bearing conditions, failure modes with numeric probabilities, validation tests, recommended action with sizing, and the strongest dissent. Use when the user says "think through this", "analyze this for me", "help me decide", "think", "/think", or presents any complex decision, investment thesis, business question, or strategic problem that warrants structured multi-framework analysis.
Verint Open Platform help — enterprise CX automation with Da Vinci AI bots (Quality Bot 100% QA, Coaching Bot real-time guidance, Wrap Up Bot auto-summaries, CX/EX Scoring, TimeFlex agent scheduling, Exact Transcription 80+ languages), WFM forecasting/scheduling/adherence, knowledge automation, IVA virtual assistants, speech/text analytics, financial compliance, Verint Marketplace 350+ listings. Use when Verint reports loading slowly or showing inconsistent data, Quality Bot not scoring interactions correctly, Coaching Bot recommendations irrelevant, WFM forecasts off vs actual volume, Verint API integration or developer portal questions, comparing Verint vs NICE vs Genesys WEM capabilities, or connecting Verint to your CCaaS or CRM. Do NOT use for choosing between CCaaS platforms (use /sales-ccaas-selection) or for QA tool comparison across vendors (use /sales-coaching).
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini on Google Ads strategy, SEO best practices, or implementation questions). Use when the user says "gemini review", "ask gemini", "gemini challenge", "second opinion from gemini", "consult gemini", "stress test with gemini", "what would gemini say", "cross-model review", or "get another opinion". Voice aliases: "gem", "gemini check". Especially useful for Google Ads changes, SEO metadata updates, campaign structure decisions, keyword strategies, and bid/budget changes — Gemini has native Google ecosystem knowledge that complements Claude's analysis.
Ensures proper Python dependency management, avoiding global `pip install` and adhering to project-specific tooling. Use this skill if any of the following are true: 1. Attempting to run `pip install {package_name}`. 2. Python packages or dependencies need to be added or modified. 3. Initiating a new Python project. 4. Creating a new notebook, even if just using BigQuery cells. 5. Generating Python code that includes `import` statements for third-party libraries. 6. Before executing Python scripts via the terminal to ensure the correct virtual environment is active.