@contentrain/skills 0.5.1 → 0.5.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentrain/skills",
-  "version": "0.5.1",
+  "version": "0.5.3",
   "license": "MIT",
   "description": "AI agent skills for Contentrain — workflow procedures, framework integration guides",
   "type": "module",
@@ -61,7 +61,7 @@
     "tsdown": "^0.21.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0",
-    "@contentrain/mcp": "1.5.1"
+    "@contentrain/mcp": "1.6.0"
   },
   "scripts": {
     "build": "tsdown src/index.ts --format esm,cjs --dts",

package/skills/contentrain/references/workflow.md

@@ -271,7 +271,7 @@ Metadata files track governance information. They are system-managed -- agents N
   "status": "published",
   "source": "agent",
   "updated_by": "claude",
-  "approved_by": "ahmet@contentrain.io",
+  "approved_by": "info@contentrain.io",
   "version": "1"
 }
 ```

package/skills/contentrain-quality/references/media.md

@@ -10,6 +10,18 @@ Follow these guidelines when populating image, video, or file fields in any cont
 
 ---
 
+## Storage & Reference Models
+
+Media references are stored in one of two models. Identify which one the project uses before populating image, video, or file fields. The asset rules below (dimensions, formats, size limits, naming) apply to **both**; only the **Asset Organization** section (paths under `assets_path`, relative references) is specific to the local-file model.
+
+1. **Local file model (default / OSS).** Media lives on disk under `config.json > assets_path` (default `.contentrain/assets/`) and is referenced by a **relative path from the project root** (e.g. `.contentrain/assets/blog/hero.webp`). To turn relative paths into URLs at read time, set `config.json > cdn.url` (or `contentrain generate --cdnBaseUrl <base>`) and use the `media()` resolver baked into the `@contentrain/query` generated client — `media('media/...') → {cdn.url}/{path}`.
+
+2. **Studio CDN model.** Media lives in the Studio CDN/object store and is referenced by a relative storage path (`media/...`) returned by the media library. Pass either that `media/...` path or its URL to `contentrain_content_save`: in **cloud mode** the value is **automatically normalized to an absolute public delivery URL** on save (`{base}/{path}`), in both media fields and markdown bodies, so the committed content renders in a browser anywhere with no SDK. In **local mode** the relative path is kept verbatim. The rewrite is idempotent and never touches external URLs (`http(s)://`, `//`, `data:`) or already-absolute delivery URLs — so for external images (a CDN or Unsplash URL), just save the URL directly.
+
+Never hand-build delivery URLs or guess the CDN base. Save the path or URL the media library gives you; the platform resolves it.
+
+---
+
 ## Image Dimensions (Recommended)
 
 1. Use these standard dimensions unless the project's `context.json` specifies overrides:

package/skills/contentrain-sdk/SKILL.md

@@ -78,6 +78,22 @@ const doc = document('blog-post').bySlug('getting-started')
 | `.where(field, op, value)` | Operator filter (same ops as QueryBuilder) |
 | `.include(relation)` | Resolve relation fields |
 
+### Media
+
+Media / image / file field values are plain strings. How you turn them into a URL depends on the storage model:
+
+- **Studio-CDN content** already carries absolute delivery URLs — the write path normalizes `media/...` references on save — so use the field value directly, no resolution needed.
+- **Relative-path content** (OSS / local-file model, values like `media/...`) resolves through an optional `media()` helper baked into the generated client. Set `config.json > cdn.url` (or run `contentrain generate --cdnBaseUrl <base>`) and the client exports it:
+
+```typescript
+import { media } from '#contentrain'
+
+media('media/original/hero.webp')          // → '{cdn.url}/media/original/hero.webp'
+media('https://images.unsplash.com/x.jpg') // → unchanged (external pass-through)
+```
+
+`media()` is omitted when no base is configured, and is idempotent — external URLs (`http(s)://`, `//`, `data:`) and already-absolute delivery URLs pass through untouched. It is the **local-mode** counterpart of CDN mode's `client.media()` (which returns a `MediaAccessor` over the media manifest, below).
+
 ## CDN Mode (Remote Data)
 
 For server-side or client-side apps that fetch content from Contentrain Studio CDN:
@@ -151,6 +167,7 @@ const history = await conv.history(response.conversationId)
 - Locale fallback chain: explicit → config default → first available
 - Generated files in `.contentrain/client/` are **immutable** — always regenerate, never edit
 - Run `contentrain generate` after any model change
+- **Media**: Studio-CDN fields already carry absolute URLs; for relative `media/...` values set `config.cdn.url` (or `generate --cdnBaseUrl`) and resolve with the generated `media()` helper
 
 ## Framework Integration