Loading...
Loading...
Found 1,681 Skills
Decision Coaching for Vue Component/Composable Refactoring — Users paste a piece of code or point to an SFC, and the skill first performs a diagnosis ("Fat Trunk" / "UI & IO Entanglement" / "Reactivity & Business Logic Entanglement"), then selects one from three recipes, and provides a specific sequence of extraction steps (which variable to move first, what errors the compiler will throw, how to fix them one by one, when rollback is possible). The entire process ensures behavioral equivalence through compiler green lights + step-by-step rollback, without relying on test safeguards. Trigger scenarios: Users say "This Vue component is too fat / I want to extract the logic / Split this SFC / This composable is too messy / Extract a composable / Split into humble / Pure functionalize", or point to an obviously overlong .vue / composable file and request "Refactor / Optimize / Split". Only handles Vue (Vue 2 Options, Vue 2/3 `<script setup>`, composable, pinia store). Does not handle: Adding new features (follow feature process), fixing bugs (follow issue process), cross-module architecture restructuring, backend code.
Unbounce platform help — landing page builder, Smart Traffic AI optimization, Smart Copy AI copywriting, A/B testing, popups, sticky bars, Dynamic Text Replacement, AMP pages, REST API. Use when landing page built in Unbounce isn't converting, Smart Traffic not improving conversions, A/B test setup in Unbounce, popup or sticky bar not triggering, Unbounce page loads too slowly, choosing between Build vs Experiment vs Optimize plan, connecting Unbounce to CRM or email tool, or Dynamic Text Replacement not working. Do NOT use for general funnel strategy (use /sales-funnel) or general CRO methodology (use /sales-vwo).
Ecosystem self-evolution orchestrator. Detects project lifecycle phases, evaluates agent relevance, synthesizes cross-agent knowledge, and proposes evolution actions (health checks, fitness scoring, evolution proposals).
Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
Error-to-fix playbook for every known failure mode on the OpenFinance backend — Polymarket, Relay, Hyperliquid, Privy delegation, and Solana RPC issues. Use this the moment a call fails, returns an unexpected status, or behaves inconsistently with on-chain state. Triggers on ANY of these error signatures verbatim or in paraphrase. Polymarket: "allowance: 0 but on-chain shows max", "CLOB reports allowance 0", "approvals confirmed but order rejected", "404 upstream" on market orders, "tick size" rejection, "order size below minimum", USDC.e vs pUSD vs native USDC confusion, V1 vs V2 exchange confusion. Relay: "InstructionFallbackNotFound", "Custom:101", "Custom:6000", "AnchorError", "Blockhash not found", "TransactionExpired", "No valid authorization signatures were provided", "Solana wallet is not delegated to the app", 412 delegation errors, quote succeeded but execute failed, stuck funds on Solana, stuck funds cross-chain, topupGas forced off. Hyperliquid: "Insufficient perp account value", "price out of bounds", WebSocket stale data, spot vs perp balance confusion. General: any "why is X failing", "why does on-chain and API state disagree", "what does this error mean". Read this BEFORE assuming a bug in the MCP or backend — most of these errors are already catalogued with known fixes.
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
Use when auditing a wiki for health issues — contradictions between pages, orphan pages, broken cross-references, stale claims, missing pages, or coverage gaps. Run after every 5-10 ingests.
DTC Full-Funnel Diagnosis & Attribution Engine —— Full-funnel attribution analysis, key indicator anomaly detection, cross-business-line problem localization, root cause analysis, priority ranking. Use when user mentions: 诊断, diagnose, 归因, attribution, 问题分析, root cause, 指标下降, conversion rate decline, ROAS decline, CPA increase, 全链路, full-funnel, 异常检测, anomaly, 问题出在哪, why the decline.
Automates ingestion of documents into the Obsidian wiki (obsidian-wiki) using the wiki-ingest pipeline. Handles deduplication via manifest, frontmatter, and cross-links; triggers on user request within the obsidian-wiki project context.
Foreign-exchange rates for all currencies supported by Longbridge Securities — HKD / USD / CNY / SGD / EUR / GBP / JPY / etc. Use to convert multi-currency holdings, normalise account values, or quote a cross-rate. Light-touch utility skill, no login required. Triggers: "汇率", "美元兑港币", "人民币兑美元", "港币换美金", "今天汇率", "USD HKD", "CNY USD", "外汇", "匯率", "美元兌港幣", "人民幣兌美元", "港幣換美金", "今天匯率", "外匯", "exchange rate", "fx rate", "currency conversion", "USD to HKD", "HKD to USD", "CNY to USD", "JPY to USD", "convert HKD to USD", "1 USD in HKD".
Buffett-style single-stock moat diagnostic — "Would Buffett buy this stock?" Five dimensions: business & moat / financial health / management & capital allocation / valuation & margin of safety / long-term visibility. Data from Longbridge CLI first, MCP fallback, WebSearch only for gaps. Runs cross-statement reconciliation (勾稽校验) BEFORE scoring; data-source appendix closes with a one-line reconciliation summary. Output: star-rated radar card, dimension detail, Buffett-voice narrative, mandatory holding-period education block. Triggers: "巴菲特", "护城河", "巴菲特会买吗", "价值投资", "好生意", "宽护城河", "定价权", "诊股", "巴菲特诊股", "巴菲特视角", "长期持有", "護城河", "巴菲特會買嗎", "價值投資", "寬護城河", "定價權", "診股", "巴菲特診股", "巴菲特視角", "長期持有", "Buffett", "Warren Buffett", "moat", "economic moat", "wide moat", "pricing power", "value investing", "owner earnings", "would Buffett buy", "Berkshire-style", "quality compounder".
OmniStudio Data Mapper (formerly DataRaptor) creation and validation with 100-point scoring. Use when building Extract, Transform, Load, or Turbo Extract Data Mappers, mapping Salesforce object fields, or reviewing existing Data Mapper configurations. TRIGGER when: user creates Data Mappers, configures field mappings, works with OmniDataTransform metadata, or asks about DataRaptor/Data Mapper patterns. DO NOT TRIGGER when: building Integration Procedures (use building-omnistudio-integration-procedure), authoring OmniScripts (use building-omnistudio-omniscript), or analyzing cross-component dependencies (use analyzing-omnistudio-dependencies).