Total 50,505 skills, Tools & Utilities has 8214 skills
Showing 12 of 8214 skills
For answering, using, and debugging @wot-ui/cli. Keywords: wot, @wot-ui/cli, CLI, MCP, doctor, usage, lint, list, info, doc, demo, token, changelog, extract, wot mcp. Applicable for command queries, parameter explanations, MCP integration, local debugging, data extraction, and open-wot repository maintenance.
Find Kalshi prediction markets on DFlow that match a criterion — arbitrage (YES+NO<$1), cheap long-shots, near-certain short-dated plays, biggest movers, widest spreads, highest volume, closing soonest, and series/event-level scans. Use when the user asks "where's the free money?", "any mispriced markets?", "cheap YES with volume", "what moved today?", "markets closing soon", "cheapest YES in this event", "top markets by volume", or "alert me when X happens" (streaming). Do NOT use to place orders (use `dflow-kalshi-trading`), to view a user's own positions (use `dflow-kalshi-portfolio`), or for general live-data plumbing unrelated to a scan (use `dflow-kalshi-market-data`).
Operate DefiLlama public price APIs through UXC with a curated OpenAPI schema and read-first guardrails.
Operate DingTalk messaging APIs through UXC with a curated OpenAPI schema, app-token bearer auth, and robot/service-group guardrails.
Query up-to-date library documentation and code examples using Context7 MCP. Use when you need current, version-specific documentation for npm packages, Python libraries, or other programming languages.
Peter Thiel's Monopoly Creation framework applied to a business idea. Spawns a team of specialist agents — Monopoly Anatomist, Secret Hunter, Market Framer, Last Mover Analyst, Girardian — who each apply a distinct lens from Thiel's framework to evaluate whether a venture has genuine monopoly potential. The lead synthesizes into a verdict: does this company have a secret, a 10x advantage, a tiny domination-ready market, and a path to becoming the last mover in its category? Use when the user says "thiel this", "monopoly test", "zero to one analysis", "does this have monopoly potential", or proposes a venture and wants Thiel-style evaluation. Works standalone or after /office-hours and /munger.
Wave platform help — AI note-taker with mobile-first recording (iOS, Android, Mac, Windows, Apple Watch, Chrome, web), 76-language transcription, Voice ID speaker labeling, REST API with semantic search and webhooks, MCP server. Use when recording meetings on your phone and transcripts aren't accurate, setting up Wave API to pull session transcripts into your CRM, configuring Wave webhooks for real-time session notifications, phone call recording stops when another call comes in, Wave meeting bot not joining Zoom or Google Meet, comparing Wave pricing vs Fathom or Otter for a small team, searching across all your Wave recordings with the API, or exporting Wave summaries to Notion or Google Docs. Do NOT use for choosing between multiple note-takers (use /sales-note-taker) or reviewing a call for coaching (use /sales-call-review).
Flespi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Flespi data.
Final gate of the Flows app certification flow for external submission. Verifies that flows-app-brief, flows-code-review, and flows-design-review have all been run and are in a passing state (App-Brief.md complete, 0 Must Fix in latest code review, design average ≥ 3.8), then runs `npx @cognite/cli apps submit` to zip the repo and pre-populate the submission form. Use when the user asks to submit a Flows app for certification, run flows-external-app-submit, or finalize an app for external review.
Fetch unresolved review comments from a GitHub PR or mark comments as resolved. Use this when managing PR review feedback, checking pending comments, or marking review threads as resolved. Supports GitHub URLs or explicit owner/repo/PR-number from anywhere, or PR number auto-detection from within a git repository.
Manifestly Checklists integration. Manage Checklists, Projects, Users, Teams. Use when the user wants to interact with Manifestly Checklists data.
Use whenever researching a technical question — a library, tool, API, error, version, or "what's the best way to X" — or whenever you're about to answer from memory. Forces multiple real searches over primary sources (official docs, source code, high-vote Stack Overflow, maintainer blogs) instead of one search plus training-data filler, and rejects SEO content-farm slop. Trigger on "research X", "look into", "what's the best library for", "how does X work", "is this still true", "find out".