Loading...
Loading...
Found 2,183 Skills
Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
Apply when building catalog or SKU synchronization logic for VTEX marketplace seller connectors. Covers the changenotification endpoint, SKU suggestion lifecycle, product data mapping, price and inventory sync, and fulfillment simulation. Use for implementing seller-side catalog integration that pushes SKUs to VTEX marketplaces with proper notification handling and rate-limited batch synchronization.
Explore a codebase for architectural friction, discover refactoring opportunities, and propose module-deepening refactors as GitHub issue RFCs. Uses friction-driven exploration and parallel sub-agents to design multiple interface alternatives. Use when user wants to improve architecture, find refactoring opportunities, consolidate coupled modules, reduce complexity, make code more testable, or review codebase health.
Optimizer that refines and professionalizes AI agent skills through real usage — saves tokens, eliminates redundancy, and tightens instructions so skills cost less to run. Learns from mistakes, reviews quality, and improves over time. Observes skill execution in the current conversation, analyzes up to four sources (conversation friction, file diffs, user feedback, static diagnostic) plus accumulated lessons, and proposes concrete improvements to the target skill's SKILL.md. Works with Claude Code and compatible SKILL.md-based agent frameworks. Use after executing any skill: `/skill-optimizer [name]` or `/skill-optimizer` to auto-detect. `--review` processes accumulated lessons.
Deep Research Skill for Horizontal-Vertical Analysis. Proposed by digital life Khazix, it integrates core ideas from Saussure's diachronic-synchronic analysis, longitudinal-cross-sectional research design in social sciences, business school case study methods, and competitive strategy analysis. It is used when users want to systematically research a product, company, concept, technology, or person. The core is dual-axis analysis: the vertical axis tracks the complete life cycle from birth to the present (presented as a narrative story), while the horizontal axis conducts a systematic horizontal comparison with competitors/peers at the current time point. Finally, unique insights are generated by intersecting the two axes, and a beautifully formatted PDF research report is produced as the final output. Trigger words include but are not limited to: horizontal-vertical analysis, research for me, help me analyze, in-depth research, conduct a research, investigate, competitor analysis, help me understand how this thing is, what's this product/company/concept about, help me figure it out, help me understand it, do a deep research for me. Even if the user only says "help me understand XX" or "what's the background of XX", it should be triggered as long as the context implies a need for systematic in-depth research (rather than a simple conceptual explanation). It also applies to scenarios where the user sends a product name, company name, or technical term and says "help me research this". Do not use it for simple noun explanations (when the user only asks "what is XX"), do not use it for official account writing (use khazix-writer for that), and do not use it for pure title abstract generation (use wechat-title for that).
Analyze previous Jetty workflow runs and propose targeted improvements to your runbook. Use when the user wants to optimize, improve, or debug a runbook based on past execution results — including 'optimize runbook', 'improve runbook', 'why is my runbook failing', 'analyze my runs', 'runbook not working well', 'make my runbook better', 'debug runbook performance', or 'learn from past runs'. Also trigger when the user mentions trajectory analysis, run patterns, or evaluation score improvements.
Master philosophy of language - meaning, reference, truth, speech acts. Use for: semantics, pragmatics, meaning theory, reference. Triggers: 'meaning', 'reference', 'Frege', 'sense', 'Kripke', 'speech act', 'semantics', 'pragmatics', 'truth conditions', 'propositions', 'names', 'descriptions', 'rigid designator', 'natural kind', 'context', 'indexical'.
When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.
Provide instructions on how to build with Arc, Circle's blockchain where USDC is the native gas token. Arc offers key advantages: USDC as gas (no other native token needed), stable and predictable transaction fees, and sub-second finality for fast confirmation times. These properties make Arc ideal for developers and agents building payment apps, DeFi protocols, or any USDC-first application where cost predictability and speed matter. Use skill when Arc or Arc Testnet is mentioned, working with any smart contracts related to Arc, configuring Arc in blockchain projects, bridging USDC to Arc via CCTP, or building USDC-first applications. Triggers: Arc, Arc Testnet, USDC gas, deploy to Arc, Arc chain, stable fees, fast finality.
Build crypto wallets using Circle Modular Wallets SDK with passkey authentication, gasless transactions, and extensible module architecture. Use when: creating crypto wallets with passkey-based (WebAuthn) registration and login, sending gasless transactions using Circle Gas Station paymaster, batching multiple transactions into a single user operation, implementing passkey recovery using BIP-39 mnemonic phrases, building advanced onchain wallets with custom modules (multisig, subscriptions, session keys). Triggers on: modular wallet, smart account, MSCA, passkey authentication, WebAuthn, gasless, paymaster, Gas Station, bundler client, user operation, userOp, ERC-4337, ERC-6900, account abstraction, toCircleSmartAccount, toPasskeyTransport, toModularTransport, sendUserOperation, batch transactions, 2D nonce, passkey recovery, EIP-1193 provider.
MUST activate when the project contains a uiBundles/*/src/ directory and the task involves adding or modifying a chat widget, chatbot, or conversational AI. Use this skill when the user asks to add, embed, integrate, configure, style, or remove an agent, chatbot, chat widget, conversation client, or AI assistant. Covers styling (colors, fonts, spacing, borders), layout (inline vs floating, width, height, dimensions), and props (agentId, agentLabel, headerEnabled, showHeaderIcon, showAvatar, styleTokens). Activate when files under uiBundles/*/src/ import AgentforceConversationClient or when adding any chat or agent functionality to a page. Never create a custom agent, chatbot, or chat widget component.
Reviews Rust test code for unit test patterns, integration test structure, async testing, mocking approaches, and property-based testing. Covers Rust 2024 edition changes including async fn in traits for mocks,