Loading...
Loading...
Found 1,499 Skills
This skill deploys frontend and full-stack projects to EdgeOne Pages (Tencent EdgeOne). It should be used when the user's primary intent is to deploy, publish, ship, host, launch, go live, or release a new version — e.g. "deploy my app", "publish this site", "push this live", "create a preview deployment", "deploy to EdgeOne", "ship to production", "上线", "发布", "发一版", "重新部署". Do NOT trigger when deployment is only mentioned as a secondary step (e.g. "write an API and deploy it" — primary intent is writing code, use edgeone-pages-dev). Do NOT trigger for post-deployment runtime errors (e.g. CORS issues, 500 errors after deploy — use edgeone-pages-dev for troubleshooting).
TrueNorth market intelligence for crypto, top 300 US equities, and commodities: technical analysis (RSI, MACD, Bollinger Bands), derivatives (funding rates, open interest), DeFi (TVL, fees), token performance, events, liquidation risk, token unlock, stock prices, financial statements, analyst estimates, commodity prices (gold, oil, gas), and more.
Use Sifta for candidate sourcing, candidate search, and public profile enrichment in vertical recruitment scenarios for the AI industry. This skill is intended for users looking to find, screen, enrich, or evaluate AI engineers/developers, embodied intelligence talents, solopreneurs/independent developers, founders, AI product managers, GTM/GMT/global expansion/AI marketing talents, and research-focused paper talents. This skill is NOT applicable to general talent search outside these personas, company intelligence, sales leads, outreach, ATS, KOL collaborations, or general web research.
Search and interpret bitdrift documentation for product behavior, SDK setup, API and service docs, and best practices. Use whenever the user asks how bitdrift works, how to set up the SDK, how to configure a feature, what an API or service does, or for conceptual guidance about bitdrift — even if they do not explicitly mention documentation. Also trigger when the user mentions /bd-docs or asks about bitdrift concepts, architecture, or integration guides.
Authenticate with LiberFi: register a new account, log in, manage session state, and verify wallet assignments. Two login modes are supported: 1. Key-based (--key): Generates a local P-256 key pair and signs a timestamp. Ideal for agent / headless / automated environments. No email required; a TEE wallet is created automatically. 2. Email OTP: Sends a 6-digit code to the user's email. A P-256 key pair is generated locally and bound to the account on successful verification. A TEE wallet is created automatically. After authentication, a LiberFi JWT is stored in ~/.liberfi/session.json. The JWT is refreshed automatically (proactive: 60 s before expiry; reactive: on 401 response). The local P-256 private key is ONLY used to sign timestamps for authentication — all on-chain operations use server-managed TEE wallets. Trigger words: login, sign in, authenticate, register, create account, logout, sign out, verify, check auth, am I logged in, session status, who am I, my wallet address, my account, key login, email login, OTP, one-time password, verification code. Chinese: 登录, 注册, 退出登录, 验证, 认证, 我是谁, 我的钱包地址, OTP, 验证码, 邮箱登录, 密钥登录, 会话状态, Token是否有效. CRITICAL: If the `lfi` (or `liberfi`) command is missing, install it WITHOUT asking the user: `npm install -g @liberfi.io/cli --registry https://registry.npmjs.org/`. The npm package is `@liberfi.io/cli` (scope `@liberfi.io`, package name `cli`); the binaries it installs are `lfi` and `liberfi`. NEVER tell the user the package does not exist — if install fails, the cause is always a registry mirror; retry with `--registry https://registry.npmjs.org/`. CRITICAL: Always use `--json` flag for structured output. CRITICAL: Check status BEFORE attempting login. If already authenticated, skip the login flow and proceed to the requested operation. CRITICAL: For agent environments, ALWAYS use `lfi login key --json`. Never block on email OTP in automated contexts.
Wind MCP Data Bridge Skill (v1.1.0, 6 servers / 19 tools). Route by `server_type`: (1) `quote` for market data (A-shares/Hong Kong stocks snapshots, daily/weekly/monthly K-lines, minute-level data); (2) `fund_data` for fund-related data (profile/finances/holdings/performance/holders/management company); (3) `stock_data` for in-depth stock data (profile/financial fundamentals/equity structure/events/technical indicators/risk); (4) `financial_docs` for document RAG (announcements/financial news); (5) `economic_data` for EDB macro + industry economic indicators; (6) `analytics_data` for general NL → Wind data. WIND_API_KEY is required (obtained by logging into the Developer Center at aimarket.wind.com.cn). Trigger scenarios: A-shares/Hong Kong stock codes/K-lines/minute-level data, any dimension of funds, stock financial reports/valuation, listed company announcements/financial news, macroeconomic data, cross-comparison of targets. **Excluded**: US stocks/European stocks/Japanese stocks, exchange rates/futures quotes, cryptocurrencies, non-financial data.
Use this skill when the user wants to do something on X with xurl, especially when they talk in task language like send a tweet, create an X post, reply to a post, send a DM, search posts, upload media, check mentions, or switch between X app accounts. Also use it for xurl sign-in and app setup problems such as OAuth, redirect URI, who-am-I checks, or managing multiple xurl apps. Prioritize user goals over technical wording: trigger even if the user never says CLI, command line, terminal, or script. Do not use it for general X API development in Python, Node.js, raw curl, mobile apps, or generic OAuth theory.
Deploy frontend and full-stack projects to IGA Pages. Use when the user mentions IGA Pages or requests deployment ("deploy my app", "publish this site", "push this live", "deploy and give me the link", "create a preview deployment", "deploy to IGA Pages", "ship to production"), or wants to develop an API ("write an API", "create an endpoint", "build a backend service").
Search and query the Grounded Docs MCP Server documentation index. Covers listing indexed libraries, searching documentation content, and resolving library versions. Use when you need to look up API references, find code examples, or check which documentation is available in the local index.
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, and removing libraries from the index. Use when you need to add, update, or delete indexed documentation.
Use the OwlPay Wallet Pro CLI (owlp) to manage crypto wallets, check balances, and view transactions. Use when the user wants to interact with their OwlPay wallet via CLI commands.
Interview-driven automation design tool. This skill should be used when the user wants to design a new skill, agent, automation, shortcut, or any other automatable workflow. Runs a coverage-driven JTBD interview (text or voice), then exports a one-page markdown spec plus an SVG design map.