Loading...
Loading...
Found 271 Skills
Create a lang/ plugin that wires any CLI tool or language runtime into gm-cc — adds exec:<id> dispatch, optional LSP diagnostics, and optional prompt context injection. Zero hook configuration required.
Remote command execution and file transfer on SageMaker HyperPod cluster nodes via AWS Systems Manager (SSM). This is the primary interface for accessing HyperPod nodes — direct SSH is not available. Use when any skill, workflow, or user request needs to execute commands on cluster nodes, upload files to nodes, read/download files from nodes, run diagnostics, install packages, or perform any operation requiring shell access to HyperPod instances. Other HyperPod skills depend on this skill for all node-level operations.
Use when monitoring or troubleshooting Cisco UCCE 12.6 — agent states, queue stats, PG diagnostics, CVP config, VVB calls, system health checks, and infrastructure inventory. Covers all cisco-ucce CLI operations across AW, Finesse, CVP, Diagnostic Portal, and VVB APIs.
Reference skill for Zoom Probe SDK. Use after routing to a preflight workflow when testing browser compatibility, media permissions, audio or video diagnostics, and network readiness before users join.
Startup diagnostic router. Use FIRST when a founder doesn't know where to start, has multiple overlapping problems, or asks a vague question like 'what's wrong with my startup', 'why aren't people buying', 'what should I focus on', 'where do I even begin', 'nothing is working'. Routes to the right framework from the 14 available skills — or tells you when no framework fits and you just need to go talk to people. This is the entry point. Use it before reaching for any specific skill.
Helps engineering managers understand and act on what drives each engineer — produces a three-driver framework (Growth, Connection, Impact), techniques for identifying someone's primary driver, driver-aligned delegation patterns, and a team composition diagnostic. Use when the user says "this person isn't motivated," "nobody picks up tasks," "I keep reminding people," "what drives my engineers," "how do I motivate my team," "what should I delegate to this person," "engineer seems disengaged," or "what growth activity should I give this person." Do NOT use when someone is actively leaving or at risk of quitting (use retaining-developers) or when the engineer is a high performer with specific management challenges (use managing-high-performers).
ARK-style single-stock disruptive-innovation diagnostic. Suitability gate on 4 dimensions (platform fit / innovation revenue / R&D intensity / management vision); if it passes, builds TAM (low/base/high), Wright's-Law cost curve with sourced learning rate, three-scenario 5-year target (Bull/Base/Bear, 15% discount), risks, conditional action frame. Data: Longbridge CLI first, MCP fallback, WebSearch only for TAM / learning rates / industry runway. Runs cross-statement reconciliation BEFORE analysis. Closes with a data-source appendix whose final row is the reconciliation summary. Independent implementation — not affiliated with ARK Invest. Triggers: "木头姐", "ARK", "ARKK", "颠覆式创新", "莱特定律", "TAM", "5年目标价", "情景分析", "AI 与大数据", "自动化与机器人", "能源存储", "基因革命", "区块链与金融科技", "木頭姐", "顛覆式創新", "萊特定律", "5年目標價", "Cathie Wood", "ARK Invest", "disruptive innovation", "Wright's Law", "learning rate", "bull base bear", "scenario analysis".
Run ACB (Anypoint Code Builder) system diagnostics to check if the machine meets minimum specifications and apply Windows optimizations if needed
Collect comprehensive debug information for Clerk issues. Use when troubleshooting complex problems, preparing support tickets, or diagnosing intermittent issues. Trigger with phrases like "clerk debug", "clerk diagnostics", "clerk support ticket", "clerk troubleshooting".
Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic".
Help create and optimize blog posts, articles, and polished writing with rigorous structure, reader expectation management, and SCQA methodology. This skill contains a specialized writing framework (reader personas, concept introduction protocol, diagnostic checklists, Pyramid Principle structure) that cannot be replicated without loading it. You must use this skill in any of these scenarios: (1) writing a blog post or article from notes/materials, (2) reviewing, diagnosing, or optimizing any draft or article for structure, clarity, and readability, (3) polishing or refining notes into publishable form, (4) giving feedback on writing structure, flow, or reader experience, (5) creating outlines for articles. Trigger on keywords: "博客", "文章", "发布", "blog", "写作", "初稿", "打磨", "诊断", "优化文章", "结构", "大纲", "投稿", "公众号", "读者". Also trigger when the user shares a markdown file and asks to improve it, or asks if something "reads well" or "makes sense to readers".
C/C++/CAPL best practices for automotive embedded systems. This skill should be used when writing, reviewing, or refactoring embedded C/C++ code or CAPL scripts targeting automotive ECUs, following MISRA, AUTOSAR, ISO 26262, and ISO 21434 guidelines. Triggers on tasks involving embedded firmware, CAN/CAN FD/LIN/Ethernet communication, TCP/UDP/DoIP/SOME-IP protocols, RTOS programming, safety-critical code, cybersecurity, diagnostics (UDS), CAPL test automation, or calibration toolchain integration.