[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8QZ59TP9FJF0JH89X9ASR":3,"skill-same:01M7C8QZ59TP9FJF0JH89X9ASR":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7C8QZ59TP9FJF0JH89X9ASR","video-maker-brand",null,"Create or reuse the Video Maker brand of the project open in this session — name, spoken name for the voice, tagline, a 4-color palette with measured contrast, logo with transparency, fonts, voice and music — derived from the repository's own files (README, landing copy, CSS, Tailwind or theme config, web manifest, logo assets). Use it before producing any video with Video Maker, or when the user asks to set up, fix or change the brand, colors, logo or voice of their videos.","e-burgos\u002Fvideo-maker","e-burgos","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F71472902?v=4","01M728XDZXTGQMP76CXHXWT7B6","EstebanBurgos","01M7C8QX5RHWXAXPMG7A62T347",0,"MIT","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fplugins\u002Fvideo-maker\u002Fskills\u002Fvideo-maker-brand\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: video-maker-brand\ndescription: Create or reuse the Video Maker brand of the project open in this session — name, spoken name for the voice, tagline, a 4-color palette with measured contrast, logo with transparency, fonts, voice and music — derived from the repository's own files (README, landing copy, CSS, Tailwind or theme config, web manifest, logo assets). Use it before producing any video with Video Maker, or when the user asks to set up, fix or change the brand, colors, logo or voice of their videos.\n---\n\n# Video Maker brand\n\nEvery video uses a brand of the studio: it gives the colors, fonts, logo, intro\u002Foutro look, voice and\nmusic bank. Your job is to get a correct brand for **this** project with the least effort for the user.\n\nTalk to the user in their language and show the brand as a short visual summary (name, colors as hex\nswatches, logo file, font, voice described in words), never as JSON.\n\nField reference of the manifest: `..\u002Fvideo-maker\u002Freferences\u002Fbrand.md` (schema:\n`..\u002Fvideo-maker\u002Freferences\u002Fschemas\u002Fbrand.schema.json`). Derivation details and edge cases:\n`references\u002Fderiving-a-brand.md`.\n\n## 1. Reuse first\n\n1. `list_brands`. If one matches the product (same name or an id derived from it), `get_brand` and show it.\n2. Ask only \"use it as is, or adjust something?\". Built-in brands cannot be changed: to adjust one,\n   create a user brand with `duplicateFrom` set to it.\n3. If none matches, derive a new one (§2).\n\n## 2. Derive from the repo\n\nCollect each item with the file it came from:\n\n| Manifest field | Where it comes from |\n| --- | --- |\n| `name` | product name as the README, manifest or landing page writes it |\n| `spokenName` | the same name written the way a voice must say it (\"Acme Pay\" for \"AcmePay\", \"Jey Ess Kit\" for \"JSKit\" only if that is how people say it); ask the user when unsure. Exact tokens (package names, commands, URLs) are never spoken: they go on screen, see the motion-brief skill |\n| `tagline` | the landing hero line or the package description, ≤ 8 words |\n| `url` | the public site of the product (homepage in the package manifest, landing page); it is the default outro caption |\n| `palette.background`, `palette.accent`, `palette.accent2`, `palette.text` | CSS variables, Tailwind theme, design tokens, web manifest `theme_color` \u002F `background_color` |\n| `logo` | an SVG or PNG wordmark in the repo; must have transparency (§3) |\n| `typography.display`, `typography.body` and the `fonts` files | the families the product uses, as woff2\u002Fttf\u002Fotf files |\n| `voice.id` | a voice from `list_voices` in the audience's language |\n\n### Palette (4 colors, contrast measured)\n\n- `background`: the color most videos sit on (dark or light, from the product's own surfaces).\n- `text`: the main text color on that background.\n- `accent` and `accent2`: the two brand colors used for highlights, gradients and buttons.\n- Measure contrast with `scripts\u002Fcontrast.mjs` (WCAG ratio):\n\n  ```bash\n  node \u003Cthis skill>\u002Fscripts\u002Fcontrast.mjs '#0b1020' '#f5f7ff' '#6d5dfc' '#22d3ee'\n  ```\n\n  `text` on `background` must be ≥ 4.5; each accent on `background` ≥ 3. If a pair fails, propose the\n  closest shade that passes and say which one you changed.\n\n### Logo with transparency (pix_fmt rule)\n\nA logo without an alpha channel is drawn as a box over the video. For raster files check the pixel\nformat with `ffprobe -v error -select_streams v:0 -show_entries stream=pix_fmt -of csv=p=0 \u003Cfile>`:\n`rgba`, `bgra`, `ya8`, `pal8` or any format with an `a` has transparency; `rgb24`, `yuv420p`, `gray` do\nnot. Prefer, in this order: an SVG wordmark, a PNG with alpha ≥ 800 px wide, a square mark from the web\nmanifest. Never pick one without alpha silently: offer to go without a logo or ask for a transparent file.\nHorizontal wordmarks work better than square icons; keep the square one as the optional `isotipo`.\n\n### Voice and music\n\n- The brand manifest has no tone field. How the product talks (\"close and direct, no jargon\") belongs to\n  the brief and the script of each video, not to the brand.\n- Voice: `list_voices`; describe two candidates to the user in words (gender, accent, energy).\n  `voice.lengthScale` 1.0 is normal speed, 1.08 slightly calmer.\n- Music: a new brand starts with an empty bank, and the brief `music` field only takes ids of the\n  brand's own bank. Ways to fill it:\n  - `musicFrom` (id of another brand) only for a sub-brand of the same owner that shares its parent's\n    music. Never use it to borrow another company's bank.\n  - Tracks the user owns: `upload_brand_file` kind `music`, then `update_brand` adding the entry.\n  - Free tracks, with no download on your side: in a project of this brand run `search_free_music`\n    (each result shows title, author, license and page URL), pick one whose license is not share-alike,\n    then call `import_brand_music` with the project slug, the `resultId`, the brand `id`, an estimated\n    `bpm`, a short `mood` and optionally `videoTypes`. The studio downloads the file (mp3, wav or m4a),\n    stores it in the brand and appends the track with its `credit` (title, author, license). Use the\n    answered `track.id` in the brief.\n  - Any entry needs `id`, `file`, `credit`, `bpm` and `mood`; `drop` and `videoTypes` are optional.\n\n## 3. Propose, then create\n\nShow the summary and wait for the OK. Then:\n\n1. `create_brand` with `name` (and `id`, kebab-case starting with a letter). The studio creates a starter\n   manifest with default fonts and a generated wordmark.\n2. `upload_brand_file` for each file: kind `logo` (svg, png, webp, jpg), `font` (woff2, ttf, otf),\n   `music` (mp3, wav, m4a; a free track goes through `import_brand_music` instead), `image` (photos the scenes can use), `device` (product hardware). Each upload\n   answers the stored relative path; use exactly that path in the manifest.\n3. `get_brand`, change only what you derived, and send the **whole** manifest with `update_brand`. The\n   studio validates it and names the offending field when invalid: fix that field and send again.\n4. `get_brand` again and confirm to the user, in words, what the brand now has.\n\nNever edit a built-in brand, never delete a brand (the user does that in the studio) and never upload\nfiles the repo does not own the rights to (a client's logo, a font without a license file).\n\n## 4. Optional parts that make videos better\n\n- `images`: photos the motion scenes may use, each with a one-line `caption` saying what it shows (the\n  storyboard AI reads the caption, it does not see the photo).\n- `devices`: when the product runs on hardware (a screen, a kiosk, a terminal, a tablet stand), upload a\n  clean product photo as kind `device` and describe its screen area as a 4-point polygon so scenes can put\n  the product's UI inside it. See `references\u002Fderiving-a-brand.md` §4.\n- `bumpers`: limit the intro\u002Foutro looks to the ones that suit the brand (`bumpers.backgrounds`,\n  `bumpers.reveals`), and set `bumpers.outroCaption` if the outro should type something other than the\n  url.\n","# Video Maker brand\n\nEvery video uses a brand of the studio: it gives the colors, fonts, logo, intro\u002Foutro look, voice and\nmusic bank. Your job is to get a correct brand for **this** project with the least effort for the user.\n\nTalk to the user in their language and show the brand as a short visual summary (name, colors as hex\nswatches, logo file, font, voice described in words), never as JSON.\n\nField reference of the manifest: `..\u002Fvideo-maker\u002Freferences\u002Fbrand.md` (schema:\n`..\u002Fvideo-maker\u002Freferences\u002Fschemas\u002Fbrand.schema.json`). Derivation details and edge cases:\n`references\u002Fderiving-a-brand.md`.\n\n## 1. Reuse first\n\n1. `list_brands`. If one matches the product (same name or an id derived from it), `get_brand` and show it.\n2. Ask only \"use it as is, or adjust something?\". Built-in brands cannot be changed: to adjust one,\n   create a user brand with `duplicateFrom` set to it.\n3. If none matches, derive a new one (§2).\n\n## 2. Derive from the repo\n\nCollect each item with the file it came from:\n\n| Manifest field | Where it comes from |\n| --- | --- |\n| `name` | product name as the README, manifest or landing page writes it |\n| `spokenName` | the same name written the way a voice must say it (\"Acme Pay\" for \"AcmePay\", \"Jey Ess Kit\" for \"JSKit\" only if that is how people say it); ask the user when unsure. Exact tokens (package names, commands, URLs) are never spoken: they go on screen, see the motion-brief skill |\n| `tagline` | the landing hero line or the package description, ≤ 8 words |\n| `url` | the public site of the product (homepage in the package manifest, landing page); it is the default outro caption |\n| `palette.background`, `palette.accent`, `palette.accent2`, `palette.text` | CSS variables, Tailwind theme, design tokens, web manifest `theme_color` \u002F `background_color` |\n| `logo` | an SVG or PNG wordmark in the repo; must have transparency (§3) |\n| `typography.display`, `typography.body` and the `fonts` files | the families the product uses, as woff2\u002Fttf\u002Fotf files |\n| `voice.id` | a voice from `list_voices` in the audience's language |\n\n### Palette (4 colors, contrast measured)\n\n- `background`: the color most videos sit on (dark or light, from the product's own surfaces).\n- `text`: the main text color on that background.\n- `accent` and `accent2`: the two brand colors used for highlights, gradients and buttons.\n- Measure contrast with `scripts\u002Fcontrast.mjs` (WCAG ratio):\n\n  ```bash\n  node \u003Cthis skill>\u002Fscripts\u002Fcontrast.mjs '#0b1020' '#f5f7ff' '#6d5dfc' '#22d3ee'\n  ```\n\n  `text` on `background` must be ≥ 4.5; each accent on `background` ≥ 3. If a pair fails, propose the\n  closest shade that passes and say which one you changed.\n\n### Logo with transparency (pix_fmt rule)\n\nA logo without an alpha channel is drawn as a box over the video. For raster files check the pixel\nformat with `ffprobe -v error -select_streams v:0 -show_entries stream=pix_fmt -of csv=p=0 \u003Cfile>`:\n`rgba`, `bgra`, `ya8`, `pal8` or any format with an `a` has transparency; `rgb24`, `yuv420p`, `gray` do\nnot. Prefer, in this order: an SVG wordmark, a PNG with alpha ≥ 800 px wide, a square mark from the web\nmanifest. Never pick one without alpha silently: offer to go without a logo or ask for a transparent file.\nHorizontal wordmarks work better than square icons; keep the square one as the optional `isotipo`.\n\n### Voice and music\n\n- The brand manifest has no tone field. How the product talks (\"close and direct, no jargon\") belongs to\n  the brief and the script of each video, not to the brand.\n- Voice: `list_voices`; describe two candidates to the user in words (gender, accent, energy).\n  `voice.lengthScale` 1.0 is normal speed, 1.08 slightly calmer.\n- Music: a new brand starts with an empty bank, and the brief `music` field only takes ids of the\n  brand's own bank. Ways to fill it:\n  - `musicFrom` (id of another brand) only for a sub-brand of the same owner that shares its parent's\n    music. Never use it to borrow another company's bank.\n  - Tracks the user owns: `upload_brand_file` kind `music`, then `update_brand` adding the entry.\n  - Free tracks, with no download on your side: in a project of this brand run `search_free_music`\n    (each result shows title, author, license and page URL), pick one whose license is not share-alike,\n    then call `import_brand_music` with the project slug, the `resultId`, the brand `id`, an estimated\n    `bpm`, a short `mood` and optionally `videoTypes`. The studio downloads the file (mp3, wav or m4a),\n    stores it in the brand and appends the track with its `credit` (title, author, license). Use the\n    answered `track.id` in the brief.\n  - Any entry needs `id`, `file`, `credit`, `bpm` and `mood`; `drop` and `videoTypes` are optional.\n\n## 3. Propose, then create\n\nShow the summary and wait for the OK. Then:\n\n1. `create_brand` with `name` (and `id`, kebab-case starting with a letter). The studio creates a starter\n   manifest with default fonts and a generated wordmark.\n2. `upload_brand_file` for each file: kind `logo` (svg, png, webp, jpg), `font` (woff2, ttf, otf),\n   `music` (mp3, wav, m4a; a free track goes through `import_brand_music` instead), `image` (photos the scenes can use), `device` (product hardware). Each upload\n   answers the stored relative path; use exactly that path in the manifest.\n3. `get_brand`, change only what you derived, and send the **whole** manifest with `update_brand`. The\n   studio validates it and names the offending field when invalid: fix that field and send again.\n4. `get_brand` again and confirm to the user, in words, what the brand now has.\n\nNever edit a built-in brand, never delete a brand (the user does that in the studio) and never upload\nfiles the repo does not own the rights to (a client's logo, a font without a license file).\n\n## 4. Optional parts that make videos better\n\n- `images`: photos the motion scenes may use, each with a one-line `caption` saying what it shows (the\n  storyboard AI reads the caption, it does not see the photo).\n- `devices`: when the product runs on hardware (a screen, a kiosk, a terminal, a tablet stand), upload a\n  clean product photo as kind `device` and describe its screen area as a 4-point polygon so scenes can put\n  the product's UI inside it. See `references\u002Fderiving-a-brand.md` §4.\n- `bumpers`: limit the intro\u002Foutro looks to the ones that suit the brand (`bumpers.backgrounds`,\n  `bumpers.reveals`), and set `bumpers.outroCaption` if the outro should type something other than the\n  url.\n",{"name":5,"description":7},"main","c3d54dc0db791f99e689a6b86ece5b6099b12809","plugins\u002Fvideo-maker\u002Fskills\u002Fvideo-maker-brand","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker","https:\u002F\u002Fgithub.com\u002Fe-burgos","https:\u002F\u002Festebanburgos.com.ar\u002F","More than 12 years of experience in different technology companies, I am oriented to design and develop productive and profitable software solutions. ","2026-11-15 03:24:14",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add e-burgos\u002Fvideo-maker --skill video-maker-brand",{"tool":38,"command":39},"bunx","bunx skills add e-burgos\u002Fvideo-maker --skill video-maker-brand",{"tool":41,"command":42},"pnpm","pnpm dlx skills add e-burgos\u002Fvideo-maker --skill video-maker-brand","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fplugins\u002Fvideo-maker\u002Fskills\u002Fvideo-maker-brand\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fderiving-a-brand.md","REFERENCE","参考文档",4032,"https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fplugins\u002Fvideo-maker\u002Fskills\u002Fvideo-maker-brand\u002Freferences\u002Fderiving-a-brand.md",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fcontrast.mjs","SCRIPT","脚本",2046,"https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fplugins\u002Fvideo-maker\u002Fskills\u002Fvideo-maker-brand\u002Fscripts\u002Fcontrast.mjs",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7C8WJD3Y1T31YNSK5BFZKJ1","video-producer","Productor de video conversacional del Video Maker Studio. Parte de un prompt del usuario y del material que haya en `media\u002F\u003Cslug>\u002Fraw\u002F` (videos, fotos, pantallas grabadas, locución, música, guion, o nada), acuerda con el usuario qué video hacer y lo produce con las herramientas ya implementadas (guion, voz Piper, montaje, captions, mezcla, render), buscando medios libres solo cuando el usuario lo pide o no hay material. Invocar con `\u002Fvideo-producer media\u002F\u003Cslug>` o cuando el usuario pida \"armá\u002Fgenerá un video\" sobre un proyecto.","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fsdd\u002Fskills\u002Fvideo-producer\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7C8WDBXCXT0K71MXSX11HVX","tucu-ui-pro","Usar siempre que un frontend React\u002FNext use (o vaya a usar) @e-burgos\u002Ftucu-ui — montarlo en Vite, Next 16 o una app con Tailwind propio, elegir ThemeProvider\u002Flayout\u002Fpreset, tematizar con customPaletteColor y tokens --tucu-*, elegir el componente correcto con sus props válidos y esquivar las trampas que rompen en runtime, con o sin el MCP tucu-ui conectado.","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fsdd\u002Fskills\u002Ftucu-ui-pro\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7C8W9MEXVQZPN9EP391J9YN","setup-graphify","Instala y configura graphify (grafo de conocimiento del repo) para un dev que lo quiera usar. Elige un backend gratuito, valida el modelo con una medición real y construye el primer grafo. Invocar solo si el dev pide habilitar graphify.","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fsdd\u002Fskills\u002Fsetup-graphify\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7C8W3NAKN7QQWWCGZ2GH9M7","sdd-steward","Conserje del kit SDD - puerta de entrada para status del harness, actualización de la librería, arranque de ideas, costos y salud de los arneses. Clasifica cualquier pedido con la tabla de ruteo, ejecuta solo lo que no tiene otro dueño y delega el resto sin bypassear gates. Invocar ante cualquier pregunta u operación sobre el kit en sí.","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fsdd\u002Fskills\u002Fsdd-steward\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7C8W0M5MPXACHFBRHRCJE58","sdd-reviewer","Skill del Agente Reviewer SDD. Valida la calidad de todo el output del ciclo y ejecuta los gates de cierre. Invocar cuando todas las tasks de implementación del ciclo estén completas.","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fsdd\u002Fskills\u002Fsdd-reviewer\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7C8VY27546VQSRY8E3AQ7XN","sdd-planner","Skill del Agente Planner SDD. Convierte historias de usuario en tasks técnicas ordenadas y estimadas. Invocar después del Funcional, en paralelo con el Arquitecto.","https:\u002F\u002Fgithub.com\u002Fe-burgos\u002Fvideo-maker\u002Fblob\u002Fmain\u002Fsdd\u002Fskills\u002Fsdd-planner\u002FSKILL.md",[],[]]