From 9edf77bd6ee18ae9a0037001d17dd9b299be287b Mon Sep 17 00:00:00 2001 From: chandresh-patelsf <118016778+chandresh-patelsf@users.noreply.github.com> Date: Wed, 6 May 2026 22:41:09 -0700 Subject: [PATCH] Update getting datacloud schema (#243) * fix: update getting-datacloud-schema skill path references Replace relative ./scripts/ paths with /scripts/ to correctly resolve script location regardless of working directory. Remove metadata version field from frontmatter. * fix: restore metadata version field in getting-datacloud-schema skill * fix: move requirements.txt to project root in directory structure diagrams --- .../SKILL.md | 2 +- .../references/README.md | 4 ++-- .../references/quick-reference.md | 4 ++-- skills/getting-datacloud-schema/SKILL.md | 20 +++++++++---------- 4 files changed, 14 insertions(+), 16 deletions(-) diff --git a/skills/developing-datacloud-code-extension/SKILL.md b/skills/developing-datacloud-code-extension/SKILL.md index 47c35d6..eead4fd 100644 --- a/skills/developing-datacloud-code-extension/SKILL.md +++ b/skills/developing-datacloud-code-extension/SKILL.md @@ -83,8 +83,8 @@ sf data-code-extension function init --package-dir my-transform/ # Project root ├── payload/ # CRITICAL: This is what --package-dir must point to for deploy │ ├── entrypoint.py # Main transformation code -│ ├── requirements.txt # Python dependencies │ └── config.json # Code extension configuration +├── requirements.txt # Python dependencies └── README.md ``` diff --git a/skills/developing-datacloud-code-extension/references/README.md b/skills/developing-datacloud-code-extension/references/README.md index 6b148d3..0116d55 100644 --- a/skills/developing-datacloud-code-extension/references/README.md +++ b/skills/developing-datacloud-code-extension/references/README.md @@ -139,8 +139,8 @@ After `init`, you'll have: my-transform/ ├── payload/ │ ├── entrypoint.py # Your transformation code -│ ├── config.json # Permissions and configuration -│ └── requirements.txt # Python dependencies +│ └── config.json # Permissions and configuration +├── requirements.txt # Python dependencies └── README.md ``` diff --git a/skills/developing-datacloud-code-extension/references/quick-reference.md b/skills/developing-datacloud-code-extension/references/quick-reference.md index 5b542d9..b18e65b 100644 --- a/skills/developing-datacloud-code-extension/references/quick-reference.md +++ b/skills/developing-datacloud-code-extension/references/quick-reference.md @@ -219,8 +219,8 @@ sf data-code-extension script scan --entrypoint ./payload/entrypoint.py my-project/ ├── payload/ │ ├── entrypoint.py # Main code -│ ├── config.json # Auto-generated permissions -│ └── requirements.txt # Auto-generated dependencies +│ └── config.json # Auto-generated permissions +├── requirements.txt # Auto-generated dependencies └── README.md ``` diff --git a/skills/getting-datacloud-schema/SKILL.md b/skills/getting-datacloud-schema/SKILL.md index f7c3f17..f3f1dfe 100644 --- a/skills/getting-datacloud-schema/SKILL.md +++ b/skills/getting-datacloud-schema/SKILL.md @@ -67,30 +67,28 @@ sf org login web --alias ### Step 3a: Execute DLO Schema Script -Use the Python script to retrieve DLO information: +The Python scripts are bundled with this skill. They live in the `scripts/` subdirectory of the same directory that contains this SKILL.md file. Use the absolute path to that directory — do NOT use `./scripts/` as that resolves relative to the current working directory, not the skill directory. **To list all DLOs:** ```bash -python3 ./scripts/get_dlo_schema.py +python3 /scripts/get_dlo_schema.py ``` **To get specific DLO schema:** ```bash -python3 ./scripts/get_dlo_schema.py +python3 /scripts/get_dlo_schema.py ``` ### Step 3b: Execute DMO Schema Script -Use the Python script to retrieve DMO information: - **To list all DMOs:** ```bash -python3 ./scripts/get_dmo_schema.py +python3 /scripts/get_dmo_schema.py ``` **To get specific DMO schema:** ```bash -python3 ./scripts/get_dmo_schema.py +python3 /scripts/get_dmo_schema.py ``` ### Step 4: Present Results @@ -227,7 +225,7 @@ User: "Show me all DLOs in afvibe org" Response: 1. Run sf org list to discover connected org alias 2. Authenticate to afvibe -3. Run: python3 ./scripts/get_dlo_schema.py afvibe +3. Run: python3 /scripts/get_dlo_schema.py afvibe 4. Display formatted list of DLOs ``` @@ -238,7 +236,7 @@ User: "Get the schema for Employee__dll in afvibe" Response: 1. Run sf org list to discover connected org alias 2. Authenticate to afvibe -3. Run: python3 ./scripts/get_dlo_schema.py afvibe Employee__dll +3. Run: python3 /scripts/get_dlo_schema.py afvibe Employee__dll 4. Display field schema with types and metadata ``` @@ -261,7 +259,7 @@ User: "Show me all DMOs in afvibe org" Response: 1. Run sf org list to discover connected org alias 2. Authenticate to afvibe -3. Run: python3 ./scripts/get_dmo_schema.py afvibe +3. Run: python3 /scripts/get_dmo_schema.py afvibe 4. Display formatted list of DMOs ``` @@ -272,7 +270,7 @@ User: "Get the schema for Individual__dlm in afvibe" Response: 1. Run sf org list to discover connected org alias 2. Authenticate to afvibe -3. Run: python3 ./scripts/get_dmo_schema.py afvibe Individual__dlm +3. Run: python3 /scripts/get_dmo_schema.py afvibe Individual__dlm 4. Display field schema with types and metadata ```