Add info about transferring vals between orgs

.changeset/tender-memes-burn.md

@@ -0,0 +1,5 @@
+---
+"@valtown/skills": minor
+---
+
+New skill for creating custom user skills; information on transferring vals between orgs

plugin/skills/blob-storage/SKILL.md

@@ -103,6 +103,10 @@ When using the `storeBlob`, `readBlob`, `listBlobs`, or `deleteBlob` tools again
 - `getJSON` returns `undefined` for missing keys; `get` throws `ValTownBlobNotFoundError`. Handle the absent case accordingly.
 - Don't store secrets in blobs — use environment variables for credentials.
 
+## Transfer between orgs
+
+Blob storage scoped to a val will automatically transfer when transferring the val to a different org.
+
 ## Reference
 
 Full API docs: https://docs.val.town/std/blob/

plugin/skills/http-endpoints/SKILL.md

@@ -77,3 +77,7 @@ For HTML responses, add this script tag to send browser errors back to val logs
 ## Verifying changes
 
 After editing an HTTP val, fetch it to confirm it returns the expected HTTP response. Do not report a change as done without this step.
+
+## Transfer between orgs
+
+HTTP endpoints will continue working/unchanged when transferring a val to a different org.

plugin/skills/sqlite-storage/SKILL.md

@@ -58,6 +58,10 @@ When using the `sqlite_execute` or `sqlite_batch` tools to query a val owned by
 - Use `CREATE TABLE IF NOT EXISTS` so schema setup is idempotent across val restarts.
 - Schema migrations: add new columns with `ALTER TABLE ... ADD COLUMN`. Wrap in `try/catch` if the migration may run against an already-updated table.
 
+## Transfer between orgs
+
+SQLite data scoped to a val will automatically transfer when transferring the val to a different org.
+
 ## Reference
 
 Full API docs: https://docs.val.town/reference/std/sqlite/usage/

plugin/skills/third-party-integrations/SKILL.md

@@ -33,3 +33,7 @@ Services with dedicated guides today — not exhaustive, so use the sitemap from
 ## Why this matters
 
 Integration code is the most common place models hallucinate. APIs change, auth flows get reworked, and platform constraints (no filesystem, no subprocess) break naive approaches. The Val Town guide is the source of truth for what currently works on the platform.
+
+## Transferring secrets between orgs
+
+Note that environment variables scoped to a val will automatically transfer when transferring the val to a different org. Environment groups will _not_ transfer, nor will (deprecated) account-based environment variables.