@indreamai/openclaw-plugin 0.1.0

package/dist/setup-entry.d.ts

@@ -0,0 +1,11 @@
+import * as openclaw_plugin_sdk_plugin_entry from 'openclaw/plugin-sdk/plugin-entry';
+
+declare const _default: {
+    id: string;
+    name: string;
+    description: string;
+    configSchema: openclaw_plugin_sdk_plugin_entry.OpenClawPluginConfigSchema;
+    register: NonNullable<openclaw_plugin_sdk_plugin_entry.OpenClawPluginDefinition["register"]>;
+} & Pick<openclaw_plugin_sdk_plugin_entry.OpenClawPluginDefinition, "kind">;
+
+export { _default as default };

package/dist/setup-entry.js

@@ -0,0 +1,20 @@
+import {
+  PLUGIN_DESCRIPTION,
+  PLUGIN_ID,
+  PLUGIN_NAME,
+  pluginConfigSchema
+} from "./chunk-ENGUNMFI.js";
+
+// src/setup-entry.ts
+import { definePluginEntry } from "openclaw/plugin-sdk/plugin-entry";
+var setup_entry_default = definePluginEntry({
+  id: PLUGIN_ID,
+  name: PLUGIN_NAME,
+  description: PLUGIN_DESCRIPTION,
+  configSchema: pluginConfigSchema,
+  register() {
+  }
+});
+export {
+  setup_entry_default as default
+};

package/openclaw.plugin.json

@@ -0,0 +1,98 @@
+{
+  "id": "indream",
+  "name": "Indream",
+  "description": "Indream video editor API tools and skills for OpenClaw",
+  "version": "0.1.0",
+  "skills": [
+    "./skills"
+  ],
+  "contracts": {
+    "tools": [
+      "indream_editor_capabilities",
+      "indream_editor_validate",
+      "indream_projects_list",
+      "indream_projects_get",
+      "indream_projects_list_assets",
+      "indream_assets_get",
+      "indream_exports_get",
+      "indream_exports_list",
+      "indream_exports_wait",
+      "indream_projects_create",
+      "indream_projects_update",
+      "indream_projects_sync",
+      "indream_projects_delete",
+      "indream_projects_add_asset",
+      "indream_projects_remove_asset",
+      "indream_assets_upload",
+      "indream_assets_delete",
+      "indream_exports_create",
+      "indream_projects_create_export"
+    ]
+  },
+  "uiHints": {
+    "apiKey": {
+      "label": "Indream API key",
+      "help": "Used for all requests to the Indream Open API.",
+      "placeholder": "indream_...",
+      "sensitive": true
+    },
+    "baseURL": {
+      "label": "Base URL",
+      "placeholder": "https://api.indream.ai"
+    },
+    "timeoutMs": {
+      "label": "Timeout (ms)",
+      "advanced": true
+    },
+    "pollIntervalMs": {
+      "label": "Poll interval (ms)",
+      "advanced": true
+    },
+    "uploads": {
+      "label": "Upload controls",
+      "advanced": true
+    }
+  },
+  "configSchema": {
+    "type": "object",
+    "additionalProperties": false,
+    "properties": {
+      "apiKey": {
+        "type": "string",
+        "minLength": 1
+      },
+      "baseURL": {
+        "type": "string",
+        "default": "https://api.indream.ai"
+      },
+      "timeoutMs": {
+        "type": "integer",
+        "minimum": 1,
+        "default": 60000
+      },
+      "pollIntervalMs": {
+        "type": "integer",
+        "minimum": 1,
+        "default": 2000
+      },
+      "uploads": {
+        "type": "object",
+        "additionalProperties": false,
+        "properties": {
+          "allowLocalPaths": {
+            "type": "boolean",
+            "default": true
+          },
+          "allowRemoteUrls": {
+            "type": "boolean",
+            "default": true
+          }
+        },
+        "default": {
+          "allowLocalPaths": true,
+          "allowRemoteUrls": true
+        }
+      }
+    }
+  }
+}

package/package.json

@@ -0,0 +1,58 @@
+{
+  "name": "@indreamai/openclaw-plugin",
+  "version": "0.1.0",
+  "description": "OpenClaw plugin for Indream video editor API workflows",
+  "type": "module",
+  "files": [
+    "dist",
+    "skills",
+    "openclaw.plugin.json",
+    "README.md"
+  ],
+  "scripts": {
+    "build": "tsup src/index.ts src/setup-entry.ts --format esm --dts --tsconfig tsconfig.build.json",
+    "typecheck": "tsc --noEmit -p tsconfig.json",
+    "lint": "eslint src tests",
+    "test": "vitest run"
+  },
+  "engines": {
+    "node": ">=22"
+  },
+  "openclaw": {
+    "extensions": [
+      "./dist/index.js"
+    ],
+    "setupEntry": "./dist/setup-entry.js",
+    "compat": {
+      "pluginApi": ">=2026.4.2",
+      "minGatewayVersion": "2026.4.2"
+    },
+    "build": {
+      "openclawVersion": "2026.4.2",
+      "pluginSdkVersion": "2026.4.2"
+    },
+    "install": {
+      "npmSpec": "@indreamai/openclaw-plugin",
+      "localPath": ".",
+      "defaultChoice": "npm",
+      "minHostVersion": ">=2026.4.2"
+    }
+  },
+  "packageManager": "pnpm@10.26.1",
+  "dependencies": {
+    "@indreamai/client": "^0.3.0",
+    "@sinclair/typebox": "^0.34.49",
+    "mime-types": "^3.0.2",
+    "openclaw": "^2026.4.2"
+  },
+  "devDependencies": {
+    "@types/node": "^25.5.2",
+    "@typescript-eslint/eslint-plugin": "^8.58.0",
+    "@typescript-eslint/parser": "^8.58.0",
+    "eslint": "^10.2.0",
+    "eslint-config-prettier": "^10.1.8",
+    "tsup": "^8.5.1",
+    "typescript": "^6.0.2",
+    "vitest": "^4.1.2"
+  }
+}

package/skills/indream-editor-json/SKILL.md

@@ -0,0 +1,157 @@
+---
+name: indream-editor-json
+description: Plan, build, validate, and repair production-ready Indream editor JSON with complete guidance for media, subtitles, motion, transitions, effects, filters, templates, charts, and schema troubleshooting.
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "🎬",
+        "requires":
+          {
+            "config": ["plugins.entries.indream.config.apiKey"],
+          },
+      },
+  }
+---
+
+# Indream Editor JSON
+
+Use this skill when the user wants to create, repair, explain, or optimize Indream editor JSON.
+
+## Goal
+
+Produce editor JSON that is valid for the current Indream schema and capability set, matches the user's creative intent, and is ready for validation and export without guesswork.
+
+## Mandatory workflow
+
+1. Identify the requested deliverable before writing JSON:
+   - composition size or output ratio
+   - target duration and scene structure
+   - available assets, captions, templates, existing draft metadata, and export goals
+2. Call `indream_editor_capabilities` before choosing any capability-bound value:
+   - transition types
+   - effect types
+   - filter types
+   - illustration names
+   - caption animation types
+   - any capability-controlled value that may vary by runtime
+3. Start from `references/minimal-editor-state.json`, then build in this order:
+   - top-level composition fields
+   - `assets`
+   - `items`
+   - `tracks`
+   - `transitions`
+   - optional `globalBackground` and `deletedAssets`
+4. Prefer the structured references in this skill over inventing field names or relying on memory.
+5. Run `indream_editor_validate` before any export or project sync step that should persist the new draft.
+6. If validation fails, repair the JSON with `references/validation-repair.md`, then validate again.
+7. If the validator output is ambiguous or a path is hard to interpret, inspect `references/editor-state.v1.schema.json` directly.
+
+## Planning checklist
+
+- Decide whether the timeline is:
+  - single-track sequential
+  - multi-track layered
+  - subtitle-heavy
+  - template-driven
+  - motion-driven with animated geometry
+- Decide whether the user wants:
+  - raster media only
+  - video plus music or voice-over
+  - subtitles from a caption asset
+  - animated text instead of a subtitle asset
+  - timed effects or filters
+  - clip transitions between adjacent scenes
+- Decide whether `text-template` is actually appropriate.
+  Use `text-template` only when the required `templateId`, `templateCategory`, and node structure are known.
+  Otherwise prefer plain `text`, `image`, `solid`, `illustration`, or `chart` items.
+- If the input comes from an existing draft, preserve unrelated valid top-level metadata instead of dropping it casually.
+
+## Authoring rules
+
+- Keep the top-level required keys stable:
+  - `compositionWidth`
+  - `compositionHeight`
+  - `timebaseTicksPerSecond`
+  - `tracks`
+  - `assets`
+  - `items`
+  - `transitions`
+- `timebaseTicksPerSecond` must always be `240000`.
+- Keep IDs stable and readable. Reuse the same IDs across updates instead of regenerating them on every revision.
+- Every `track.items[]` entry must exist in `items`.
+- Every item `assetId` must exist in `assets`.
+- Use the upload result from `indream_assets_upload` directly when possible. The simplest stable pattern is to reuse `editorAssetMapping.assetId` as the editor asset key and as the item `assetId`.
+- All geometry-like number fields must use the animated number track shape:
+  - `{ "value": number, "keyframes": [] }` for static values
+  - `{ "value": number, "keyframes": [{ "timeTicks": n, "value": number }] }` for animated values
+- Do not omit geometry fields from asset-backed items just because they are audio-like or auxiliary. The schema still requires the base item geometry fields.
+- Use `outputRatio` when it helps express user intent, especially when the user asks for a standard aspect ratio such as `16:9` or `9:16`.
+- Preserve optional existing fields that are already valid unless the user asks to remove them.
+- Do not invent unsupported `effectType`, `filterType`, `transition.type`, `illustrationName`, or caption animation names.
+- Do not invent unknown template node contracts. If a template-driven request lacks a real template contract, say so and fall back to regular items.
+- Prefer practical static defaults over speculative animation. Only add motion, transitions, or subtitle effects that the user asked for or that are clearly implied.
+
+## Feature coverage
+
+- Timeline structure, ID strategy, composition sizing, static vs animated number tracks:
+  - `references/structure-and-principles.md`
+- Upload mapping, asset catalog, asset-specific required metadata:
+  - `references/asset-mapping.md`
+- Material libraries, hand-drawn vector illustrations, and sticker compatibility notes:
+  - `references/material-libraries.md`
+- Core item catalog for `image`, `video`, `gif`, `lottie`, `audio`, `solid`, `illustration`, `effect`, `filter`, and `chart`:
+  - `references/common-items.md`
+- Text overlays, subtitle assets, `captions`, `text-template`, and subtitle animation strategy:
+  - `references/text-and-captions.md`
+- Clip animations, keyframes, transitions, effects, filters, and motion design patterns:
+  - `references/motion-effects-and-transitions.md`
+- How to add one keyframe to a single property without rewriting the whole item:
+  - `references/keyframes.md`
+- Practical composition recipes for common user requests:
+  - `references/recipes.md`
+- Full scene templates and composition blueprints:
+  - `references/template-catalog.md`
+  - `references/templates/`
+- Validation and repair workflow:
+  - `references/validation-repair.md`
+- Minimal valid starting point:
+  - `references/minimal-editor-state.json`
+- Full fallback schema for edge-case troubleshooting:
+  - `references/editor-state.v1.schema.json`
+
+## Repair loop
+
+1. If `indream_editor_validate` returns `valid: false`, fix the reported `errors[]` one by one.
+2. Prefer the server error path and code over assumptions.
+3. When an enum value is invalid, replace it with a capability-supported value instead of deleting unrelated fields.
+4. When a transition is invalid, check all of the following before changing the type:
+   - both clips exist
+   - both clips are on the same track
+   - `fromClipId` and `toClipId` are adjacent in `track.items[]`
+   - the transition `type` is supported
+5. When an asset-backed item fails, inspect both the item shape and the referenced asset shape.
+6. When the validator path is not enough, search the full fallback schema for the matching definition name or property path.
+7. Do not create export tasks until validation returns `valid: true`.
+
+## Missing information rules
+
+- Ask for clarification when the user requests a specific template, illustration, supported effect or transition value, or subtitle source that cannot be inferred from the available data.
+- If the user wants a complete draft quickly and a capability-bound value is missing, choose the nearest capability-supported value and state that choice explicitly.
+- If the request conflicts with the schema, prioritize a valid JSON result and explain the compromise.
+
+## Reference files
+
+- `references/structure-and-principles.md`
+- `references/minimal-editor-state.json`
+- `references/asset-mapping.md`
+- `references/material-libraries.md`
+- `references/common-items.md`
+- `references/text-and-captions.md`
+- `references/motion-effects-and-transitions.md`
+- `references/keyframes.md`
+- `references/recipes.md`
+- `references/template-catalog.md`
+- `references/templates/`
+- `references/validation-repair.md`
+- `references/editor-state.v1.schema.json`

package/skills/indream-editor-json/references/asset-mapping.md

@@ -0,0 +1,147 @@
+# Asset Mapping
+
+Use `indream_assets_upload` when the user provides a local file path or a remote media URL.
+Use `indream_projects_list_assets` when the user already has assets attached to an Indream project.
+
+## Recommended ID strategy
+
+The most reliable pattern is to reuse the uploaded `editorAssetMapping.assetId` as:
+
+- the key under `assets`
+- the nested `assets[*].id`
+- the item-level `assetId`
+
+That avoids accidental mismatches.
+
+## Upload result fields that matter for editor JSON
+
+The upload tool returns:
+
+- `assetId`
+- `type`
+- `filename`
+- `mimetype`
+- `fileUrl`
+- `fileKey`
+- `width`
+- `height`
+- `duration`
+- `editorAssetMapping.assetId`
+- `editorAssetMapping.remoteUrl`
+- `editorAssetMapping.remoteKey`
+
+## Standard mapping pattern
+
+```json
+{
+  "assets": {
+    "asset_test": {
+      "id": "asset_test",
+      "type": "image",
+      "filename": "hero.png",
+      "size": 1024,
+      "remoteUrl": "https://cdn.example.com/uploads/hero.png",
+      "remoteKey": "uploads/hero.png",
+      "mimeType": "image/png",
+      "width": 1280,
+      "height": 720
+    }
+  },
+  "items": {
+    "item-image-hero": {
+      "id": "item-image-hero",
+      "type": "image",
+      "assetId": "asset_test"
+    }
+  }
+}
+```
+
+## Asset catalog
+
+### Image asset
+
+Required shape:
+
+- `type: "image"`
+- `id`
+- `filename`
+- `size`
+- `mimeType`
+- `width`
+- `height`
+- `remoteUrl` and `remoteKey` are usually present for uploaded media
+
+### Video asset
+
+Required shape:
+
+- `type: "video"`
+- `durationInSeconds`
+- `hasAudioTrack`
+- `width`
+- `height`
+
+### GIF asset
+
+Required shape:
+
+- `type: "gif"`
+- `durationInSeconds`
+- `width`
+- `height`
+- `loopBehavior: "finite" | "loop"`
+
+### Audio asset
+
+Required shape:
+
+- `type: "audio"`
+- `durationInSeconds`
+
+### Caption asset
+
+Required shape:
+
+- `type: "caption"`
+- `timingGranularity: "word" | "line"`
+- `captions`
+
+Notes:
+
+- Caption records are intentionally flexible in the schema.
+- Preserve caption entries from the source whenever possible instead of rewriting them.
+- Caption assets may have `remoteUrl` and `remoteKey` set to `null`.
+
+### Lottie asset
+
+Required shape:
+
+- `type: "lottie"`
+- `durationInSeconds`
+- `width`
+- `height`
+- `resourceType: "lottie" | "svg"`
+
+Common optional fields:
+
+- `resourceJson`
+- `resourceComponentId`
+- `materialConfig`
+
+## Item-to-asset relationships
+
+- `image` items require an `image` asset.
+- `video` items require a `video` asset.
+- `gif` items require a `gif` asset.
+- `lottie` items require a `lottie` asset.
+- `audio` items require an `audio` asset.
+- `captions` items require a `caption` asset.
+- `text`, `text-template`, `solid`, `illustration`, `effect`, `filter`, and `chart` items do not require assets unless a template node or design workflow explicitly depends on them.
+
+## Practical rules
+
+- When in doubt, keep asset map keys equal to the actual asset ID returned by the upload tool.
+- Do not reference a project asset unless it is actually present in `assets`.
+- Do not guess missing `width`, `height`, or `durationInSeconds`. Use the upload or project asset payload.
+- If a request depends on subtitles, prefer a real `caption` asset plus a `captions` item instead of simulating subtitles with dozens of manually timed text items.