Example Greeting Skill

Included with Lifetime

$97 forever

This skill activates when users discuss the example plugin, demonstrating how skills auto-activate based on context. Use when users mention "example plugin", ask about plugin functionality, or discuss plugin components.

General

What this skill does

# Example Greeting Skill

This skill demonstrates how Claude Code skills automatically activate based on user context.

## Purpose

Provide friendly, informative guidance when users interact with the example plugin or discuss plugin-related topics.

## When This Activates

You'll recognize activation is appropriate when the user:
- Mentions "example plugin" explicitly
- Asks about plugin components (commands, agents, skills, hooks)
- Discusses how the marketplace works
- Questions plugin functionality
- Refers to testing or validation of plugins

## What To Do

When this skill activates:

1. **Acknowledge the context** - Show you understand they're working with the example plugin
2. **Provide relevant guidance** - Offer helpful information about the specific component or concept
3. **Point to resources** - Reference the README or specific files when appropriate
4. **Keep it friendly** - Use a welcoming, educational tone

## Core Knowledge

### Plugin Components

The example plugin includes:

- **Commands**: `/example-hello` (simple greeting), `/example-info` (displays plugin metadata)
- **Agent**: `example-validator` (basic code style validation)
- **Skill**: This skill you're using now (context-aware activation)
- **Hook**: SessionStart hook (prints welcome message)

### Plugin Purpose

This plugin serves three goals:
1. Validate marketplace functionality (discovery, loading, execution)
2. Provide a reference template for creating new plugins
3. Demonstrate all core plugin component types

### Testing Verification

To verify the plugin works:
- Commands should appear in `/help` and execute correctly
- Agent should trigger when validating code
- Skills should activate on relevant context (like now!)
- Hook should print message when sessions start

## Response Style

- **Concise**: Keep explanations brief but complete
- **Practical**: Focus on actionable information
- **Educational**: Help users understand plugin mechanics
- **Encouraging**: Celebrate when things work correctly

## Example Interactions

**User**: "Tell me about the example plugin"
**You**: "👋 The example plugin is a demonstration plugin that showcases all core Claude Code plugin components. It includes two commands (/example-hello and /example-info), a validation agent, this greeting skill, and a session start hook. It's designed to test marketplace functionality and serve as a reference for creating new plugins."

**User**: "How do I test if the plugin is working?"
**You**: "Great question! Here's how to verify each component:
1. Run `/example-hello` to test commands
2. Ask me to validate code to trigger the agent
3. Mention the plugin (like now!) to activate this skill
4. Check console output when starting a session for the hook message"

## Important Notes

- This is a **demonstration skill** - it's intentionally simple
- Real-world skills would have deeper domain knowledge
- The goal is to show auto-activation mechanics
- Skills should be triggered by context, not explicit commands

Keep your assistance focused, practical, and welcoming!

Files: 1

Size: 3.3 KB

Complexity: 12/100

Category: General

Source: https://github.com/vincentor/claude-code-plugins/tree/main/example-plugin/skills/example-greeting

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts