Sf Data
Jaganpro/sf-skills
Salesforce data operations with 130-point scoring. An agent skill from Jaganpro/sf-skills.
Salesforce data operations with 130-point scoring. An agent skill from forcedotcom/sf-skills.
Install Platform Data Manage
$ npx skills add forcedotcom/sf-skills --skill platform-data-manage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills platform-data-manage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/platform-data-manage .claude/skills/platform-data-manage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "platform-data-manage" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-data-manage into .claude/skills/platform-data-manage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-data-manage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-data-manageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add forcedotcom/sf-skills --skill platform-data-manage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills platform-data-manage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/platform-data-manage .agents/skills/platform-data-manage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "platform-data-manage" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-data-manage into .agents/skills/platform-data-manage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-data-manage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill platform-data-manage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills platform-data-manage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/platform-data-manage .cursor/skills/platform-data-manage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "platform-data-manage" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-data-manage into .cursor/skills/platform-data-manage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-data-manage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/platform-data-manage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add forcedotcom/sf-skills --skill platform-data-manage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills platform-data-manage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/platform-data-manage .gemini/skills/platform-data-manage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "platform-data-manage" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-data-manage into .gemini/skills/platform-data-manage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-data-manage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install forcedotcom/sf-skills platform-data-manageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add forcedotcom/sf-skills --skill platform-data-manage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/platform-data-manage .github/skills/platform-data-manage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "platform-data-manage" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-data-manage into .github/skills/platform-data-manage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-data-manage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill platform-data-manage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install forcedotcom/sf-skills platform-data-manage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/platform-data-manage .opencode/skills/platform-data-manage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "platform-data-manage" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-data-manage into .opencode/skills/platform-data-manage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-data-manage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
platform-data-manage- GitHub stars
- 1.1k
- Token cost
- ~2.7k tokens
- SKILL.md length
- 930 words
- Files
- 52 (incl. scripts, references, assets)
- Skills in repo
- 251
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Salesforce data operations with 130-point scoring. An agent skill from forcedotcom/sf-skills.
- Works in 7 steps: Verify prerequisites → Run describe-first pre-flight validation… → Choose the smallest correct mechanism → …
- Bulk import/export
- SKILL.md covers When This Skill Owns the Task, Important Mode Decision, Required Context to Gather First and Core Operating Rules, plus 7 more sections
- Calls sf; needs INVALID_CROSS_REFERENCE_KEY
What it does
Platform Data Manage is an agent skill from forcedotcom/sf-skills. Salesforce data operations with 130-point scoring. Use to create, update, delete, bulk import/export, generate test data, and clean up org records via sf CLI and anonymous Apex. TRIGGER on creating test data, bulk import/export, sf data CLI commands, data-factory patterns for Apex tests, or seeding/cleaning org records. DO NOT TRIGGER for SOQL query writing only (use platform-soql-query), Apex test execution (use platform-apex-test-run), or metadata deployment (use platform-metadata-deploy).
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 56 other files, including scripts, reference files and assets (for example `README.md`).
It sits in Testing & QA, covering Test data and fixtures, CRM management and Test generation. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.
When your agent uses it
- Bulk import/export
- Generate test data
- Clean up org records via sf CLI and anonymous Apex
- Creating test data
Example prompts
- “/platform-data-manage”
Requirements
- A credential in INVALID_CROSS_REFERENCE_KEY
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
sf
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
INVALID_CROSS_REFERENCE_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Platform Data Manage loads about 2.7k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 129 tokens; SKILL.md has 930 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 930 words, ~2,692 tokens.
Download SKILL.mdSave it as
.claude/skills/platform-data-manage/SKILL.md (or your agent's skills folder). This skill also uses 51 other files; get the full folder from GitHub.- name
- platform-data-manage
- description
- Salesforce data operations with 130-point scoring. Use to create, update, delete, bulk import/export, generate test data, and clean up org records via sf CLI and anonymous Apex. TRIGGER on creating test data, bulk import/export, sf data CLI commands, data-factory patterns for Apex tests, or seeding/cleaning org records. DO NOT TRIGGER for SOQL query writing only (use platform-soql-query), Apex test execution (use platform-apex-test-run), or metadata deployment (use platform-metadata-deploy).
- metadata.version
- 1.1
- metadata.domains
- Platform
- metadata.relatedSkills
- automation-flow-generate, platform-apex-generate, platform-apex-test-run, platform-custom-field-generate, platform-custom-object-generate…
Salesforce Data Operations Expert (platform-data-manage)
Use this skill when the user needs Salesforce data work: record CRUD, bulk import/export, test data generation, cleanup scripts, or data factory patterns for validating Apex, Flow, or integration behavior.
When This Skill Owns the Task
Use platform-data-manage when the work involves:
sf dataCLI commands- record creation, update, delete, upsert, export, or tree import/export
- realistic test data generation
- bulk data operations and cleanup
- Apex anonymous scripts for data seeding / rollback
Delegate elsewhere when the user is:
- writing SOQL only → platform-soql-query
- running or repairing Apex tests → platform-apex-test-run
- deploying metadata first → platform-metadata-deploy
- creating or modifying custom objects / fields → platform-custom-object-generate or platform-custom-field-generate
Important Mode Decision
Confirm which mode the user wants:
| Mode | Use when |
|---|---|
| Script generation | they want reusable .apex, CSV, or JSON assets without touching an org yet |
| Remote execution | they want records created / changed in a real org now |
Do not assume remote execution if the user may only want scripts.
Required Context to Gather First
Ask for or infer:
- target object(s)
- org alias, if remote execution is required
- operation type: query, create, update, delete, upsert, import, export, cleanup
- expected volume
- whether this is test data, migration data, or one-off troubleshooting data
- any parent-child relationships that must exist first
Core Operating Rules
platform-data-manageacts on remote org data unless the user explicitly wants local script generation.- Objects and fields must already exist before data creation.
- For automation testing, prefer 251+ records when bulk behavior matters.
- Plan cleanup before creating large or noisy datasets — untracked records accumulate across runs and pollute org state.
- Use synthetic, non-identifying data in test records — real PII creates compliance risk and cannot be safely removed after bulk import.
- Prefer CLI-first for straightforward CRUD; use anonymous Apex when the operation truly needs server-side orchestration.
If metadata is missing, stop and hand off to:
- platform-custom-object-generate or platform-custom-field-generate to create the missing schema, then platform-metadata-deploy to deploy it before retrying the data operation
Recommended Workflow
1. Verify prerequisites
Confirm object / field availability, org auth, and required parent records.
2. Run describe-first pre-flight validation when schema is uncertain
Before creating or updating records, use object describe data to validate:
- required fields
- createable vs non-createable fields
- picklist values
- relationship fields and parent requirements
See references/sf-cli-data-commands.md for the sf sobject describe command and jq filter patterns for inspecting fields, picklist values, and createable constraints.
3. Choose the smallest correct mechanism
| Need | Default approach |
|---|---|
| small one-off CRUD | sf data single-record commands |
| large import/export | Bulk API 2.0 via sf data ... bulk |
| parent-child seed set | tree import/export |
| reusable test dataset | factory / anonymous Apex script |
| reversible experiment | cleanup script or savepoint-based approach |
4. Execute or generate assets
Use the built-in templates under assets/ when they fit:
assets/factories/assets/bulk/assets/cleanup/assets/soql/assets/csv/assets/json/
5. Verify results
Check counts, relationships, and record IDs after creation or update.
6. Apply a bounded retry strategy
If creation fails:
- try the primary CLI shape once
- retry once with corrected parameters
- re-run describe / validate assumptions
- pivot to a different mechanism or provide a manual workaround
Do not repeat the same failing command indefinitely.
7. Leave cleanup guidance
Provide exact cleanup commands or rollback assets whenever data was created.
High-Signal Rules
Bulk safety
- use bulk operations for large volumes
- test automation-sensitive behavior with 251+ records where appropriate
- avoid one-record-at-a-time patterns for bulk scenarios
Show full SKILL.md (381 more words)Show less
Data integrity
- include required fields
- validate picklist values before creation
- verify parent IDs and relationship integrity
- account for validation rules and duplicate constraints
- exclude non-createable fields from input payloads
Cleanup discipline
Prefer one of:
- delete-by-ID
- delete-by-pattern
- delete-by-created-date window
- rollback / savepoint patterns for script-based test runs
Common Failure Patterns
| Error | Likely cause | Default fix direction |
|---|---|---|
INVALID_FIELD | wrong field API name or FLS issue | verify schema and access |
REQUIRED_FIELD_MISSING | mandatory field omitted | include required values from describe data |
INVALID_CROSS_REFERENCE_KEY | bad parent ID | create / verify parent first |
FIELD_CUSTOM_VALIDATION_EXCEPTION | validation rule blocked the record | use valid test data or adjust setup |
| invalid picklist value | guessed value instead of describe-backed value | inspect picklist values first |
| non-writeable field error | field is not createable / updateable | remove it from the payload |
| bulk limits / timeouts | wrong tool for the volume | switch to bulk / staged import |
Output Format
When finishing, report in this order:
- Operation performed
- Objects and counts
- Target org or local artifact path
- Record IDs / output files
- Verification result
- Cleanup instructions
Suggested shape:
Data operation: <create / update / delete / export / seed>
Objects: <object + counts>
Target: <org alias or local path>
Artifacts: <record ids / csv / apex / json files>
Verification: <passed / partial / failed>
Cleanup: <exact delete or rollback guidance>Cross-Skill Integration
| Need | Delegate to | Reason |
|---|---|---|
| create missing custom objects | platform-custom-object-generate | schema must exist before data operations |
| create missing custom fields | platform-custom-field-generate | field-level schema must exist before data creation |
| run bulk-sensitive Apex validation | platform-apex-test-run | test execution and coverage |
| deploy missing schema first | platform-metadata-deploy | metadata readiness |
| implement production Apex logic consuming the data | platform-apex-generate | Apex class / trigger authoring |
| implement Flow logic consuming the data | automation-flow-generate | Flow authoring and automation |
Reference Map
Start here
- references/sf-cli-data-commands.md
- references/test-data-best-practices.md
- references/orchestration.md
- references/test-data-patterns.md
- references/test-data-factory-usage.md
Query / bulk / cleanup
- references/soql-relationship-guide.md
- references/relationship-query-examples.md
- references/bulk-operations-guide.md
- references/cleanup-rollback-guide.md
- references/cleanup-rollback-example.md
Examples / limits
- references/crud-workflow-example.md
- references/bulk-testing-example.md
- references/anonymous-apex-guide.md
- references/governor-limits-reference.md
Validation scripts
- scripts/soql_validator.py — validate SOQL queries before execution
- scripts/validate_data_operation.py — pre-flight check for data operations (required fields, picklist values, createable fields)
Asset templates
assets/factories/— Apex test data factory scripts (account, contact, opportunity, lead, user, etc.)assets/bulk/— Bulk API 2.0 Apex templates (insert 200, 500, 10000 records; upsert by external ID)assets/cleanup/— Cleanup and rollback scripts (delete by name, date, pattern; transaction rollback)assets/soql/— SOQL query templates (aggregate, subquery, parent-to-child, child-to-parent, polymorphic)assets/csv/— CSV import templates for Account, Contact, Opportunity, custom objectsassets/json/— JSON tree import templates (account-contact, account-opportunity, full hierarchy)
Score Guide
| Score | Meaning |
|---|---|
| 117+ | strong production-safe data workflow |
| 104–116 | good operation with minor improvements possible |
| 91–103 | acceptable but review advised |
| 78–90 | partial / risky patterns present |
| < 78 | blocked until corrected |
© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 51 other files (scripts, references, assets) in skills/platform-data-manage of forcedotcom/sf-skills.
- SKILL.md
- README.md
- assets/bulk/bulk-insert-10000.apex
- assets/bulk/bulk-insert-200.apex
- assets/bulk/bulk-insert-500.apex
- assets/bulk/bulk-upsert-external-id.apex
- assets/cleanup/delete-by-created-date.apex
- assets/cleanup/delete-by-name.apex
- assets/cleanup/delete-test-data.apex
- assets/cleanup/rollback-transaction.apex
- assets/csv/account-import.csv
- assets/csv/contact-import.csv
- assets/csv/custom-object-import.csv
- assets/csv/opportunity-import.csv
- assets/factories/account-factory.apex
- assets/factories/case-factory.apex
- … and 36 more
Open the folder on GitHubat commit e5164d9
Compare with similar skills
Platform Data Manage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Platform Data Manage this skillforcedotcom/sf-skills | 1.1k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Sf DataJaganpro/sf-skills | 424 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Soql Lib Testingbeyond-the-cloud-dev/soql-lib | 154 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Skill Doli Test InteractiveDolibarr/dolibarr | 7.7k | 1 repos | ~5.5k | Automated safety check: Pass | GPL-3.0 | |
| Eval Designagentscope-ai/OpenJudge | 868 | — | ~2.8k | Automated safety check: Warn | Apache-2.0 | |
| Sf DeployJaganpro/sf-skills | 424 | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Soql Lib Testing
beyond-the-cloud-dev/soql-lib
Writes unit tests for Salesforce Apex code that uses SOQL Lib (SOQL.cls).
Skill Doli Test Interactive
Dolibarr/dolibarr
Create interactive PHP test case scripts for Dolibarr ERP/CRM that allow users to setup test data, view results via direct links, and tear down (clean up) the data.
Eval Design
agentscope-ai/OpenJudge
A skill your agent uses when the user needs to design evaluation datasets, create test cases, stratify samples, generate adversarial examples, extract eval dimensions from traces/specs, or build a…
Sf Deploy
Jaganpro/sf-skills
Salesforce DevOps automation using sf CLI v2. An agent skill from Jaganpro/sf-skills.
Sf Vlocity Build Deploy
Jaganpro/sf-skills
Salesforce Industries DataPack deployment automation using Vlocity Build.
More from forcedotcom/sf-skills
All 251 skills in this repoAgentforce Architecture Analyze
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Design Systems Slds Apply
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
Experience Lwc Generate
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Related
Works with
Categories
Questions about Platform Data Manage
What does Platform Data Manage do?
Salesforce data operations with 130-point scoring. An agent skill from forcedotcom/sf-skills. Platform Data Manage is an agent skill from forcedotcom/sf-skills. Salesforce data operations with 130-point scoring.
When should I use Platform Data Manage?
Platform Data Manage fits situations like: bulk import/export; generate test data; clean up org records via sf CLI and anonymous Apex; creating test data.
How do I install Platform Data Manage in Claude Code?
Run `npx skills add forcedotcom/sf-skills --skill platform-data-manage -a claude-code`. Or copy the skill folder (skills/platform-data-manage in forcedotcom/sf-skills) into .claude/skills/platform-data-manage in your project. Claude Code loads it when a task matches its description.
How do I install Platform Data Manage in Codex?
Run `npx skills add forcedotcom/sf-skills --skill platform-data-manage -a codex`. Or copy the skill folder (skills/platform-data-manage in forcedotcom/sf-skills) into .agents/skills/platform-data-manage in your project. Codex loads it when a task matches its description.
Can I use Platform Data Manage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill platform-data-manage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/platform-data-manage, .gemini/skills/platform-data-manage, .github/skills/platform-data-manage and .opencode/skills/platform-data-manage in your project.
What does Platform Data Manage need to run?
Going by SKILL.md and its folder, Platform Data Manage needs the command-line tools its instructions call (sf) and credentials named INVALID_CROSS_REFERENCE_KEY. Our summary lists: A credential in INVALID_CROSS_REFERENCE_KEY.
Does Platform Data Manage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Platform Data Manage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Platform Data Manage use?
Platform Data Manage is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Platform Data Manage use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.
What are the alternatives to Platform Data Manage?
Skills that share tags, products or a category with Platform Data Manage: Sf Data (Jaganpro/sf-skills, 424 stars), Soql Lib Testing (beyond-the-cloud-dev/soql-lib, 154 stars), Skill Doli Test Interactive (Dolibarr/dolibarr, 7.7k stars) and Eval Design (agentscope-ai/OpenJudge, 868 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Platform Data Manage?
forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.
Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.