Advisor Capability Preflight
Check and configure documentation capabilities before an ISV Partner Advisor interaction. Use when the advisor starts, when Salesforce Docs MCP or official-documentation access may be missing, when a customer asks to install or approve documentation tools, or when the active harness changes.
Install
/plugin marketplace add forcedotcom/partner-ecosystem-agentic-kitThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add forcedotcom/partner-ecosystem-agentic-kit --skill advisor-capability-preflightgit clone --depth 1 https://github.com/forcedotcom/partner-ecosystem-agentic-kit.git /tmp/partner-ecosystem-agentic-kit
mkdir -p ~/.claude/skills
cp -r /tmp/partner-ecosystem-agentic-kit/skills/advisor-capability-preflight ~/.claude/skills/advisor-capability-preflightPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
Follow the instructions below. Read [this skill's contract](references/skill-contract.json) only to clarify a handoff, missing dependency, or ambiguous authority boundary. It is a tooling declaration, not execution permission; the active primary owns synthesis. # Advisor capability preflight Establish documentation capability without touching a Salesforce org. Keep this setup separate from the partner's advisory decision. Salesforce Docs MCP is optional but highly recommended. Missing or declined MCP access must never block the advisor; continue with the approved fallback and label unsupported current claims as unknown. ## Preflight 1. Read `references/documentation-policy.json`. 2. Inspect only the tools exposed by the current harness. Do not probe an org, Salesforce CLI, credentials, or unrelated MCP servers. 3. Treat Salesforce Docs MCP as connected only when an exposed tool name matches the policy patterns. Never infer connection from a file, product name, or remembered installation. 4. Read `.advisor/capabilities.json` under the explicitly selected project root when available. Reuse choices only for the same harness, project, and policy. Legacy records without project scope need one confirmation, not silent reuse in another project. Recorded preference is not proof of host access. In app sessions without durable project storage, retain the decision only in session context; do not claim it persists into another conversation.
Details
- Skill name
advisor-capability-preflight- Repository
- forcedotcom/partner-ecosystem-agentic-kit
- Path
skills/advisor-capability-preflight/SKILL.md- License
- Apache-2.0
- Repo updated
- 10 November 2026
FAQ
What does the Advisor Capability Preflight skill do?
Check and configure documentation capabilities before an ISV Partner Advisor interaction. Use when the advisor starts, when Salesforce Docs MCP or official-documentation access may be missing, when a customer asks to install or approve documentation tools, or when the active harness changes.
How do I install the Advisor Capability Preflight skill?
Claude Code plugin: /plugin marketplace add forcedotcom/partner-ecosystem-agentic-kit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Advisor Capability Preflight popular?
It lives in forcedotcom/partner-ecosystem-agentic-kit, which has 24 GitHub stars and 1 forks.
Related skills
Agentforce Implementation Advisor
24forcedotcom/partner-ecosystem-agentic-kit
Use for Agentforce agent, topic, action, prompt template, orchestration, state, testing, packaging, scratch-shape, and UX implementation decisions. Owns Agent, topic, action, orchestration, state, testing, and UX implementation decisions.
Data 360 Implementation Advisor
24forcedotcom/partner-ecosystem-agentic-kit
Use for Data 360 architecture, data-kit workflow, scratch entitlement, metadata packageability, activation ordering, and partner-solution integration decisions. Owns Data 360 architecture and implementation patterns that affect partner solutions and packaging.
Development Environment
24forcedotcom/partner-ecosystem-agentic-kit
Route and synthesize decisions about PBO Dev Hubs, namespaces, scratch org shape, persistent development orgs, demos, trials, provisioning, developer access, and environment lifecycle. Use when a partner asks which Salesforce org or environment should perform a development, test, demo, packaging, or customer-validation job.
Coda
33dvcrn/openclaw-skills-marketplace
General-purpose Coda document manager via REST API v1. Supports listing/creating/updating/deleting docs, managing tables/rows/pages, triggering automations, and exploring doc structure. Requires CODA_API_TOKEN environment variable. Delete operations require explicit confirmation; publishing and permission changes require explicit user intent.
Validate Block Markup
23nathanonn/agent-skills
Validate, diagnose, or repair standalone serialized WordPress Gutenberg block markup built from core blocks, using a pinned Node.js runtime. Use when the user explicitly asks to validate, check, lint, or debug block markup or `<!-- wp:... -->` block comments, reports an invalid block, "unexpected or invalid content", or an "Attempt Block Recovery" prompt, or is about to paste markup into the WordPress Code Editor or assign it to post_content. Scope is standalone, cross-site-portable core block markup only; site-specific, theme-specific, dynamic, plugin, and third-party block content are out of
Cold Email Writer
33dvcrn/openclaw-skills-marketplace
Writes personalized cold emails that actually get replies
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.