Loading...
Loading...
Found 1,282 Skills
Use when the user has an SRT (or transcript text) in one language and wants it translated to another, with punctuation-bounded re-segmentation so cues end at real sentence breaks. Simplified Chinese (zh-CN) and English (en) are first-class targets; other targets follow the same rules. Outputs a target-language SRT or bilingual SRT — no audio, no burn-in. Triggers — "翻译字幕", "翻成中文", "translate this SRT", "中英双语字幕", "把这个 SRT 翻译成 X", "bilingual subtitles".
This skill should be used when the user intends to repurpose content, such as requesting to "generate long-form article", "generate short-form post", "convert to WeChat Official Account article", "create versions for Moments/Twitter/Jike", or "generate other formats based on this script". It applies when the user wants to repurpose a finalized video script into a long-form article or short posts. Call li-writer to generate long-form articles (for WeChat Official Account) or short-form posts (for Moments/Twitter/Jike) based on confirmed short video scripts. Even if the user only mentions "create long-form article" or "create short-form post" without specifying the source script, proactively retrieve available scripts for the user to select from. Do NOT trigger the following: generating original scripts (use li-writer), optimizing openings (use li-opening), generating covers (use li-cover).
Every Tesla mobile-app feature, plus a charging-cost ledger and supercharger queue watcher no other Tesla CLI ships. Trigger phrases: `is my tesla ready`, `precondition my tesla`, `how much did i spend on charging this month`, `supercharger queue at`, `send this address to my tesla`, `list my tesla keys`, `use tesla`, `run tesla`.
Build a personalised voice profile inside a Cowork project from a short interview plus 3 to 5 sample pieces of writing. Works for any content format: LinkedIn posts, newsletters, essays, emails, blog posts, tweets, or any other published writing. Use this skill at the start of any Cowork project where the user wants Claude to learn who they are and how they write before drafting new content. Trigger whenever the user says "build my voice", "learn my voice", "set up my content system", "onboard me", "train on my writing", "train on my posts", "I want Claude to sound like me", or drops a batch of writing samples into chat at the start of a project. Also trigger for first-time Cowork users who need a voice foundation before writing anything. Always produces two files (about-me.md and voice.md) saved into the project root.
When the user wants to identify or fix keyword cannibalization in Google Ads — where multiple campaigns or ad groups are competing against each other in the same auction. Triggers on 'keyword cannibalization', 'campaigns competing with each other', 'duplicate keywords', 'keyword overlap', 'internal competition', 'same keyword in multiple campaigns', 'cannibalization check', 'campaign conflict', 'which campaign wins the auction', 'overlapping match types', or 'cross-campaign negatives'. For general negative keyword strategy see google-ads-negative-keywords.
Foundation patterns for the `hubspot` CLI — JSONL piping, batch read, pagination, dry-run/digest/confirm for destructive ops, and `hubspot history` for recovery. Every other skill builds on this one.
BaoStock A-share Data Platform, free and open-source, supports queries for stock quotes, K-lines, financial data, industry classification, and index constituent stocks; used when users need to obtain A-share historical quotes, financial statements, trading calendars and other data
Reusable pattern for presenting the user with explicit choices and gating execution until they respond. Used by other skills when a decision point requires human input before proceeding. Platform-agnostic — works on Telegram (inline buttons), Discord, CLI, or any agent with a message tool.
Use this skill when the agent needs to interact with CLAWLOGIC prediction markets. This includes: registering as an agent on-chain, creating new prediction markets, analyzing market questions to form opinions, buying YES/NO positions, asserting market outcomes via UMA Optimistic Oracle, disputing incorrect assertions from other agents, settling resolved markets to claim winnings, and posting bet narratives ("what I bet and why") to the frontend feed. Triggers: - "create a market about..." - "what do you think about [market question]?" - "buy YES/NO on market..." - "assert the outcome of market..." - "dispute the assertion on market..." - "check my positions" - "settle market..." - Any discussion about prediction markets, trading, or information markets
Create and maintain a product marketing context document covering positioning, ICP definition, messaging hierarchy, competitive differentiation, and value proposition. This skill creates the foundation that all other marketing skills reference. Trigger phrases: "product marketing," "positioning statement," "ideal customer profile," "ICP," "messaging hierarchy," "value proposition," "competitive differentiation," "product narrative," "use case mapping," "update our positioning," "what makes us different," "who is our customer," "messaging framework," "category design," "go to market strategy," "product story."
This skill should be used when the user asks about Mermaid diagram syntax, how to write flowchart, sequence, class, state, ER, Gantt, C4, mindmap, timeline, or other diagram types, node shapes, styling, theming, or rendering errors.
Build and deploy a Next.js, Bigfish (@alipay/bigfish), or Vite project to the Morphe service (https://morphe.zenmux.app), targeting a linux-x64-gnu runtime. Use when the user asks to deploy, ship, publish, or release a Next.js, Bigfish, or Vite app to Morphe, run "morphe deploy", or otherwise push a build to the Morphe / zenmux platform. Handles login, framework detection, Next.js standalone validation / config fixing, Bigfish static-server wrapping, Vite SPA static wrapping or custom-server (server.ts/js) esbuild bundling, building, zipping, OSS upload, CRC64 checksum, .morphe.json management, and the deploy API call.