Loading...
Loading...
Found 10,823 Skills
Comprehensive SAP Joule CLI (formerly sapdas CLI) assistant for managing digital assistants from the command line — compiling capabilities, deploying assistants, running BDD tests, linting, and troubleshooting errors. Use this skill whenever the user mentions "joule cli", "sapdas", "joule compile", "joule deploy", "joule test", "joule login", "joule lint", digital assistant deployment, capability compilation, DAAR files, RTA artifacts, or any task involving the Joule command line interface — even if they just say something like "deploy my assistant" or "how do I log in to Joule from the terminal". Also trigger when the user asks about testing Joule capabilities with Cucumber, linking AI assistants, managing deployed assistants, or automating Joule workflows in CI/CD pipelines.
Soroban smart contract development on Stellar (Rust SDK). Covers project setup, contract structure, storage types, authorization, cross-contract calls, events, error handling, testing (unit, integration, fuzz, property, mutation, fork, differential), security patterns and vulnerability classes, advanced architecture patterns (upgrades, factories, governance, DeFi primitives), and common pitfalls. Use when writing, testing, securing, or shipping Soroban contracts.
Use this skill when the user asks about Goldsky Edge — the managed RPC endpoint service for EVM chains. Triggers on: 'Edge RPC', 'Goldsky RPC endpoint', 'edge.goldsky.com', 'eth_getLogs is slow', 'RPC rate limit', 'hedged requests', 'flashblocks', 'HyperEVM system transactions', 'x402 pay-per-request RPC', 'Goldsky Edge pricing', 'Edge dashboard', 'gs_edge_ API key', 'rpc-edge'. Also use this skill when the user wants a resilient, low-latency JSON-RPC endpoint for EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon zkEVM, BSC, Avalanche, Berachain, HyperEVM, Monad, Sei, Sonic, Unichain, zkSync, etc.), is debugging RPC errors like -32005/-32012/-32014/-32015/-32016, or is comparing providers (Alchemy, Infura, QuickNode, Ankr) against Edge. For questions about self-hosting eRPC or custom eRPC configuration beyond what Edge exposes, point them at https://docs.erpc.cloud/llms.txt. Do NOT trigger on Goldsky Mirror, Turbo, or Subgraph pipeline questions — those belong to their respective skills.
Wang Jianshuo's thinking framework and expression style. Based on 7 in-depth researches (about 1 million words of English blogs + about 1.09 million words of Chinese blogs, 2002–2022, all first-hand), 7 core mental models, 10 decision-making heuristics and a complete bilingual expression DNA are extracted. Purpose: Write, respond and think from Wang Jianshuo's identity and voice—he is plain, sincere and curious, loves to use everyday metaphors and self-created words, repeatedly builds ladders between the concrete and the abstract, and never writes anything he hasn't personally verified. Activate when users mention phrases like "from Wang Jianshuo's perspective", "what would Wang Jianshuo think", "Wang Jianshuo's mode", "write like Wang Jianshuo", "Jian Shuo Wang perspective", "switch to Wang Jianshuo". It should also be triggered even if users only say "help me think from Wang Jianshuo's angle" or "how would Wang Jianshuo write this article". Once activated, all subsequent responses in this conversation will maintain Wang Jianshuo's identity until the user explicitly says "exit"—no need to name him repeatedly in each round. Inapplicable scenarios: When users ask for objective introductions or factual inquiries about Wang Jianshuo himself (such as "Who is Wang Jianshuo" or "When did he start his business"), answer such questions normally without entering role-playing.
Revenue playbook for getting a mobile or web subscription app from zero to early MRR. Use when users ask how to make revenue, reach $1K MRR, monetize an app, get first users, improve ASO, plan TikTok/Reels/Shorts or Reddit acquisition, design a paywall, choose freemium vs trial, price subscriptions, reduce churn, or build a simple growth loop for an app.
Use when tasks are complex and require full microservices collaboration: The main agent acts as a pure Orchestrator, strictly prohibited from writing code personally, and is responsible for accurately assigning responsibilities such as positioning, planning, coding, testing, and review to corresponding sub-agents (explorer, planner, worker, verifier, reviewer, fixer). This Skill enforces microservices workflow discipline, requiring full Chinese communication, minimal routing output, and minimized context transfer.
HK IPO Subscription Analysis — A "Four-Dimensional Evaluation" framework to diagnose whether Hong Kong new stocks are worth subscribing (Pricing Rationality / Issue Quality / Market Timing / Fundamental Outlook). Outputs three-tier ratings: Recommend / Neutral / Avoid, plus prospectus highlights, risk warnings, and subscription references. It is retail-investor friendly with conclusions upfront. Covers three scenarios: in-depth evaluation of a single new stock, browsing recent IPO subscription calendars, and judging whether to chase newly listed stocks after missing the subscription. Prioritizes data from Longbridge CLI (ipo detail / ipo subscriptions / ipo wait-listing / ipo listed / peer-comparison / news / quote / kline / index-quote, etc.); uses MCP fallback for data missing from CLI; uses WebSearch as a last resort for data still unavailable (prospectus TAM, original cornerstone announcement, claw-back ratio, grey market price, underwriter industry ranking). **The report must end with a fixed "Data Source Details" appendix**, where every figure can be traced to line number + capture time + period. Only covers Hong Kong Main Board and GEM; does not involve US / A-share IPOs; must actively prompt leverage risks when margin financing (孖展) is involved. Triggers: "打新", "港股打新", "新股申购", "新股申購", "新股", "打新分析", "新股分析", "招股", "招股书", "招股書", "基石投资者", "基石投資者", "国际配售", "國際配售", "公开发售", "公開發售", "暗盘", "暗盤", "回拨机制", "回撥機制", "孖展", "新股盈亏", "新股盈虧", "次新股", "破发", "破發", "中签率", "中籤率", "新股几手", "新股幾手", "新股值不值得打", "新股能不能打", "港股 IPO 推荐", "港股 IPO 推薦", "近期港股新股", "HK IPO analysis", "hong kong IPO worth it", "HK new listing", "cornerstone investor", "prospectus highlights", "grey market premium", "subscription ratio", "claw-back", "margin financing IPO", "0700.HK", "09988.HK", "01024.HK"
Prioritized TypeScript React code review guidelines. Focuses on type safety, React conventions, performance, security, architecture, accessibility, error handling, and testing. First scan the code to identify issues, then obtain solutions and review comment templates from the references/ directory.
Submission cover letter assistant for academic papers. Generate, optimize, align-check, and journal-fit-check a cover letter using an existing LaTeX manuscript as the evidence source. Use for "write cover letter", "draft submission letter", "polish cover letter", "check overclaim in cover letter", "align cover letter with paper", "投稿信", "cover letter for Nature/Science/Cell/IEEE Trans/ACM/Springer LNCS/NeurIPS/ICML/CVPR", "review my submission letter", "manuscript cover letter generation", "is my cover letter framed for this journal". Use latex-paper-en for source edits to main.tex, paper-audit for full manuscript review, and bib-search-citation for bibliography search instead.
Use when the user asks for a broad codebase review, substantial PR/branch review, architecture audit, tech-debt scan, cleanup assessment, structural sanity check, or design-alignment review. Default workflow: use sub-agents when available unless specifically forbidden; do not require the user to mention sub-agents, council mode, delegation, or parallel review. Focus on cruft, duplication, weak boundaries, missed reuse, lifecycle/concurrency risks, test/roadmap drift, and code aesthetics. Do not use for narrow bug fixes, ordinary small-diff reviews, frontend visual QA, repo-onboarding docs, or OpenAI Agents SDK production-readiness review. Output evidence-backed findings first, then pressure points, design alignment, open questions, and follow-through.
Build a complete agent-readable Obsidian vault for a Tailwind-based web codebase, eight flat top-level domain docs (PRODUCT/RUNTIME/ARCHITECTURE/DATA/AUTH/ENGINEERING/TESTING/DESIGN), folder-level deep specs, bidirectional wikilinks for graph navigation, and a `DESIGN.md` that conforms to the google-labs-code/design.md spec with tokens derived from `tailwind.config.{ts,js}` or the v4 `@theme` block. Use when asked to "set up project docs", "write project documentation", "create an Obsidian vault from this repo", "document this codebase for agents", "add a DESIGN.md", or "make the design system machine-readable".
Use only to generate or update a governance skill card for a specified existing agent skill directory. Do not use for explaining, listing, comparing, or discussing skill capabilities.