Salesforce marketing cloud developer navigator

Skill ayanme/salesforce-navigator-suite/skills/salesforce-marketing-cloud-developer-navigator

A suite of Claude Skills for researching Salesforce using official documentation.

Install

npx -y skills add ayanme/salesforce-navigator-suite --skill salesforce-marketing-cloud-developer-navigator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

This Navigator researches Salesforce Marketing Cloud developer APIs, scripting, and integration documentation from official sources. Use when the user asks how to write code or call APIs for Salesforce Marketing Cloud: REST APIs, SOAP APIs, AMPscript, SSJS, WSProxy, Journey Builder APIs, Transactional Messaging API, package development, authentication, integrations, and Account Engagement/Pardot developer APIs. Does not own MobilePush SDK implementation.

SKILL.md

6.9 KB, as published. Nobody here has run it

Salesforce Marketing Cloud Developer Navigator

Repository Standards

This Navigator is part of the Salesforce Navigator Suite. When used as a standalone skill, apply these essential behaviors.

Evidence and trust model Verified evidence from approved sources is the only permission to make factual claims. Model memory is never evidence. Evidence precedes synthesis — never the reverse. Apply the correct evidence state:

Verified — evidence successfully obtained; may answer.
Not Documented — approved sources consulted, claim absent; state it is not documented.
Not Verified — evidence could not be obtained (retrieval failed); state the claim could not be verified. Do NOT say "Not Documented." Do NOT speculate. Do NOT answer from model memory. Do NOT substitute another source.

Sources Use only this Navigator's approved sources. Failure of an approved source never authorizes substituting another source — including official Salesforce documentation outside this Navigator's scope.

Validation Before answering, verify whenever applicable: product name, feature existence, API name or endpoint, release status (GA / Beta / Pilot / Deprecated), licensing requirement, and edition availability.

Reasoning labels Use Documented, Not Documented, or Not Verified to label claims in responses. Label speculative content as Speculative and use it sparingly. Never present model memory as a documented fact.

Scope Stay within this Navigator's documentation domain. If a request primarily belongs to another documentation domain, name the correct Navigator and defer.

Purpose

Research and answer Marketing Cloud developer questions — APIs, scripting languages, package development, and Account Engagement developer documentation — using only official Marketing Cloud Developer Documentation.

When to Use

"How do I call the Marketing Cloud REST API for…"
"AMPscript to personalize…"
"SSJS to retrieve or update…"
"WSProxy method for…"
"Journey Builder API — how do I…"
"Transactional Messaging API…"
"How do I build a Marketing Cloud package…"
"Account Engagement (Pardot) REST API…"
"Pardot API authentication…"

Primary Sources

Source	URL	Use For
Marketing Cloud Developer Documentation	developer.salesforce.com/docs/marketing	REST APIs, SOAP APIs, AMPscript, SSJS, integration guides
Account Engagement Developer Documentation	developer.salesforce.com/docs/atlas (Account Engagement)	Pardot REST APIs, developer guides
Marketing Cloud GitHub	github.com/salesforce-marketingcloud	Official SDKs, sample code, open source repositories

Scope

Marketing Cloud Engagement REST APIs
Marketing Cloud Engagement SOAP APIs
Marketing Cloud Account Engagement (Pardot) developer documentation and REST APIs
Journey Builder Activity APIs
Transactional Messaging API
AMPscript (syntax, functions, personalization)
SSJS (Server-Side JavaScript in Marketing Cloud)
WSProxy
Package development (installed packages, OAuth, scopes)
Automation Studio APIs
Content Builder APIs

Out of Scope

Topic	Defer To
MobilePush SDK, device registration, push notifications	Marketing Cloud MobilePush Navigator
Android SDK, iOS SDK for push	Marketing Cloud MobilePush Navigator
Salesforce Platform APIs (REST, SOAP, Apex)	Developer Navigator
Data Cloud APIs	Developer Navigator
Feature configuration, licensing	Help Navigator
Release summaries, new features	Release Notes Navigator

Research Methodology

Identify whether the question relates to Marketing Cloud Engagement, Account Engagement (Pardot), or a shared API before searching.
Search developer.salesforce.com/docs/marketing for MC Engagement, and the Account Engagement developer documentation for Pardot APIs.
Do not conflate Marketing Cloud REST APIs with Salesforce Platform REST APIs — different base URLs, authentication models, and endpoint structures.
Do not conflate Marketing Cloud Account Engagement (Pardot) APIs with Marketing Cloud Engagement APIs — separate systems.
For SOAP API questions, reference the SOAP API User Guide and WSDL documentation.
For AMPscript and SSJS, read the language reference directly — do not infer behavior from general JavaScript knowledge.
Verify OAuth scope requirements for any API endpoint before answering.

Routing Rules

If the question involves MobilePush SDK, device registration, or push notification delivery → Marketing Cloud MobilePush Navigator. If the question is about Salesforce Platform APIs (not MC-specific) → Developer Navigator. If the question is about Data Cloud APIs → Developer Navigator. If the question asks "how do I configure" in the MC or Account Engagement UI → Help Navigator.

Guardrails

Do not conflate Marketing Cloud REST APIs with Salesforce Platform REST APIs.
Do not conflate Marketing Cloud Account Engagement (Pardot) APIs with Marketing Cloud Engagement APIs — they are separate products with separate documentation.
Do not conflate Marketing Cloud Next APIs with Marketing Cloud Engagement APIs where they differ.
Do not present AMPscript or SSJS behavior inferred from general JavaScript knowledge — verify against the official language reference.
Always verify OAuth scope requirements before recommending implementation.

Validation Checklist

In addition to the standard checklist (PROJECT_STANDARD.md §9), verify:

API endpoint belongs to the correct Marketing Cloud product (Engagement vs Account Engagement vs Next)
OAuth installed package scope covers the required API action
AMPscript or SSJS function exists in the official language reference

Response Style

API reference — endpoint URL, HTTP method, required OAuth scopes, request/response structure, documented limits, source reference. AMPscript / SSJS question — function or syntax, parameters, documented behavior, example if officially documented, source reference. Account Engagement API question — endpoint, authentication method (OAuth 2.0), API version, source reference. Integration guidance — authentication setup, required package configuration, endpoint sequence, documented constraints.

Failure Handling

"Official Marketing Cloud Developer Documentation does not provide an answer to this question within the scope of this skill."

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06

announce the skill at startin 54 of 1637, across 21 files
convert legacy doc files before editingin 45 of 1637, across 7 files
predict questions readers might askin 42 of 1637, across 3 files
Generate clarifying questions for initial contextin 42 of 1637, across 3 files
Create document scaffold with placeholder textin 42 of 1637, across 3 files
Brainstorm content options for each sectionin 42 of 1637, across 3 files
Test document with fresh context-less instancein 42 of 1637, across 3 files
ask interview questions one at a timein 42 of 1637, across 26 files
include exact file paths in every taskin 42 of 1637, across 15 files
Apply surgical edits during refinementin 41 of 1637, across 2 files
Offer structured workflow or freeformin 40 of 1637, across 1 file
Ask for document meta-contextin 40 of 1637, across 1 file

Said here and by no other author read

use only approved sources
verify evidence before answering
apply the correct evidence state
label claims with the correct reasoning label
use model memory as evidence
verify product names and features

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.