Loading...
Loading...
Found 1,603 Skills
Claude Code extensibility: agents, skills, output styles. Capabilities: create/update/delete agents and skills, YAML frontmatter, system prompts, tool/model selection, resumable agents, CLI-defined agents. Actions: create, edit, delete, optimize, test extensions. Keywords: agent, skill, output-style, SKILL.md, subagent, Task tool, progressive disclosure. Use when: creating agents/skills, editing extensions, configuring tool access, choosing models, testing activation.
Guide for working with Shopify Metafields. Covers definitions, storing custom data, accessing via Liquid, and GraphQL mutations.
Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.
Design and apply AI personas for specialized contexts — project-specific voices, domain expert modes, or custom interaction styles. Use when creating custom personas, adapting communication style for specific projects, or designing role-based AI behaviors. Triggers on "페르소나", "persona", "역할 설정", "톤 설정", "voice", "캐릭터", "role definition".
Deep persona design for Agentforce agents with 50-point scoring. TRIGGER when: user designs agent personas, defines agent personality/identity, creates persona documents, encodes persona into Agent Builder fields, or asks about agent tone/voice/register. DO NOT TRIGGER when: building agent metadata (use sf-ai-agentforce), testing agents (use sf-ai-agentforce-testing), or Agent Script DSL (use sf-ai-agentscript).
Universal principles for agentic development when collaborating with AI agents. Defines divide-and-conquer, context management, abstraction level selection, and an automation philosophy. Applicable to all AI coding tools.
AI agent configuration policy and security guide. Project description file writing, Hooks/Skills/Plugins setup, security policy, team shared workflow definition.
Framework Overview of Major Historical Events - A framework-based overview of one macro historical event per day. Prioritize linking to recent hot topics, form a systematic cognitive framework, and provide social talking points. The output includes six modules: Definition, Causes, Process, Impacts, Cognitive Framework, and Talking Points Cheat Sheet.
Guides research ideation through a 5-step goal-driven workflow: define long-term goal, build literature tree (novelty + challenge-insight), select a problem (well-established solution check), design a solution (cross-domain transfer + decomposition), validate and iterate. Also covers structured paper reading (3 depth levels). Use when: user wants to find a research direction, brainstorm ideas, build field vision, do a literature review, evaluate idea novelty, or read papers systematically. Do NOT use for comparing/ranking existing ideas (use idea-tournament) or planning a paper (use paper-planning).
OmniStudio FlexCard creation and validation with 130-point scoring. Use when building at-a-glance UI cards, configuring data source bindings to Integration Procedures, or reviewing existing FlexCard definitions for accessibility and performance. TRIGGER when: user creates FlexCards, configures data sources, designs card layouts, or asks about OmniUiCard metadata. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or analyzing dependencies (use sf-industry-commoncore-omnistudio-analyze).
Use this skill when calculating, analyzing, or reporting SaaS business metrics. Triggers on MRR, ARR, churn rate, LTV, CAC, LTV:CAC ratio, cohort analysis, net revenue retention, expansion revenue, board deck metrics, investor reporting, unit economics, payback period, or SaaS financial modeling. Covers metric definitions, formulas, spreadsheet implementation, cohort tables, and board-ready reporting for founders, finance teams, and growth operators.
Perses-aware code review: check Go backend against Perses patterns, React components against Perses UI conventions, CUE schemas against plugin spec, and dashboard definitions against best practices. Dispatches appropriate sub-reviewers. Use for "review perses", "perses pr", "perses code review". Do NOT use for general Go/React review without Perses context.