@salesforce/afv-skills 1.37.0 → 1.39.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.37.0",
+  "version": "1.39.0",
   "description": "Salesforce skills for Agentforce Vibes",
   "license": "CC-BY-NC-4.0",
   "files": [

package/skills/agentforce-d360-analyze/README.md

@@ -50,7 +50,7 @@ See `SKILL.md` for the full TRIGGER conditions, flag table, and the "DC-only bli
 
 Three stages, each independently runnable:
 
-```
+```text
 fetch_dc.py     →  24 dc.<name>.json + dc._session_manifest.json   (DC Query REST waterfall)
 assemble_dc.py  →  dc._session_tree.json                           (in-memory hierarchical join)
 render_dc.py    →  dc._session_summary.md                          (markdown rendering)
@@ -87,7 +87,7 @@ For design-time architecture questions (topic/action tree, flow inventory, Apex
 
 ## Layout
 
-```
+```text
 agentforce-d360-analyze/
 ├── SKILL.md                               ← runtime-parsed entry point (TRIGGER / DO NOT TRIGGER, flags, prompts)
 ├── README.md                              ← this file

package/skills/agentforce-d360-analyze/SKILL.md

@@ -2,15 +2,15 @@
 name: agentforce-d360-analyze
 description: "Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud."
 metadata:
+  version: "1.0"
+  minApiVersion: "66.0"
+  relatedSkills:
+    - "agentforce-architecture-analyze"
   cliTools:
     - tool: ["python3"]
       semver: ">=3.10.0"
     - tool: ["sf"]
       semver: ">=2.0.0"
-  relatedSkills:
-    - "agentforce-architecture-analyze"
-  version: "1.0"
-  minApiVersion: "66.0"
 ---
 
 # agentforce-d360-analyze — Data Cloud 360° session view
@@ -72,7 +72,7 @@ python3 "$prefix/discover_sessions.py" --org <alias> [filters...]
 
 ## Pipeline — three stages
 
-```
+```text
 fetch_dc.py     →  24 dc.<name>.json + dc._session_manifest.json     (DC Query REST waterfall, 5 waves)
 assemble_dc.py  →  dc._session_tree.json                             (pure in-memory hierarchical join)
 render_dc.py    →  dc._session_summary.md                            (human summary, multi-section)
@@ -92,7 +92,7 @@ Flags: `--verbose` for per-DMO row counts; `--no-assemble` / `--no-render` to st
 
 Everything lands under `~/.vibe/data/agentforce-d360-analyze/<org_id15>/<agent>__<ver>/<session_id>/` (default; override with `--data-dir <path>`):
 
-```
+```text
 dc.sessions.json              dc.steps.json                dc.gateway_requests.json
 dc.interactions.json          dc.messages.json             dc.gateway_responses.json
 dc.participants.json          dc.generations.json          dc.gateway_request_llm.json

package/skills/agentforce-d360-analyze/references/artifacts.md

@@ -5,7 +5,7 @@ Every successful trace lands artifacts under
 Re-running the same `(org, sid)` overwrites in place. Listed below in
 the order they're produced.
 
-```
+```text
 ~/.vibe/data/agentforce-d360-analyze/<org_id15>/<agent>__<ver>/<sid>/
 ├── dc._session_manifest.json ← per-query counts + session_shape + empties
 ├── dc._session_tree.json ← hierarchical join (primary artifact)

package/skills/agentforce-d360-analyze/references/dc_dmo_fields.md

@@ -59,7 +59,7 @@ Per-run row counts, empty reasons, and join paths are recorded in
 Legend: ★ = session-FK direct (one hop) ▸ = polymorphic `parent__c`
  ⚠ = requires feature provisioning
 
-```
+```text
 Session (ssot__AIAgentSession__dlm, PK ssot__Id__c)
  │
  ├── ★ Participant (ssot__AiAgentSessionId__c)
@@ -135,7 +135,7 @@ All 24 entries below are in the `scripts/fetch_dc.py` waterfall — the
 join expressions are exactly what the script runs, and each one has a
 `.sql` template under `assets/dc/`.
 
-```
+```text
  1. sessions WHERE ssot__Id__c = {sid}
  2. interactions WHERE ssot__AiAgentSessionId__c = {sid}
  3. messages WHERE ssot__AiAgentSessionId__c = {sid}
@@ -370,7 +370,7 @@ schemas are documented in the per-DMO sections below.
 `turnId__c` column (verified via live `describe`; 11 fields total,
 none reference session/trace/turn). The canonical join path is:
 
-```
+```text
 Session → Interaction → Step (.ssot__GenerationId__c) → Generation (.generationId__c)
 ```
 
@@ -432,7 +432,7 @@ Richer than `GenAIGeneration` — carries prompt text, tokens, model, and
 session/user/bot identifiers. **Forward entry point for the entire audit
 chain**, reached from Session via `sessionId__c`:
 
-```
+```text
 Session.ssot__Id__c → GatewayRequest.sessionId__c LIKE '%<sid>%'
 ```
 

package/skills/agentforce-d360-analyze/references/dc_pipeline_contract.md

@@ -3,7 +3,7 @@
 The DC pipeline for a single Agentforce session runs as three stages in
 sequence:
 
-```
+```text
 fetch_dc.py → 24 dc.<name>.json artifacts + dc._session_manifest.json
 assemble_dc.py → dc._session_tree.json (pure in-memory join)
 render_dc.py → dc._session_summary.md (pure tree reader)
@@ -71,7 +71,7 @@ Per-field schema for every DMO lives in
 The "normal" path that nests a `GatewayRequest` under its owning
 `LLM_STEP` in the tree. Every edge is a platform-sanctioned forward FK:
 
-```
+```text
 Step.ssot__GenerationId__c → Generation.generationId__c
 Generation.generationResponseId__c → GatewayResponse.generationResponseId__c
 GatewayResponse.generationRequestId__c → GatewayRequest.gatewayRequestId__c

package/skills/agentforce-generate/README.md

@@ -10,6 +10,7 @@ The skill routes agent work across the full lifecycle:
 |--------|----------------|
 | Create an Agent | Agent Spec design, environment checks, bundle generation, draft authoring |
 | Modify an Agent | Subagent/action changes, instruction refinement, flow updates |
+| Audit and Repair | Health checks, common-pitfall review, minimal evidence-backed repairs |
 | Diagnose Compilation Errors | Error capture, classification, targeted fixes |
 | Diagnose Behavioral Issues | Trace-based debugging, routing/action analysis |
 | Deploy / Release | Draft iteration, deploy, explicit publish + activate |
@@ -26,6 +27,7 @@ agentforce-generate/
 │   ├── agent-design-and-spec-creation.md
 │   ├── architecture-patterns.md
 │   ├── agent-script-core-language.md
+│   ├── agent-audit-and-repair.md
 │   ├── salesforce-cli-for-agents.md
 │   ├── agent-validation-and-debugging.md
 │   ├── deploy-reference.md
@@ -47,8 +49,8 @@ agentforce-generate/
 Core rules include:
 
 1. **Always `--json`** on every `sf` CLI command
-2. **Diagnose before you fix** — preview with live actions and read traces before modifying code
-3. **Spec approval is a hard gate** — never proceed past Agent Spec creation without user approval
+2. **Use proportionate evidence** — compile local syntax changes; use preview and traces for behavior; use live actions only with approval in a safe org
+3. **Use a proportionate spec gate** — require approval for greenfield and material design changes, not every one-line repair
 4. **Draft-first lifecycle** — iterate in draft by default; publish/activate only with explicit user confirmation
 
 ## Prerequisites
@@ -75,6 +77,20 @@ your-project/
 
 Restart Claude Code after installation.
 
+The skill can install its local AgentScript compiler on first use. It uses a
+skill-owned user cache and does not add dependencies to the customer's project:
+
+```bash
+node .claude/skills/agentforce-generate/scripts/setup-agentscript-sdk.mjs \
+  --npm --json
+```
+
+Claude should run this automatically for every existing `.agent` file before
+org-side validation. If npm setup fails, the skill can build the public
+`salesforce/agentscript` source checkout. If neither provider works, the skill
+continues with target-org validation or a clearly labeled static review and
+states that the compiler was not used.
+
 ## Key References
 
 - Pattern selection: [references/patterns-by-requirement.md](references/patterns-by-requirement.md)
@@ -82,12 +98,13 @@ Restart Claude Code after installation.
 - Design/spec workflow: [references/agent-design-and-spec-creation.md](references/agent-design-and-spec-creation.md)
 - Architecture mechanics: [references/architecture-patterns.md](references/architecture-patterns.md)
 - Core language: [references/agent-script-core-language.md](references/agent-script-core-language.md)
+- Audit and repair: [references/agent-audit-and-repair.md](references/agent-audit-and-repair.md)
 - Validation/debugging: [references/agent-validation-and-debugging.md](references/agent-validation-and-debugging.md)
 - Reference index and consolidation notes: [references/reference-map.md](references/reference-map.md)
 
 ## Version
 
-Current version: **0.6.1** (2026-05-20). See [references/version-history.md](references/version-history.md) for the full changelog.
+Current version: **0.11**. See [references/version-history.md](references/version-history.md) for the full changelog.
 
 ## Credits