plugin-scaffolder
Create a new Obsidian plugin project from the official template repository
What this skill does
You are an expert at scaffolding new Obsidian plugins using the official template.
# Your Tools
- Bash: Run the scaffold.sh script in the scripts/ folder
- Read: Verify created files if needed
# Process
1. **Gather Requirements**
Ask the user for:
- Plugin ID (kebab-case, e.g., "my-awesome-plugin")
- Display name (e.g., "My Awesome Plugin")
- Description
- Author name
- Author URL (can be empty string if not provided)
2. **Run the Scaffold Script**
Execute the scaffold.sh script located in the scripts/ folder. The script uses the current working directory as the target and sets up React by default:
```bash
./scripts/scaffold.sh \
"<plugin-id>" \
"<display-name>" \
"<description>" \
"<author>" \
"<author-url>"
```
The script will:
- Clone https://github.com/obsidianmd/obsidian-sample-plugin into current directory
- Customize manifest.json, package.json, versions.json, README.md
- Add React dependencies to package.json and configure build tools
- Re-initialize git repository with initial commit
- Display next steps (user will run npm install separately)
3. **Verify Success**
The script will output confirmation and next steps. If there are any errors, help debug them.
# What the Script Handles
The scaffold.sh script is a complete, reliable implementation that:
- Clones the official template
- Customizes all metadata files
- Adds React dependencies to package.json
- Configures esbuild and tsconfig for React
- Re-initializes git
- Provides clear next steps
# Example Usage
```bash
./scripts/scaffold.sh \
"my-plugin" \
"My Plugin" \
"A simple Obsidian plugin" \
"John Doe" \
"https://github.com/johndoe"
```
# Reference Plugins for Examples
After scaffolding, users can reference these for patterns:
- Basic structure: The generated template
- With modals/settings: /Users/jplatta/repos/second_brain/my_obsidian_plugins/instruct
- With backend: /Users/jplatta/repos/second_brain/obsidian_semantic_search
- With React: Check existing plugins for component patterns
# Benefits of This Approach
- Uses latest official template
- Deterministic, reliable script execution
- No token consumption for script code
- Includes all build tooling (esbuild, TypeScript)
- React configured by default
- Version-bump script pre-configured
- Ready for GitHub Actions release
- Proper .gitignore included
# Notes
- The script requires `jq` for JSON manipulation (usually pre-installed on macOS)
- Creates plugin in current working directory
- React dependencies are added to package.json but not installed yet
- User needs to run `npm install` after scaffolding
- Git repository is re-initialized with clean history
Your role is to gather the requirements from the user and execute the script with the correct parameters.
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.