PranavNagrecha/AwesomeSalesforceSkills / skills/admin/data-cloud-provisioning
data-cloud-provisioning
VerifiedUse when enabling Data Cloud (Data 360) in an org, creating data spaces, assigning permission sets, registering ingestion API sources, or configuring activation targets. Triggers: 'enable data cloud', 'data spaces setup', 'data cloud permission sets', 'ingestion API connected app', 'activation target setup', 'data cloud licensing', 'dedicated home org vs existing org'. NOT for data streams or DLO-to-DMO mapping — use data/data-cloud-data-streams. NOT for identity resolution rulesets — use admin/data-cloud-identity-resolution.
Security report
VerifiedStatic analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.
- Commit
450bcdeaff3e5ce7a86ef4d66129e0e62612b7b3- Content hash
35dbf3d07d693f42587db2f29c2086a4a7f9674ef7928bc84a3acc5eed321147- Scanned
- 2026-11-17
- Scanner version
- skillxone-scan-1.0.0
- Policy version
- 0.1-draft
- Decision
- Every required check completed with no open blocking or medium findings.
- Verification expires
- 2026-12-17
Findings (2 low, 1 info)
- low
INT-MISSING-LICENSENeither the skill nor its repository states a license, so the terms of use are unclear.
Suggested fix: Add a LICENSE file to the repository or a `license` field to SKILL.md.
A link uses unencrypted http:// (soap.sforce.com), so its content can be altered in transit.
SALESFORCE_NS = "http://soap.sforce.com/2006/04/metadata"Suggested fix: Use https://.
The skill ships an executable script. Review it before allowing an agent to run it.
#!/usr/bin/env python3Suggested fix: None required. Informational.
Checks run
- prompt-injection
- dangerous-commands
- credentials
- network
- file-access
- integrity
Checks skipped
- dependencies: No dependency manifest in the skill directory.
- gitleaks: gitleaks is not installed on this host.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |