Recommend script files for errorHandling scripts in the build-plugin skill

[andrewmumblebee]

📋 Summary

The build-plugin skill only showed errorHandling scripts written inline in the stream JSON, which becomes unreadable beyond a one-liner. The deploy pipeline resolves errorHandling.script file references from dataStreams/scripts/ using exactly the same mechanism as postRequestScript (it's one of the two registered dataStreamScriptPaths, and plugin export already writes to an errorHandling/ sub-folder), so the skill now documents that form — and only that form, since script files are easier to review than inline JSON strings:

• The errorHandling section of references/data-streams.md shows the file-reference form as the way to write a script (dataStreams/scripts/errorHandling/<streamName>.js), with a "Script files" subsection covering the reference-resolution rules (bare .js path marks a reference, deploy inlines the source, unresolvable references fail validation, {{ ... }} expressions work in script files too) and a script-file example. No inline example remains.
• The post-request script wiring section cross-links the errorHandling equivalent.
• The scaffold folder layout in SKILL.md shows the scripts/errorHandling/ sub-folder.

---

🔍 Scope of change

• Documentation only
• Repository metadata or configuration
• CI / automation
• Other (please describe):

---

📚 Checklist

• I agree to the Code of Conduct

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated plugin scaffolding guidance to include the errorHandling/ script directory.
  • Clarified that error-handling scripts should be referenced as files rather than inline code.
  • Added examples and guidance on script placement, file paths, and required .js extensions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: d31f2c21-95bd-4994-92c3-1ce4dfad8c33

📥 Commits

Reviewing files that changed from the base of the PR and between 9dafcf7 and 70a72c1.

📒 Files selected for processing (2)

• .claude/skills/build-plugin/SKILL.md
• .claude/skills/build-plugin/references/data-streams.md

---

📝 Walkthrough

Walkthrough

The documentation updates define error-handling scripts as .js files stored in dataStreams/scripts/errorHandling/, referenced by path, and reflected in the plugin scaffold structure.

Changes

Error-handling script file guidance

Layer / File(s)	Summary
Document error-handling script references .claude/skills/build-plugin/references/data-streams.md	Error-handling examples now reference script files, document their required location and .js extension, and clarify wiring from the errorHandling/ folder.
Align plugin scaffolding .claude/skills/build-plugin/SKILL.md	The scaffold structure now includes an errorHandling/ directory containing a path-referenced myStream.js script.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly names the main documentation change: recommending file-based errorHandling scripts in the build-plugin skill.
Description check	✅ Passed	The description includes a clear summary, scope, and checklist, and it matches the docs-only change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🧩 Plugin PR Summary

ℹ️ No plugins were modified in this PR.

[clarkd]

Ah - you can probably ignore some of the comments on your Sanity PR!

[andrewmumblebee]

Ah - you can probably ignore some of the comments on your Sanity PR!

@clarkd yeah I still need to clean those up, don't even need errorHandling on that PR, as I changed how the objects are indexed, so we only index ones we have apiKeys for so the errorHandling should never be hit