Loading...
Loading...
Found 235 Skills
Debug HWP layout, dump document IR, compare versions, extract thumbnails, and unlock read-only HWPs with the upstream rhwp Rust CLI (export-svg/dump/dump-pages/ir-diff/thumbnail/convert).
Smart-money and ownership-flow signals for a single stock via Longbridge Securities — SEC 13F institutional portfolios + position changes (US), funds and ETFs that hold the stock, SEC Form 4 insider trades (US-only), US short-interest history, and HK broker holdings (HK-only). Read-only. Markets vary by subcommand. Triggers: "13F", "机构持仓", "基金持仓", "ETF 持有", "持有这只股票的基金", "内部人交易", "高管买卖", "Form 4", "做空数据", "空头", "卖空", "经纪商持仓", "中央结算", "13F", "機構持倉", "基金持倉", "ETF 持有", "持有這隻股票的基金", "內部人交易", "高管買賣", "做空數據", "空頭", "賣空", "經紀商持倉", "中央結算", "13F holdings", "institutional holders", "fund holders", "ETF holders", "insider trades", "insider buying", "insider selling", "Form 4", "short interest", "days to cover", "short ratio", "broker holding", "CCASS", "AAPL insider sales", "TSLA short interest", "700.HK broker holding".
Check Meilisearch index status, tasks, health, and settings. Use for debugging search issues, monitoring indexing tasks, and inspecting index configuration. Read-only admin operations.
Smoke test for alicloud-compute-fc-agentrun. Validate minimal authentication, API reachability, and one read-only query path.
PANews creator workflow — authenticate, manage column applications, upload images, and create or submit articles. Requires PA-User-Session. Use panews for public read-only access instead.
HODLMM volatility risk monitor — reads Bitflow HODLMM pool state, computes current-state volatility proxy from bin distribution, scores regime (calm/elevated/crisis), and emits position-sizing or liquidity-pull signals for LP agents. Read-only; no wallet required.
Delegate coding, review, diagnosis, planning, structured output, and native browser research tasks to independent Codex sessions via Codex CLI. Use cases include creating new tasks with `codex exec`, resuming multi-turn sessions with `codex exec resume`, performing read-only reviews with `codex exec review`, as well as scenarios requiring `--json` event streams, `-o` final message persistence, image input, or Computer Use browser operations.
Preview an existing saved CARTO Builder map inline in the chat via the CARTO MCP server's load_builder_map tool. Use whenever the user references a saved Builder map — by URL, by ID, or by name (resolved via list_maps first). Renders a lightweight read-only preview (layers, basemap, viewport, popups, legend). Widgets, SQL parameters, map description, and other Builder-only features are NOT included; the user can click "Open in Builder" for the full experience. Triggers on "show me the X map", "open the Y map", "preview the Z map", and post-CLI-creation inline previews of a freshly-created map. Distinct from carto-create-builder-maps (CLI authoring), carto-render-inline-map (ad-hoc deck.gl spec), and carto-develop-app (developer app).
Uniview Smart Parking Open Platform Data Analysis Domain openydt data: Read-only data statistics and reports including parking lot payment bills, bill summaries, traffic flow, top license plate distribution, real-time parking lot data, daily vehicle exit/transaction counts, per-minute traffic flow, parking space usage, parking duration analysis, etc. Trigger words: data analysis/statistics/reports/check bills/payment bills/bill summaries/traffic flow/traffic statistics/top license plates/license plate distribution/real-time data/present vehicles/exit counts/transaction counts/per-minute traffic/parking space usage/parking space utilization rate/parking space occupancy/heatmap/echart/parking duration/duration analysis/parking duration distribution
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code quality, DRY, refactor review.
Pre-PR review pipeline — runs security, API audit, and scope check agents in parallel. Read-only, no changes. Use before creating PRs or after completing a phase of work.
Read-only exploration, status checks, and reporting without modifications. Use when user asks to check status, find files, search code, show state, or explicitly requests read-only investigation. Do NOT use when user wants changes, fixes, refactoring, or any write operation.