← ClaudeAtlas

salesforce-inspectionlisted

Establish actual deployed Salesforce state through safe, least-privilege, read-only inspection. Use when NorthstarIQ work depends on org reality that source alone cannot settle — whether metadata is really deployed, what value currently governs a rule, which records meet an assessment condition, whether source-controlled intent and the deployed org have drifted, or what evidence actually supports a finding. Read-only throughout; every mutation, deployment, data load, permission change and authentication remains gated.
Shantydotcom/northstariq-revenue-operations-intelligence · ★ 0 · AI & Automation · score 60
Install: claude install-skill Shantydotcom/northstariq-revenue-operations-intelligence
# Salesforce Read-Only Inspection Answers questions about **what the org actually contains right now**, with evidence, and without changing anything. Governance comes from `~/.claude/CLAUDE.md` and the repository `CLAUDE.md`; both apply throughout and are not restated here. What follows is procedure. ## When to run it Run it when the task depends on deployed Salesforce state that source cannot reliably settle: whether metadata is actually deployed · the current state of a field or configuration · how deployed automation is configured · the value a governed configuration record currently holds · the record population relevant to an assessment · whether source-controlled intent and deployed reality have diverged · the evidence behind a finding · behaviour needed for a diagnosis · whether an implementation assumption holds in the connected org. **Read-only inspection is Tier 0.** It changes nothing, needs no business authority and no approval. Do not turn it into a heavyweight workflow. **Do not run it** when the question is already answered authoritatively by repository source, by evidence the current task has already produced, by recorded executed evidence, or by another governing source. > Inspect Salesforce when **deployed reality matters** — not because Salesforce exists. ## Access rule > **Existing authenticated, least-privilege, read-only access may be used without additional task > authorisation** where repository policy permits. Reading is not mutating, and no