@kolbo/kolbo-code-linux-x64 - npm Package Compare versions

Comparing version

2.4.1

2.4.2

+1

-1

package.json

		{
		"name": "@kolbo/kolbo-code-linux-x64",
		"version": "2.4.1",
		"version": "2.4.2",
		"os": [
		@@ -5,0 +5,0 @@ "linux"

+8

-6

skills/kolbo/references/workflows/media-library.md

		@@ -52,2 +52,3 @@ # Media Library
		\| "Move this to project X" \| `move_media` \|
		\| "Move this whole session/chat to project X" / "this landed in the wrong project" \| `move_session` (moves the session + ALL its media in one call — prefer over per-item `move_media`) \|
		\| "Clean up old [type]" / "delete everything from [time period]" \| `list_media` (find ids) → confirm → `bulk_delete_media` \|
		@@ -72,7 +73,8 @@ \| "Restore all from trash" \| `list_media include_deleted=true` → `bulk_restore_media` \|
		3. `bulk_move_media` is atomic. If you get a "not all items owned by you" error, do NOT retry partially. Surface the error to the user and let them pick a smaller batch.
		4. Prefer `list_media` filters over post-filtering. Pass `project_id` / `folder_id` / `category` / `type` / `search` to the backend; don't fetch the whole library and filter client-side.
		5. `is_favorited` is per-user. On shared projects, an item can be favorited by you and not by your teammates — the value reflects the calling user only.
		6. "Empty trash" flow: `list_media` with `include_deleted=true` → show the count → confirm → `bulk_permanently_delete_media`. Never call the bulk-permanent endpoint without listing first so the user knows the scope.
		7. Bulk caps: 1000 ids for `bulk_delete_media` / `bulk_restore_media` / `bulk_permanently_delete_media` / `bulk_move_media`; 500 ids for `add_media_to_folder` / `remove_media_from_folder`. Split larger jobs into successive calls.
		8. Folder share resolution: `share_media_folder` takes emails; users not found come back in `not_found`. Report those to the user — don't assume the share succeeded silently. Members can list/add/remove items but cannot delete the folder or reshare it.
		9. `get_media` accepts a generation_id as a fallback for the `media_id` arg, so you can chase down items the user references by their original generation rather than by library id.
		4. `upload_media` accepts `project_id` — when the user works in a named project, pass it on uploads too (resolve via `list_projects`), or the file lands outside the project.
		5. Prefer `list_media` filters over post-filtering. Pass `project_id` / `folder_id` / `category` / `type` / `search` to the backend; don't fetch the whole library and filter client-side.
		6. `is_favorited` is per-user. On shared projects, an item can be favorited by you and not by your teammates — the value reflects the calling user only.
		7. "Empty trash" flow: `list_media` with `include_deleted=true` → show the count → confirm → `bulk_permanently_delete_media`. Never call the bulk-permanent endpoint without listing first so the user knows the scope.
		8. Bulk caps: 1000 ids for `bulk_delete_media` / `bulk_restore_media` / `bulk_permanently_delete_media` / `bulk_move_media`; 500 ids for `add_media_to_folder` / `remove_media_from_folder`. Split larger jobs into successive calls.
		9. Folder share resolution: `share_media_folder` takes emails; users not found come back in `not_found`. Report those to the user — don't assume the share succeeded silently. Members can list/add/remove items but cannot delete the folder or reshare it.
		10. `get_media` accepts a generation_id as a fallback for the `media_id` arg, so you can chase down items the user references by their original generation rather than by library id.

+18

-0

skills/kolbo/references/workflows/visual-dna.md

		@@ -234,1 +234,19 @@ # Visual DNA — Character / Style Consistency
		- Video DNA support is limited to `generate_elements` (Seedance 2, Kling O3 Reference, Grok Imagine). `generate_video`, `generate_video_from_image`, and `generate_first_last_frame` all ignore `visual_dna_ids` — for character-consistent video, route through `generate_elements`.


		## Folders — organizing a large cast

		Tools: `list_visual_dna_folders`, `create_visual_dna_folder` (`name`, optional hex `color`), `update_visual_dna_folder`, `delete_visual_dna_folder`, `move_visual_dna_to_folder`.

		- Folders are user-scoped and flat; names are unique per user (409 on duplicate).
		- Personal DNAs only — global presets must be imported first; organization DNAs cannot go in personal folders (server rejects with a clear message).
		- Deleting a folder never deletes DNAs — contents move back to root (`items_moved_to_root` in the response). Mention this instead of asking for confirmation on non-empty folders.
		- Creating many characters for one production? Create the folder FIRST, then `move_visual_dna_to_folder` each DNA right after `create_visual_dna` — don't leave a big cast unsorted at root.
		- To list a folder's contents: `list_visual_dnas` and filter by each profile's `folder_id` (there is no server-side folder filter).

		## Character sheet — offer it for character DNAs

		`generate_character_sheet` builds a multi-angle turnaround from reference image URLs — the strongest consistency booster for a character DNA. It CHARGES CREDITS, so:
		- When the user is about to create a character DNA, proactively OFFER it: "want me to generate a character sheet first? It makes the character far more consistent and costs a few credits." Run it only on a yes.
		- Flow: `generate_character_sheet {image_urls}` → show the sheet → `create_visual_dna {name, images, character_sheet_url: <url>}`.
		- For non-character DNAs (style/product/environment), skip it.

+22

-4

skills/kolbo/SKILL.md

		---
		version: 0.5.1
		version: 0.7.1
		name: kolbo
		@@ -10,3 +10,4 @@ description: \|
		marketplace cards), Creative Director (multi-scene batches), HTML artifact
		publishing (presentations, landing pages, dashboards), and the App Builder.
		publishing (presentations, landing pages, dashboards), AI Docs (project
		documents you author and share), and the App Builder.

		@@ -17,3 +18,4 @@ Use when the user wants to generate, create, make, edit, animate, or
		listings, presentations, landing pages, dashboards, or 'build me an app';
		or to reuse a character or brand (Visual DNA, brand kits).
		to reuse a character or brand (Visual DNA, brand kits); or to save a written
		plan / brief / script / research doc into their Kolbo project (AI Docs).

		@@ -116,5 +118,12 @@ NOT for: video editing / FFmpeg (use video-production), motion graphics
		\| `upload_media` / `list_media` / `get_media` / `get_media_stats` / `favorite_media` / `unfavorite_media` / `delete_media` / `restore_media` / `permanently_delete_media` / `move_media` / `bulk__media` / `_media_folder` \| Media library — see `workflows/media-library.md` \|
		\| `create_visual_dna` / `list_visual_dnas` / `get_visual_dna` / `delete_visual_dna` \| Visual DNA — see `workflows/visual-dna.md` \|
		\| `create_visual_dna` / `generate_character_sheet` / `list_visual_dnas` / `get_visual_dna` / `delete_visual_dna` / `*_visual_dna_folder` (5 folder tools) \| Visual DNA (+ character sheet, character folders) — see `workflows/visual-dna.md` \|
		\| `list_moodboards` / `get_moodboard` / `list_presets` \| Style overlays \|
		\| `search_stock_media` / `get_stock_sources` / `get_stock_categories` / `get_stock_collections` / `get_stock_asset` / `analyze_script_for_stock` / `import_stock_asset` \| Stock library (free, no credits) — EXISTING photos / videos / 3D / SFX / music. For stock music use `search_stock_media` with `mediaType: "music"` (semantic vibe query, e.g. "uplifting corporate background") → `get_stock_asset` for downloads. The older `*_music_library` tools are deprecated adapters over this — prefer the stock tools. \|
		\| `list_projects` / `move_session` \| Projects: resolve a project NAME → the `project_id` you pass on generation/upload/doc calls; `move_session` relocates a whole session + its media when work landed in the wrong project. NOT the same as `app_builder_list_projects`. See "Projects — Where Work Lands" below. \|
		\| `create_project` / `update_project` / `archive_project` / `unarchive_project` / `list_sessions` \| Project lifecycle + session inventory (deletion stays in-app). Create a project when the user starts new work, then pass its id on EVERY call. \|
		\| `add_project_context` / `list_project_context` / `delete_project_context` / `get_project_profile` / `regenerate_project_profile` \| Project knowledge base (RAG): feed scripts/URLs/notes; `get_project_profile` = the living brief — read it to ground work in the project \|
		\| `create_moodboard` / `update_moodboard` / `delete_moodboard` \| Moodboards from image URLs → AI master style prompt → pass `moodboard_id` to generation tools \|
		\| `clone_voice` / `import_elevenlabs_voice` / `delete_voice` \| Custom voices (clone CHARGES CREDITS — confirm first; new voices show in `list_voices`) \|
		\| `trim_video` \| Frame-accurate trim of a Kolbo-hosted video (tool waits and returns the URL). `edit_video` also gained `remove_background`. \|
		\| `create_doc` / `list_docs` / `get_doc` / `update_doc` / `share_doc` / `delete_doc` \| AI Docs (Magic Pad): YOU author full HTML documents (plans, briefs, scripts, research) saved into the user's project, editable in the Kolbo app. `share_doc` returns a public link. `update_doc` content replaces the WHOLE doc — `get_doc` first. \|
		\| `chat_send_message` / `chat_list_conversations` / `chat_get_messages` \| Kolbo chat with optional `media_urls` (up to 10 per call) \|
		@@ -166,2 +175,11 @@ \| `app_builder_*` (9 tools) \| Full React app generation — see `workflows/app-builder.md` \|

		## 📁 Projects — Where Work Lands (CRITICAL)

		Everything in Kolbo — sessions, generations, media, docs — lives inside a PROJECT. Getting this wrong is the #1 user complaint ("my work went to the wrong project").

		1. User names a project ("in my Acme project", "for the film") → call `list_projects` ONCE to resolve the name to an ObjectId, then pass that id as `project_id` on EVERY subsequent `generate_` / `upload_media` / `create_doc` / `chat_send_message` call in the conversation. It is per-call, NOT sticky* — any call that omits it silently lands in the default "API Generations" bucket (`is_default: true`).
		2. No project mentioned → omit `project_id`; the default bucket is correct. Don't ask unless intent is ambiguous.
		3. `list_projects` ≠ `app_builder_list_projects` — the latter scopes App Builder coding sessions only.
		4. Work landed in the wrong project? MOVE it, never regenerate: `move_session` relocates a whole session + all its media (works for any session type — the `session_id` from generation responses, chats, transcriptions); `move_media` / `bulk_move_media` / `move_folder_contents` relocate individual media items.

		## Cost Awareness — Quick Rules
		@@ -168,0 +186,0 @@

+1

-1

skills/kolbo/VERSION

		@@ -1,1 +0,1 @@
		0.5.1
		0.7.1

bin/kolbo

Sorry, the diff of this file is not supported yet

		@@ -52,2 +52,3 @@ # Media Library
		\| "Move this to project X" \| `move_media` \|
		\| "Move this whole session/chat to project X" / "this landed in the wrong project" \| `move_session` (moves the session + ALL its media in one call — prefer over per-item `move_media`) \|
		\| "Clean up old [type]" / "delete everything from [time period]" \| `list_media` (find ids) → confirm → `bulk_delete_media` \|
		@@ -72,7 +73,8 @@ \| "Restore all from trash" \| `list_media include_deleted=true` → `bulk_restore_media` \|
		3. `bulk_move_media` is atomic. If you get a "not all items owned by you" error, do NOT retry partially. Surface the error to the user and let them pick a smaller batch.
		4. Prefer `list_media` filters over post-filtering. Pass `project_id` / `folder_id` / `category` / `type` / `search` to the backend; don't fetch the whole library and filter client-side.
		5. `is_favorited` is per-user. On shared projects, an item can be favorited by you and not by your teammates — the value reflects the calling user only.
		6. "Empty trash" flow: `list_media` with `include_deleted=true` → show the count → confirm → `bulk_permanently_delete_media`. Never call the bulk-permanent endpoint without listing first so the user knows the scope.
		7. Bulk caps: 1000 ids for `bulk_delete_media` / `bulk_restore_media` / `bulk_permanently_delete_media` / `bulk_move_media`; 500 ids for `add_media_to_folder` / `remove_media_from_folder`. Split larger jobs into successive calls.
		8. Folder share resolution: `share_media_folder` takes emails; users not found come back in `not_found`. Report those to the user — don't assume the share succeeded silently. Members can list/add/remove items but cannot delete the folder or reshare it.
		9. `get_media` accepts a generation_id as a fallback for the `media_id` arg, so you can chase down items the user references by their original generation rather than by library id.
		4. `upload_media` accepts `project_id` — when the user works in a named project, pass it on uploads too (resolve via `list_projects`), or the file lands outside the project.
		5. Prefer `list_media` filters over post-filtering. Pass `project_id` / `folder_id` / `category` / `type` / `search` to the backend; don't fetch the whole library and filter client-side.
		6. `is_favorited` is per-user. On shared projects, an item can be favorited by you and not by your teammates — the value reflects the calling user only.
		7. "Empty trash" flow: `list_media` with `include_deleted=true` → show the count → confirm → `bulk_permanently_delete_media`. Never call the bulk-permanent endpoint without listing first so the user knows the scope.
		8. Bulk caps: 1000 ids for `bulk_delete_media` / `bulk_restore_media` / `bulk_permanently_delete_media` / `bulk_move_media`; 500 ids for `add_media_to_folder` / `remove_media_from_folder`. Split larger jobs into successive calls.
		9. Folder share resolution: `share_media_folder` takes emails; users not found come back in `not_found`. Report those to the user — don't assume the share succeeded silently. Members can list/add/remove items but cannot delete the folder or reshare it.
		10. `get_media` accepts a generation_id as a fallback for the `media_id` arg, so you can chase down items the user references by their original generation rather than by library id.

		---
		version: 0.5.1
		version: 0.7.1
		name: kolbo
		@@ -10,3 +10,4 @@ description: \|
		marketplace cards), Creative Director (multi-scene batches), HTML artifact
		publishing (presentations, landing pages, dashboards), and the App Builder.
		publishing (presentations, landing pages, dashboards), AI Docs (project
		documents you author and share), and the App Builder.

		@@ -17,3 +18,4 @@ Use when the user wants to generate, create, make, edit, animate, or
		listings, presentations, landing pages, dashboards, or 'build me an app';
		or to reuse a character or brand (Visual DNA, brand kits).
		to reuse a character or brand (Visual DNA, brand kits); or to save a written
		plan / brief / script / research doc into their Kolbo project (AI Docs).

		@@ -116,5 +118,12 @@ NOT for: video editing / FFmpeg (use video-production), motion graphics
		\| `upload_media` / `list_media` / `get_media` / `get_media_stats` / `favorite_media` / `unfavorite_media` / `delete_media` / `restore_media` / `permanently_delete_media` / `move_media` / `bulk__media` / `_media_folder` \| Media library — see `workflows/media-library.md` \|
		\| `create_visual_dna` / `list_visual_dnas` / `get_visual_dna` / `delete_visual_dna` \| Visual DNA — see `workflows/visual-dna.md` \|
		\| `create_visual_dna` / `generate_character_sheet` / `list_visual_dnas` / `get_visual_dna` / `delete_visual_dna` / `*_visual_dna_folder` (5 folder tools) \| Visual DNA (+ character sheet, character folders) — see `workflows/visual-dna.md` \|
		\| `list_moodboards` / `get_moodboard` / `list_presets` \| Style overlays \|
		\| `search_stock_media` / `get_stock_sources` / `get_stock_categories` / `get_stock_collections` / `get_stock_asset` / `analyze_script_for_stock` / `import_stock_asset` \| Stock library (free, no credits) — EXISTING photos / videos / 3D / SFX / music. For stock music use `search_stock_media` with `mediaType: "music"` (semantic vibe query, e.g. "uplifting corporate background") → `get_stock_asset` for downloads. The older `*_music_library` tools are deprecated adapters over this — prefer the stock tools. \|
		\| `list_projects` / `move_session` \| Projects: resolve a project NAME → the `project_id` you pass on generation/upload/doc calls; `move_session` relocates a whole session + its media when work landed in the wrong project. NOT the same as `app_builder_list_projects`. See "Projects — Where Work Lands" below. \|
		\| `create_project` / `update_project` / `archive_project` / `unarchive_project` / `list_sessions` \| Project lifecycle + session inventory (deletion stays in-app). Create a project when the user starts new work, then pass its id on EVERY call. \|
		\| `add_project_context` / `list_project_context` / `delete_project_context` / `get_project_profile` / `regenerate_project_profile` \| Project knowledge base (RAG): feed scripts/URLs/notes; `get_project_profile` = the living brief — read it to ground work in the project \|
		\| `create_moodboard` / `update_moodboard` / `delete_moodboard` \| Moodboards from image URLs → AI master style prompt → pass `moodboard_id` to generation tools \|
		\| `clone_voice` / `import_elevenlabs_voice` / `delete_voice` \| Custom voices (clone CHARGES CREDITS — confirm first; new voices show in `list_voices`) \|
		\| `trim_video` \| Frame-accurate trim of a Kolbo-hosted video (tool waits and returns the URL). `edit_video` also gained `remove_background`. \|
		\| `create_doc` / `list_docs` / `get_doc` / `update_doc` / `share_doc` / `delete_doc` \| AI Docs (Magic Pad): YOU author full HTML documents (plans, briefs, scripts, research) saved into the user's project, editable in the Kolbo app. `share_doc` returns a public link. `update_doc` content replaces the WHOLE doc — `get_doc` first. \|
		\| `chat_send_message` / `chat_list_conversations` / `chat_get_messages` \| Kolbo chat with optional `media_urls` (up to 10 per call) \|
		@@ -166,2 +175,11 @@ \| `app_builder_*` (9 tools) \| Full React app generation — see `workflows/app-builder.md` \|

		## 📁 Projects — Where Work Lands (CRITICAL)

		Everything in Kolbo — sessions, generations, media, docs — lives inside a PROJECT. Getting this wrong is the #1 user complaint ("my work went to the wrong project").

		1. User names a project ("in my Acme project", "for the film") → call `list_projects` ONCE to resolve the name to an ObjectId, then pass that id as `project_id` on EVERY subsequent `generate_` / `upload_media` / `create_doc` / `chat_send_message` call in the conversation. It is per-call, NOT sticky* — any call that omits it silently lands in the default "API Generations" bucket (`is_default: true`).
		2. No project mentioned → omit `project_id`; the default bucket is correct. Don't ask unless intent is ambiguous.
		3. `list_projects` ≠ `app_builder_list_projects` — the latter scopes App Builder coding sessions only.
		4. Work landed in the wrong project? MOVE it, never regenerate: `move_session` relocates a whole session + all its media (works for any session type — the `session_id` from generation responses, chats, transcriptions); `move_media` / `bulk_move_media` / `move_folder_contents` relocate individual media items.

		## Cost Awareness — Quick Rules
		@@ -168,0 +186,0 @@

@kolbo/kolbo-code-linux-x64 - npm Package Compare versions

Improved metrics