salesforce-api-integration@1.0.3
CAUTION· static onlyPublisher claims: "Calls the Salesforce REST, Bulk, Composite, and Metadata APIs: SOQL, record CRUD, upserts, OAuth, sync, and error handling. Use when querying, loading, exporting or syncing Salesforce data, when writing SOQL or SOSL against Account, Contact, Opportunity, Lead, Case or a `__c` custom object, when a call returns INVALID_SESSION_ID, MALFORMED_QUERY, INVALID_FIELD, REQUEST_LIMIT_EXCEEDED, UNABLE_TO_LOCK_ROW, or DUPLICATES_DETECTED, when importing tens of thousands of records or migrating from another CRM, when setting up server-to-server auth with a Connected App, JWT bearer or refresh token, when keeping an external database in step through Change Data Capture or Platform Events, or when calling a custom Apex REST endpoint or invoking a Flow. Covers sandboxes, API versioning, external IDs, and field-level security. Not for designing a personal CRM (`crm`), generic third-party API mechanics (`api`), or authoring Apex code." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Pipe-to-shell pattern. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…AsyncApexJob` | **When a custom endpoint, action or flow enters the picture**: add its row to `## Integrations` in `memory.md` (name, direction, mechanism, objects, owner) and put its contract — path, payl…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…completion. Check `DataStorageMB` before a load that adds millions of rows, and write the reading into `## Limits Observed` in `memory.md`. ## Budgeting a Job State this before running anything large: ``` calls = c…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…he user asks for repeatedly, or it replaces a report that hit its row ceiling — add a row to `## Saved Queries` in `~/Clawic/data/salesforce-api-integration/memory.md` with its purpose and whether the filter is selective. If a query's fail…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…it — save it as `artifacts/<kebab-name>.md` with a line on when to read it, and add its `## Boxes` line in `memory.md` the same turn. Rebuilding a 25-step chain from scratch costs an afternoon; rea…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…es, a picklist restricted by record type, a master-detail you cannot reparent — add or update its row in `## Schema Map` in `memory.md`. If you had to derive the whole field list, it goes to `schema/<object-api-nam…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| code_style | curl \| python \| node \| sf-cli | curl | Language of every emitted example |Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim ivangdavila: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.