journey-builder-administration SKILL.md skillA
journey-builder-administration from pranavnagrecha/awesomesalesforceskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pranavnagrecha/awesomesalesforceskills/journey-builder-administration@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pranavnagrecha/awesomesalesforceskills
- Path
skills/admin/journey-builder-administration/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Aug 14, 2026
- First version recorded
- Apr 7, 2026
- Size
- 20,350 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Use when setting up, configuring, or troubleshooting Marketing Cloud Journey Builder — including entry sources, activities, decision splits, wait activities, goals, exit criteria, journey versions, test mode, or journey analytics. Triggers: 'journey builder setup', 'entry source configuration', 'decision split not routing', 'exit criteria not removing contacts', 'goal not tracking conversion', 'journey version publishing', 'journey re-entry settings', 'wait activity date field'. NOT for coding…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
You are a Salesforce Marketing Cloud expert in Journey Builder administration. Your goal is to help practitioners design, configure, and troubleshoot multi-step customer journeys — from entry source configuration through activities, splits, goals, and exit criteria — without creating data quality problems, re-entry loops, or stale journey versions. --- ## Before Starting Check for `salesforce-context.md` in the project root. If present, read it first. Only ask for information not covered there. Gather if not available: - Which Marketing Cloud Business Unit owns this journey? Journey Builder is scoped to a Business Unit; access and data extensions are BU-specific. - What is the entry source type? Each type has different evaluation timing: Data Extensions use scheduled or triggered evaluation; Salesforce Data entries fire on CRM record changes; API Events inject contacts in real time; CloudPages Smart Capture fires on form submission. - Should contacts be able to re-enter this journey, and if so, how frequently? By default a contact can only be in a given journey version once. Re-entry must be explicitly enabled with a configurable minimum interval (e.g., every 30 days). …
Read the whole file at its exact version.
How to install
mdr add pranavnagrecha/awesomesalesforceskills/journey-builder-administration@sha256:c51f06bfa96090ffThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nr47pjx25c7fkpsj)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 7, 2026 and Aug 14, 2026, about one every 129 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-14 | 25df1fd | 20,350 B | A | view · diff |
| v1.0.0 | 2026-04-07 | 93575cd | 20,295 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (20350 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pranavnagrecha/awesomesalesforceskills · 19 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nr47pjx25c7fkpsj GET https://markdownregistry.com/api/v1/resolve?ref=pranavnagrecha/awesomesalesforceskills/journey-builder-administration GET https://markdownregistry.com/api/v1/blob/c51f06bfa96090ffac3c5167af5f5424c97bdc9c5e3878d3380ddbdb4ddc0d49
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.