Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By seb-schi
Salesforce demo preparation pipeline — sparring, audit, deployment for SE demo orgs
npx claudepluginhub seb-schi/sf-demo-scout --plugin sf-demo-scoutOrchestrator for SF Demo Prep deployment. Parses a completed spec from /scout-sparring, delegates deployment to Sonnet sub-agents in phases, and writes a consolidated change log. Activate with /scout-building.
One-stop install, refresh, and repair for Scout. Run on first install, after a Scout update, or whenever something feels broken. Idempotent — safe to re-run any time.
Opus sparring partner for Salesforce demo preparation. Handles both new scenario discovery and targeted iterations on existing demos. Produces a structured spec for /scout-building to deploy. Activate with /scout-sparring.
Switch to a different Salesforce demo org.
Canonical deployment rules for Flows, Apex, LWC, Agentforce, Page Layouts, Queues, and Picklists in SF Demo Prep. Pattern-gated 3-attempt rule, known deploy-error patterns, rollback commands, and per-category deployment procedures. TRIGGER when: a phase sub-agent needs deployment rules outside its inlined scope, or needs to verify rollback command syntax. DO NOT TRIGGER when: deploying metadata (phase prompts inline the relevant rules), during sparring, or for permission set generation.
Decision tree for when to consult the Salesforce Docs MCP — YES/NO rules, citation format, and degraded-mode handling. TRIGGER when: deciding whether to call salesforce_docs_search/fetch (sparring Stage 4, building error recovery, sub-agent unfamiliar-error path). DO NOT TRIGGER when: actually executing a docs search (the decision is already made), during audits, or for standard metadata generation.
Format and procedure for auditing a Salesforce demo org — required content, priority flags, and ProfileLayout query patterns. TRIGGER when: audit sub-agents need the canonical output format, section structure, or ★ priority flag rules. DO NOT TRIGGER when: running the audit (sub-agent prompts have inlined procedures), generating specs, or deploying metadata.
Build, modify, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, modifies, or asks about .agent files or aiAuthoringBundle metadata; changes agent behavior, responses, or conversation logic; designs agent actions, tools, subagents, or flow control; writes or reviews an Agent Spec; previews, debugs, deploys, publishes, or tests agents; uses Agent Script CLI commands (sf agent generate/preview/publish/test). DO NOT TRIGGER when: Apex development, Flow building, Prompt Template authoring, Experience Cloud configuration, or general Salesforce CLI tasks unrelated to Agent Script.
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, or field metadata. Also use when users encounter field deployment errors, especially around Roll-up Summary format, Master-Detail constraints, or formula issues. Always use this skill for any custom field metadata work, field generation, or field troubleshooting.
External network access
Connects to servers outside your machine
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Permanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
v9.44.0 — Patch release for cursor-agent smoke checks in untrusted workspaces. Run /octo:setup.
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
A Claude Code plugin for Salesforce Solutions Engineers. Scout audits your demo org, spars with you on the scenario, and deploys the configuration via Headless 360 — so you ship CLI-driven demos this week instead of next quarter.
Full setup guide with videos and screenshots: Demo Scout Canvas (internal Salesforce link)
Inside Claude Code, run these four commands in order:
/plugin marketplace add https://github.com/seb-schi/sf-demo-scout.git
/plugin install sf-demo-scout@scout
/reload-plugins
/scout-setup
When prompted on the install step, select Install for you (user scope).
/scout-setup handles all prerequisites: Homebrew check, Node / Python /
Salesforce CLI install, SFDX scaffold, 16 community skills sync, shell
environment, and Slack MCP registration + auth.
After setup, kick off your first demo with /scout-sparring.
If you installed Scout before 2026-05-23 (via git clone or the curl
bootstrap), run the migration trampoline one last time:
cd ~/claude-projects/sf-demo-scout
bash update.sh
This opens a fresh Claude Code window and walks you through the plugin
install — same four commands as above, plus a finishing
/setup-demo-scout step that migrates your workspace in place. Your
org data at ~/claude-projects/sf-demo-scout/orgs/ is preserved.
After today, you never run update.sh again — Claude Code pulls plugin
updates automatically in the background.
Updates are automatic. Claude Code pulls new plugin versions on session
startup; if an update is downloaded but not yet installed, you'll see a
one-line banner suggesting /scout-setup to finish. To trigger
manually: /plugin marketplace update scout.
The full clone-install history is preserved at branch
archive/clone-install-final and tag v-clone-install-final.
Ping #sf-demo-scout on Slack.