From vanguard-frontier-agentic
Creates a structured, auditable handoff capsule when a Salesforce specialist agent transfers a matter to another agent, preserving context, risk labels, privilege posture, and privacy labels.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vanguard-frontier-agentic:salesforce-case-capsuleThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill defines the **salesforce-case-capsule** — the single structured
This skill defines the salesforce-case-capsule — the single structured record that Salesforce specialist agents exchange when a matter crosses an agent boundary. The capsule exists so that no agent works in a silo, no context is lost in a handoff, and every cross-domain exchange is auditable. It is a data contract, not a decision: a capsule never approves, denies, or directs an action. It carries facts, uncertainty, risk posture, and an explicit decision owner.
salesforce-routing-protocol.salesforce-live-change-approval-protocol.salesforce-data-exposure-escalation-protocol.decision_owner (an accountable human)
and exactly one primary_agent.do_not_do_list. An empty list is not acceptable;
if nothing is prohibited, the capsule is not ready to send.privilege_sensitivity and privacy_sensitivity.assumptions, inferences, and
missing_evidence are mandatory fields, not optional.risk_rating uses risk language only.escalation_required: true and
recommended_next_action to a pause-and-escalate posture unless documented
controls already exist.matter_id — unique identifier (generated, never a real org ID)matter_type — from salesforce-risk-taxonomy matter type listsource_agent — agent or human invoker creating the capsulereceiving_agent — primary receiving agentsecondary_agents — list of parallel-review agents if anyprimary_agent — agent with primary accountabilitydecision_owner — named accountable humanorg_environment_type — sandbox / scratch / staging / production (placeholder, not real ID)business_unit — redacted business unit referencetimeline — relevant dates and deadlines (no PII)facts — confirmed facts from sanitized inputsassumptions — inferences the agent made without direct evidenceinferences — derived conclusions labeled as suchmissing_evidence — what is unknown and neededevidence_quality — High / Medium / Low / Insufficientrisk_rating — Critical / High / Medium / Low / Unknown per salesforce-risk-taxonomymatter_type_flags — relevant escalation gates from salesforce-risk-taxonomyprivilege_sensitivity — None / Advisory / Legal-Privilegeprivacy_sensitivity — None / Internal / PII / Regulated-Datadata_exposure_risk — boolean + description if trueguest_user_risk — booleanautonomous_ai_risk — booleanfinance_revenue_risk — booleanirreversible_change_risk — booleanhuman_approval_required — booleanescalation_required — booleanescalation_gate_fired — name of gate from salesforce-risk-taxonomy or nullrecommended_next_action — pause-and-escalate / proceed-with-approval / proceed-with-review / blockeddo_not_do_list — explicit list of actions the receiving agent must not takeopen_questions — questions that must be answered before the matter can proceedblockers — conditions that prevent forward progressapproval_state — draft / pending-human-review / approved / rejectedaudit_log_summary — one-line summary of routing decision and rationaleProduce a structured capsule with all fields from the field set above.
Label each section clearly. Every assumptions entry must state its basis.
Every do_not_do_list entry must state the reason.
[ORG-ID], [USER-ID]) before including in capsule.npx claudepluginhub raishin/vanguard-frontier-agentic --plugin vanguard-frontier-agenticClassifies and routes Salesforce matters to specialist agents, handles cross-domain overlap, and resolves agent conflicts. Use when a Salesforce issue needs triage or parallel review.
Create structured handoff documents between GTM functions — sales-to-CS, SDR-to-AE, AE-to-SE, sales-to-implementation. Captures deal context, customer expectations, success criteria, risk flags, and action items so nothing falls through the cracks. Use this skill whenever a deal is closing and needs to transition to CS or implementation, when an SDR qualifies a lead for an AE, when a rep needs SE support, or when someone says "hand off this deal", "create a CS transition doc", "pass this lead to [rep]", "implementation kickoff", or when building handoff templates for the team.
Implements Salesforce patterns for PII classification, GDPR/CCPA compliance via Individual object, consent tracking, data retention, and Shield field-level encryption.