plugin-settings
Guide for implementing user-configurable plugin settings with .local.md files. Use when the user asks about ".local.md", "plugin settings", "configuration file", "temporarily active hooks", or "user configuration".
What this skill does
# Plugin Settings
User-configurable plugin settings use `.local.md` files that combine YAML frontmatter with markdown documentation.
## File Location
```
my-plugin/
├── .local.md # User's local config (gitignored)
├── .local.example.md # Template for users to copy
└── ...
```
## .local.md Format
```yaml
---
api_key: ${MY_API_KEY}
theme: dark
auto_format: true
excluded_paths:
- node_modules
- dist
---
# My Plugin Settings
Custom notes or documentation (for human reference only).
```
## Reading Configuration
### In Hook Scripts
Parse the YAML frontmatter from `.local.md`. Locate the file using `CLAUDE_PLUGIN_ROOT`:
```javascript
const pluginRoot = process.env.CLAUDE_PLUGIN_ROOT || __dirname.replace('/hooks', '');
const configPath = path.join(pluginRoot, '.local.md');
```
Environment variable substitution: replace `${VAR}` patterns with `process.env[name]`.
### In Skills
```markdown
Read the user's configuration from `.local.md` in the plugin root
to determine their preferences before proceeding.
```
## Temporarily Active Hooks
Configuration can enable/disable hooks dynamically:
```yaml
---
hooks:
format_on_save: true
lint_on_commit: false
---
```
```javascript
// In hook script — check if enabled
const config = parseLocalMd(configPath);
if (!config.hooks?.format_on_save) {
process.exit(0); // Skip hook
}
```
## Template Pattern (.local.example.md)
Provide a template users copy to `.local.md`:
```yaml
---
# Copy this file to .local.md and customize
# API Configuration
api_key: ${MY_API_KEY} # Set MY_API_KEY environment variable
# Behavior Settings
auto_format: true # Format files on save
verbose: false # Enable debug output
---
# Configuration Guide
1. Copy this file to `.local.md`
2. Set required environment variables
3. Customize settings as needed
```
## Gitignore
Always gitignore user config files:
```gitignore
# User configuration (may contain secrets)
.local.md
```
## Validation
Validate configuration in a SessionStart hook — warn on missing required fields but don't block (`process.exit(0)`).
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.