AF sf-ai-agentforce-observability
Agentforce session tracing extraction and analysis. TRIGGER when: user extracts STDM data from Data Cloud, analyzes agent session traces, debugs agent conversations via telemetry, or works with .parquet files from Agentforce. DO NOT TRIGGER when: testing agents (use sf-ai-agentforce-testing), Apex debug logs (use sf-debug), or building agents (use sf-ai-agentforce).
As a process F 68/100 · Will not run — References files that are not bundled: ../sf-ai-agentforce-testing/SKILL.md, ../sf-debug/SKILL.md, ../sf-ai-agentforce/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/query-patterns.md:769High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)- `{{KNOWLEDGE_ARTICLE_DMO}}`: Your org's Knowledge DMO name (e.g., `Know…dlm`)detector
Files scanned: 36. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../sf-ai-agentforce-testing/SKILL.md - warning
missing-refreference to a missing file: ../sf-debug/SKILL.md - warning
missing-refreference to a missing file: ../sf-ai-agentforce/SKILL.md - warning
missing-refreference to a missing file: ../sf-ai-agentscript/SKILL.md - warning
missing-refreference to a missing file: ../sf-connected-apps/SKILL.md - warning
missing-refreference to a missing file: ../sf-flow/SKILL.md - warning
missing-refreference to a missing file: ../sf-apex/SKILL.md
Process rating: all ten parameters 68/100
- 0Tools and files. 7 referenced file(s) missing: ../sf-ai-agentforce-testing/SKILL.md, ../sf-debug/SKILL.md, ../sf-ai-agentforce/SKILL.md
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 70 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1637 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -37 of 7 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 368: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 70 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (15 of 15)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.