Loading...
Loading...
Found 1,339 Skills
This skill should be used when the user asks to "fix my skill" or "audit this skill". Make sure to use this skill whenever the user mentions skill quality, structural issues, broken skills, or skill diagnostics — even if they don't explicitly say "repair-skill". Not for adding features or improving effectiveness — use improve-skill. Not for agents — use repair-agent.
Use this skill when rendering live HTML/DOM elements (or frozen snapshots of them) as PixiJS v8 textures via the EXPERIMENTAL HTML-in-Canvas browser APIs. Covers the pixi.js/html-source side-effect import, feature-detection with canvas.requestPaint, HTMLSource for a live, repainting element kept interactive in the browser (autoLayout/autoUpdate/autoRequestPaint, requestPaint, isReady, the direct-child-of-canvas + layoutsubtree requirement), ElementImageSource for an immutable captureElementImage() snapshot (autoClose, ready immediately), using the source on a Sprite/Texture/Mesh, fallback-only auto-detection via Texture.from at priority -10, and destroy/cleanup. Triggers on: HTMLSource, ElementImageSource, pixi.js/html-source, requestPaint, captureElementImage, ElementImage, layoutsubtree, autoRequestPaint, autoUpdate, autoClose, HTML in canvas, render DOM to texture, HTMLSourceOptions, ElementImageSourceOptions, HTMLSourceCanvas, experimental.
Use when creating or improving persuasive copy, launch offers, fundraising appeals, onboarding prompts, sales pages, calls to action, or behavior-change messages where the goal is effective persuasion without deception, coercion, fake proof, fake scarcity, or overstated authority.
Compose and Compose Multiplatform expert for UI development across Android, Desktop, iOS, and Web. Use whenever the user mentions Compose APIs (@Composable, remember, LaunchedEffect, NavHost, MaterialTheme, LazyColumn, Modifier, recomposition), Compose Multiplatform (commonMain, expect/actual, Res.*, ComposeUIViewController, UIKitView, ComposeViewport), Android TV (tv-material, D-pad, focus, Carousel), Material 3 motion, atomic design systems, design-to-code workflows, Paging 3, or navigation. Activates Review Mode on GitHub PR URLs and review phrases ("review this PR", "what's wrong with this"). Auto-detects Compose projects on session_start. Backed by actual androidx/androidx and JetBrains/compose-multiplatform-core source receipts. See "## When this skill applies" in SKILL.md for the full trigger surface.
When the user wants to design, optimize, or improve lead qualification forms and processes. Also use when the user mentions "lead scoring," "qualification criteria," "BANT," "discovery questions," "intake form," "lead routing," "MQL," "SQL," or "qualification framework." This skill covers capturing the right information to qualify and prioritize sales leads effectively.
The X/Twitter growth playbook for 2026. Use when someone wants to "grow on X / Twitter," "get more reach/followers/impressions on X," "an X content/posting strategy," "should I get X Premium," "how the X algorithm works," or how to use replies/quote-posts/long-form/video to grow. Conversation is the engine (replies and first-hour velocity), Premium is effectively a baseline, and links go in the first reply. Uses the SPARK framework. Reads brand-profile + voice-builder first. The agent drafts posts + reply copy; a human does the live replying/quote-posts/community engagement; WoopSocial schedules posts; metrics come from native X analytics; nothing is fabricated. Complements thread-writer (thread-format craft).
Use the iPhone Duo hinge angle for interactions and effects, support Split View multitasking and multiple app scenes, and pair UI across both displays with scene accessories including CameraCaptureAccessory. Use when building fold-driven effects, multi-window support, or dual-display experiences.
Quantitative strategy frameworks: pairs trading/cointegration, volatility regime strategies, seasonality/calendar effects, multi-factor models (IC/IR), factor research and screening, correlation analysis, statistical methods (ADF/GARCH), strategy optimization, execution modeling, hedging, and ML-based prediction (sklearn). Also provides CLI access to run indicator scripts against K-line data. Triggers: "量化", "因子", "配对交易", "协整", "波动率策略", "季节性", "多因子", "IC", "机器学习", "对冲", "量化策略", "協整", "波動率策略", "季節性", "多因子", "對沖", "quant", "pairs trading", "cointegration", "volatility strategy", "seasonality", "multi-factor", "factor model", "IC IR", "machine learning", "hedging", "walk-forward", "配對交易", "機器學習", "因子選股"
Viewer release-notes overstack TỨC THÌ (kiểu /release-notes của Claude CLI). Gõ /ovs-notes → liệt kê NGAY changelog OVERSTACK framework (newest-first) để chọn & đọc; /ovs-notes <version|latest> in đầy đủ; /ovs-notes --here = release của PROJECT hiện tại. READ-ONLY, KHÔNG side-effect — KHÁC /ship (quy trình CẮT release). Trigger: /ovs-notes, 'xem release notes', 'release notes bản nào', 'changelog', 'các bản đã ra', 'bản mới nhất có gì'.
Best practices for using Claude Code effectively based on insights from its creator Boris Cherny. Trigger this skill when users ask about optimizing Claude Code usage, configuring CLAUDE.md files, using plan mode, working with sub-agents, understanding Claude Code philosophy, improving coding productivity with Claude Code, or building AI coding tools. Also trigger when users mention blatant demand, scaffolding in AI products, building for future model capabilities, or ask about Anthropic's approach to AI coding assistants.
Interactively manage Sub-Store node subscriptions and multi-source collections; orchestrate operator pipelines (filtering/renaming/flagging/sorting/deduplication); author and mount JavaScript node-processing scripts on demand; and export clean node subscriptions or Proxy Provider links. Strictly follow the Sub-Store frontend Web UI two-way-binding conventions by constructing complete Schemas, fully preventing issues where “backend execution takes effect but frontend radio controls become desynchronized, input fields remain blank, or configuration is overwritten and lost by the UI.”
Choose a cost-effective Cloudflare architecture using Workers, Static Assets, KV, D1, R2, Durable Objects, Queues, and Workers Logs while avoiding designs that lead to ballooning bills. Use this when designing Cloudflare deployments, adding Workers or bindings, deciding how to distribute pages and data, or writing loops and retry logic.