sshvarzman-salesforce/claude-skills

sf-agent-api-review

Review rubric for Agentforce Agent API integrations.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/sshvarzman-salesforce/claude-skills --skill sf-agent-api-review

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Agent API Integration Review

Use This Skill When

  • Reviewing an Agent API integration before it ships.
  • Auditing an existing client for security, correctness, and resilience gaps.
  • Producing a prioritized risk list for an Agentforce headless/chat integration.

Review Checklist

Authentication and secrets

  • [ ] Consumer secret and token are server-side only; not in the browser or source control.
  • [ ] Token refresh handled (proactive + on 401); no static/pasted tokens.
  • [ ] ECA uses client credentials flow with the required scopes (api, refresh_token/offline_access, chatbot_api, sfap_api).
  • [ ] Run As user has appropriate (least-privilege) access; bypassUser chosen deliberately.

Endpoints and environment

  • [ ] instanceConfig.endpoint uses the My Domain URL, not the Lightning URL.
  • [ ] Correct base host (api.salesforce.com, or api.gov.salesforce.com for Government Cloud).
  • [ ] Agent is not type "Agentforce (Default)".

Session hygiene

  • [ ] externalSessionKey is unique per conversation and logged for tracing.
  • [ ] sessionId tracked; sessions explicitly ended (DELETE) with a sensible x-session-end-reason.
  • [ ] Abandoned sessions are reaped; not relying solely on timeout.

Turn correctness and concurrency

  • [ ] sequenceId increments monotonically per session.
  • [ ] Exactly one request in flight per session (guards against 423).
  • [ ] Turns serialized/queued client-side.

Messaging and streaming

  • [ ] Sync vs streaming choice matches the surface.
  • [ ] SSE parser buffers partial frames and splits on event boundaries.
  • [ ] All streaming events handled: ProgressIndicator, TextChunk, Inform, EndOfTurn, ValidationFailureChunk.
  • [ ] On ValidationFailureChunk, rendered chunks are cleared.
  • [ ] Inform treated as authoritative full text.

Variables

  • [ ] API-settable variables are external + "Allow value to be set by API".
  • [ ] __c suffix stripped; $Context. prefix used correctly.
  • [ ] Read-only/context variables not mutated post-start (except $Context.EndUserLanguage).
  • [ ] Variable values validated before downstream use (SOQL/HTML/callouts).

Citations

  • [ ] citedReferences empty-guarded; inlineMetadata optional-handled.
  • [ ] Inline markers inserted by location from highest offset backward.
  • [ ] Cited URLs validated; internal records navigated via recordId.

Error handling and resilience

  • [ ] 400/401/404/423/500 mapped to specific handling.
  • [ ] 120s timeout handled with client timeout + user-facing fallback.
  • [ ] Transient vs deterministic failures distinguished for retry.
  • [ ] traceId, sessionId, status logged on every failure.

Trust, safety, and billing

  • [ ] Agent text treated as untrusted output (sanitized before render).
  • [ ] isContentSafe respected.
  • [ ] Credit/billing impact understood; agent-to-agent chains budgeted.
  • [ ] Feedback capture wired (feedbackId → feedback endpoint) where useful.

Output Format

Report findings as:

  • 🔴 Critical: security/correctness must-fix before ship (e.g., secret in browser, no concurrency guard).
  • 🟡 Suggestion: resilience/quality improvement (e.g., add token pre-refresh).
  • 🟢 Nice to have: polish (e.g., inline citation rendering).

Close with the top 3 risks and concrete mitigations.

Deliverables

  • Completed checklist with pass/fail per item.
  • Prioritized findings (Critical / Suggestion / Nice to have).
  • Top 3 risks and mitigations.

Additional Resources

  • Domain skills for each area: sf-agent-api-setup, sf-agent-api-session-lifecycle, sf-agent-api-messaging, sf-agent-api-variables, sf-agent-api-citations, sf-agent-api-integration-patterns, sf-agent-api-troubleshooting
  • Official docs: Agent API Developer Guide

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
sshvarzman-salesforce
Comunidad

activating-datacloud

Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use segmenting-datacloud), data retrieval/search work (use retrieving-datacloud), or STDM/session tracing (use observing-agentforce).

instalaciones
1
GitHub Stars
0
Actualizado
15 oct
sshvarzman-salesforce
Comunidad

agentforce-skills-research

Research Agentforce configuration patterns — topics, actions, instructions, CLTs, knowledge, planner behavior. Searches Salesforce docs, Trailhead, internal repos (git.soma), Slack channels, and Google Docs to find working examples, known issues, and best practices.

instalaciones
1
GitHub Stars
0
Actualizado
15 oct
sshvarzman-salesforce
Comunidad

harmonizing-datacloud

Salesforce Data Cloud Harmonize phase. Use this skill when the user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. TRIGGER when: user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. DO NOT TRIGGER when: the task is only about streams/DLOs (use preparing-datacloud), segments/insights (use segmenting-datacloud), retrieval/search (use retrieving-datacloud), or STDM/sessio

instalaciones
1
GitHub Stars
0
Actualizado
15 oct
sshvarzman-salesforce
Comunidad

preparing-datacloud

Salesforce Data Cloud Prepare phase. Use this skill when the user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use connecting-datacloud), DMOs and identity resolution (use harmonizing-datacloud), or query/search work (use retrieving-datacloud)

instalaciones
1
GitHub Stars
0
Actualizado
15 oct