example-skill
This skill should be used when demonstrating skill structure and format. Provides example patterns for creating new skills.
What this skill does
# Example Skill A demonstration skill showing the proper structure and format for Claude Code skills. ## When to Use This Skill - Creating new skills and need a reference - Understanding skill structure and best practices - Learning how to bundle resources with skills ## What This Skill Does 1. Demonstrates proper YAML frontmatter format 2. Shows content structure requirements 3. Provides examples of bundled resources 4. Illustrates best practices for skill documentation ## Core Principles ### Principle 1: Clear Purpose Skills should have a clear, well-defined purpose. The "When to Use" section should make it obvious when to apply the skill. ### Principle 2: Progressive Disclosure Structure content from high-level overview to detailed implementation. Start with "When to Use" and "What This Skill Does" before diving into workflows. ### Principle 3: Actionable Workflows Provide step-by-step workflows that can be followed directly. Include examples and anti-patterns. ## Workflow ### Step 1: Identify Need Determine if this skill is appropriate for the current task. ### Step 2: Review Documentation Read the skill documentation to understand capabilities and limitations. ### Step 3: Apply Skill Follow the workflow steps to apply the skill. ### Step 4: Validate Results Check that the skill achieved the intended outcome. ## Best Practices - Keep skills focused on a single domain or capability - Include clear examples and use cases - Document anti-patterns to avoid common mistakes - Bundle resources when they add value ## Anti-Patterns - Creating overly broad skills that try to do everything - Skipping the "When to Use" section - Missing examples or use cases - Not documenting bundled resources ## Examples ### Example 1: Basic Usage **Scenario:** Creating a new skill for code review **Approach:** 1. Review this example skill structure 2. Use the template from `steve/templates/AGENT_SKILL.template.md` 3. Fill in domain-specific content 4. Add bundled resources if needed ## Reference Files This skill includes reference files in `references/`: - `structure-guide.md`: Detailed structure guidelines - `examples.md`: Additional examples
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.