[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6VVZJR7K6ZFD0MACV7S8D":3,"skill-same:01M7F6VVZJR7K6ZFD0MACV7S8D":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F6VVZJR7K6ZFD0MACV7S8D","part",null,"Runs ONE Part of an already planned phase item by item, with Opus reviewers and a gate, then STOPS. Use for \"Phase NNN Part X\", \"run the part\", \"execute part\", \"rode a parte\", \"toca a parte\", with or without \u002Fgoal.","stage2dev\u002Ftune-up","stage2dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F205088513?v=4","01M7F6TJSVA061K0AHEMXHHZAA","01M7F6TJTDN359R5QXK9C5RAZD",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Fskills\u002Fpart\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: part\ndescription: Runs ONE Part of an already planned phase item by item, with Opus reviewers and a gate, then STOPS. Use for \"Phase NNN Part X\", \"run the part\", \"execute part\", \"rode a parte\", \"toca a parte\", with or without \u002Fgoal.\nargument-hint: \"\u003CNNN> \u003CPart>  e.g. 184 B\"\nallowed-tools: Bash(sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info), Bash(graphify update .), Bash(command -v graphify)\n---\n\n# Run a Part\n\nContext: !`sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info`\n\nRequest: $ARGUMENTS\n\nThe JSON above is the context. Write to the user in its `language`, honoring `reply_style`; final answer short. Use document names from `names` (`goal`, `progress`, `research`, `later`, `backlog`, `need_you`, `part_closed`), never literal. Models\u002Feffort per role from `models`; if missing, use the table defaults.\n\nYou (main session, highest effort) coordinate and judge; you do not write the items' code. One Part per conversation: at the end, STOP.\n\n## Roles\n\n| Role | Agent | Default model | Effort |\n|---|---|---|---|\n| Map \u002F recheck lines | `tune-up:mapper` | haiku | medium |\n| Pick skills for an item | `tune-up:skill-finder` | haiku | medium |\n| Simple item (screen, text, simple route, test, doc) | `tune-up:executor-sonnet` | sonnet | medium |\n| Risky item (migration, trigger, access rules, RPC, worker, money, auth, external sending, concurrency) | `tune-up:executor-opus` | opus | medium |\n| Review the diff | `tune-up:reviewer-failures`, `tune-up:reviewer-database`, `tune-up:reviewer-security` | opus | high |\n| Definition of done | `tune-up:checker` | haiku | medium |\n| Edit goal\u002Fprogress\u002Fdocs | `tune-up:writer` | sonnet | medium |\n\n- Independent agents go in ONE message, in background. Do not wait awake.\n- Pass `model` and `effort` on every call. Never a model in `forbidden_subagent_models` (default `[\"fable\"]`).\n- Production writes, customer messages, ads: only with the owner's explicit request IN THE TURN. A \"yes\" to another question does not count.\n- Planning documents (goal, progress, later, research, handoff) live in the LOCAL `\u003Cplans_dir>`, the main checkout, as absolute paths. Read and write them only there, never only in the worktree: the worktree copy is invisible to the other sessions and to `\u002Ftune-up:status`. Each session writes only its own Part's lines. Before the PR (Step 6), copy the phase files from the local folder into the worktree at the same relative path and commit them on the Part branch, so the PR carries them. The local copy stays the source.\n- Commit of an item on the Part branch: yes. Push and PR only if this Part's request (message or `\u002Fgoal` condition) says push\u002FPR; otherwise leave all ready and write `names.need_you` may I push and open the PR? Branch cut from the day's `origin\u002F\u003Cmain>`. Merged PR = dead branch: a post-merge fix is a NEW PR from main; never stacked PRs.\n- Never `git stash -u`. `git add` by file name only. Preserve existing changes and untracked files.\n- Read the project profile (`profile_path`): definition of done, production, pitfalls.\n\n## Workflow scripts\n\n- If you orchestrate with the Workflow tool, start from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002Fworkflow-template.js`.\n- Every `agent()` carries a literal `agentType` from the table above, plus `model` and `effort`. Never let an agent inherit the session model.\n- A generic agent (no `agentType`, or `general-purpose`) starts with about three times the context of a `tune-up:*` agent. Use one only for work that needs MCP tools, a browser or images, and mark the line above with `\u002F\u002F tune-up: allow-generic \u003Creason>`. The guard warns (or blocks, with `\"workflow_generic\": \"block\"` in the profile config) otherwise.\n- Review loop in a script: at most 2 fix rounds per item; after each fix only the reviewers that rejected run again; CRITICAL\u002FHIGH left after the review that follows the second fix -> `names.need_you`, never a third fix.\n- A `null` result or a \"hit your ... limit\" reply is an interrupted item: do not relaunch it and do not count it as done; check git before resuming.\n\n## Step 1 - Understand and check prerequisites\n\n1. Read ONLY the Part's sections, the criteria C and the Execution section of the goal document, plus progress. Research is spot consultation.\n2. Check `origin\u002F\u003Cmain>`, `gh pr list` and `git status`: another session may have done something unrecorded. A sibling Part closed in the local progress counts as done for the \"Parts\" table, even if it is not merged; its merge\u002Fmigration is the owner's prerequisite.\n3. A prerequisite in the \"Parts\" table that depends on the owner (decision, merge, deploy, migration): say ONCE `names.need_you` + the exact action and STOP (with `\u002Fgoal`, ask for `\u002Fgoal clear`). Never \"still waiting\" in a loop.\n\n## Step 2 - Base and map\n\n1. `git fetch`; your OWN worktree from `origin\u002F\u003Cmain>` with the Part branch. Before committing: `git branch --show-current`.\n2. One `tune-up:mapper` per item group, ALL groups in one message, rechecks EVERY line cited in the goal against today's base and returns current snippets (`file:line`). Line moved: adjust the work order, not the goal; note it in progress. In that same message call `tune-up:skill-finder` (item text, absolute `info.catalog_path`) only when `info.catalog_path` is set and the goal item has no Skills.\n3. Item that reads, filters or deletes EXISTING data: while the mappers run, the main session runs 1-3 read-only queries on production (counts per status\u002Fshape, NULL counts, lengths, min\u002Fmax dates). Aggregates and shapes only, never a raw value of a phone, name, e-mail or message. Paste the result under REAL DATA in the order; never copy it to progress or to a test fixture.\n\n## Step 3 - One item at a time\n\nBuild the work order from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002Fwork-order.md` and dispatch in background. \"Skills to read\" ALWAYS includes every entry of `info.pitfall_skills` whose `paths` globs match the absolute path of an owned file (worktree + path, no `:lines` suffix; `**\u002F` also matches zero folders), with or without a catalog, plus the goal's \"Skills\"; the skill-finder (Step 2) only adds extras. A handoff whose json `skills_read` misses a matched pitfall skill: note it in progress and tell the reviewers, who get the same paths under PITFALLS TO READ. 1 item (or items in the same files). `maxTurns` 220; past ~150 steps the executor stops and reports. Database item: the executor proves it on a local database, never production. The executor commits its own item on the Part branch with `git add` by name; push and PR go at the end through `\u002Ftune-up:ship`, only with the request above.\n\n## Step 4 - Item review\n\n- Up to 3 reviewers (opus, high), ALL in ONE message, receiving ONLY the item's diff + criterion C + `PITFALLS TO READ` (the same absolute paths as the executor's pitfall skills): `tune-up:reviewer-failures` always; `tune-up:reviewer-database` for migration\u002Faccess rules\u002FRPC\u002Ftrigger\u002FSQL; `tune-up:reviewer-security` for auth, personal data, payment, webhook or sending.\n- Reviewers end with a fenced json block `{\"verdict\",\"findings\":[{\"sev\",\"file\",\"line\",\"introduced\",\"proof\",\"title\"}]}` (proof: observed|read|suspected) and the last line `Verdict: ...`. Route by the json: `introduced` and sev CRITICAL\u002FHIGH goes back; the rest goes to the later document. Missing or invalid json: ask again once.\n- All CRITICAL\u002FHIGH from all reviewers become ONE fix round: a NEW executor gets the ORIGINAL order + the findings + the item's cumulative diff (never SendMessage to the old one). A MEDIUM of 1-3 obvious lines may ride along, never alone.\n- MEDIUM, LOW and pre-existing -> the phase `names.later` document (1 line: file:line, finding, reviewer).\n- Next round: only the reviewer(s) that rejected, receiving `PREVIOUS FINDINGS` + the cumulative item diff, marking each finding closed or reopened. Max 2 rounds; CRITICAL\u002FHIGH left or count not dropping -> `names.need_you` and STOP.\n- Record per item in progress: executor, step count and pitfall skills read (from the handoff json, real numbers, not estimates), CRITICAL\u002FHIGH per round (e.g. `HIGH 2->0`, reviewer and 1-line finding each).\n\n## Step 5 - Part gate\n\n1. One `tune-up:checker` per side the Part touched (as the profile splits them; otherwise one call), all in ONE message, in the worktree; each runs the profile's \"Definition of done\", comparing with main (a pre-existing failure is not yours, but name it).\n2. Criteria C measured (query\u002Fcommand) and written in progress with the result.\n3. Project docs updated if the profile asks.\n4. Migration headed for production: hand over the file and steps; apply only via `\u002Ftune-up:migration` on the owner's order.\n5. Say what did NOT run (CI, test, deploy) and why.\n\n## Step 6 - Close and STOP\n\n1. Progress document (local `\u003Cplans_dir>`, then copied into the Part branch): `names.part_closed` (date), what landed, criteria measured, what stays with the owner (merge, deploy, migration), the later document, the next Part's `\u002Fgoal` command ending in ` - follow \u002Ftune-up:part. Stop when: \"\u003Cnames.part_closed>\" in progress OR you wrote \u003Cnames.need_you> OR 40 turns.`\n2. Backlog: copy the open items of the phase `names.later` into the `names.backlog` document in `\u003Cplans_dir>\u002F` (`names.roadmap` and `names.backlog` live in `plans_dir`; `names.vision`, `names.prd`, `names.architecture`, `names.design`, `names.decisions` in `docs\u002F`; create it if missing; skip duplicates).\n3. Knowledge graph: if `graphify-out\u002F` exists AND `command -v graphify` succeeds, run `graphify update .`; otherwise skip silently.\n4. Pitfalls learned: for each CRITICAL\u002FHIGH of this Part that can repeat (a pattern, not a one-off slip), draft 1 line for the pitfall skill of the project's modules whose `paths` match the file (name or description says pitfalls\u002Farmadilhas), in its format: **rule.** Why: what happened (Part, date). Already covered by a line: propose sharpening that line instead, never a duplicate. Show the drafts in ONE `AskUserQuestion` (multiSelect); record the approved ones via `\u002Ftune-up:learn` (it edits the module in `plugin_source`; without it, the rule goes to the project profile). No candidate: write \"no new pitfall\" in progress.\n5. If the project has a Claude memory, record a short note there (+ index line).\n6. Short answer: done, what depends on the owner, pitfalls recorded, next Part command. STOP. Never chain the next Part in this conversation.\n","# Run a Part\n\nContext: !`sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info`\n\nRequest: $ARGUMENTS\n\nThe JSON above is the context. Write to the user in its `language`, honoring `reply_style`; final answer short. Use document names from `names` (`goal`, `progress`, `research`, `later`, `backlog`, `need_you`, `part_closed`), never literal. Models\u002Feffort per role from `models`; if missing, use the table defaults.\n\nYou (main session, highest effort) coordinate and judge; you do not write the items' code. One Part per conversation: at the end, STOP.\n\n## Roles\n\n| Role | Agent | Default model | Effort |\n|---|---|---|---|\n| Map \u002F recheck lines | `tune-up:mapper` | haiku | medium |\n| Pick skills for an item | `tune-up:skill-finder` | haiku | medium |\n| Simple item (screen, text, simple route, test, doc) | `tune-up:executor-sonnet` | sonnet | medium |\n| Risky item (migration, trigger, access rules, RPC, worker, money, auth, external sending, concurrency) | `tune-up:executor-opus` | opus | medium |\n| Review the diff | `tune-up:reviewer-failures`, `tune-up:reviewer-database`, `tune-up:reviewer-security` | opus | high |\n| Definition of done | `tune-up:checker` | haiku | medium |\n| Edit goal\u002Fprogress\u002Fdocs | `tune-up:writer` | sonnet | medium |\n\n- Independent agents go in ONE message, in background. Do not wait awake.\n- Pass `model` and `effort` on every call. Never a model in `forbidden_subagent_models` (default `[\"fable\"]`).\n- Production writes, customer messages, ads: only with the owner's explicit request IN THE TURN. A \"yes\" to another question does not count.\n- Planning documents (goal, progress, later, research, handoff) live in the LOCAL `\u003Cplans_dir>`, the main checkout, as absolute paths. Read and write them only there, never only in the worktree: the worktree copy is invisible to the other sessions and to `\u002Ftune-up:status`. Each session writes only its own Part's lines. Before the PR (Step 6), copy the phase files from the local folder into the worktree at the same relative path and commit them on the Part branch, so the PR carries them. The local copy stays the source.\n- Commit of an item on the Part branch: yes. Push and PR only if this Part's request (message or `\u002Fgoal` condition) says push\u002FPR; otherwise leave all ready and write `names.need_you` may I push and open the PR? Branch cut from the day's `origin\u002F\u003Cmain>`. Merged PR = dead branch: a post-merge fix is a NEW PR from main; never stacked PRs.\n- Never `git stash -u`. `git add` by file name only. Preserve existing changes and untracked files.\n- Read the project profile (`profile_path`): definition of done, production, pitfalls.\n\n## Workflow scripts\n\n- If you orchestrate with the Workflow tool, start from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002Fworkflow-template.js`.\n- Every `agent()` carries a literal `agentType` from the table above, plus `model` and `effort`. Never let an agent inherit the session model.\n- A generic agent (no `agentType`, or `general-purpose`) starts with about three times the context of a `tune-up:*` agent. Use one only for work that needs MCP tools, a browser or images, and mark the line above with `\u002F\u002F tune-up: allow-generic \u003Creason>`. The guard warns (or blocks, with `\"workflow_generic\": \"block\"` in the profile config) otherwise.\n- Review loop in a script: at most 2 fix rounds per item; after each fix only the reviewers that rejected run again; CRITICAL\u002FHIGH left after the review that follows the second fix -> `names.need_you`, never a third fix.\n- A `null` result or a \"hit your ... limit\" reply is an interrupted item: do not relaunch it and do not count it as done; check git before resuming.\n\n## Step 1 - Understand and check prerequisites\n\n1. Read ONLY the Part's sections, the criteria C and the Execution section of the goal document, plus progress. Research is spot consultation.\n2. Check `origin\u002F\u003Cmain>`, `gh pr list` and `git status`: another session may have done something unrecorded. A sibling Part closed in the local progress counts as done for the \"Parts\" table, even if it is not merged; its merge\u002Fmigration is the owner's prerequisite.\n3. A prerequisite in the \"Parts\" table that depends on the owner (decision, merge, deploy, migration): say ONCE `names.need_you` + the exact action and STOP (with `\u002Fgoal`, ask for `\u002Fgoal clear`). Never \"still waiting\" in a loop.\n\n## Step 2 - Base and map\n\n1. `git fetch`; your OWN worktree from `origin\u002F\u003Cmain>` with the Part branch. Before committing: `git branch --show-current`.\n2. One `tune-up:mapper` per item group, ALL groups in one message, rechecks EVERY line cited in the goal against today's base and returns current snippets (`file:line`). Line moved: adjust the work order, not the goal; note it in progress. In that same message call `tune-up:skill-finder` (item text, absolute `info.catalog_path`) only when `info.catalog_path` is set and the goal item has no Skills.\n3. Item that reads, filters or deletes EXISTING data: while the mappers run, the main session runs 1-3 read-only queries on production (counts per status\u002Fshape, NULL counts, lengths, min\u002Fmax dates). Aggregates and shapes only, never a raw value of a phone, name, e-mail or message. Paste the result under REAL DATA in the order; never copy it to progress or to a test fixture.\n\n## Step 3 - One item at a time\n\nBuild the work order from `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002Fwork-order.md` and dispatch in background. \"Skills to read\" ALWAYS includes every entry of `info.pitfall_skills` whose `paths` globs match the absolute path of an owned file (worktree + path, no `:lines` suffix; `**\u002F` also matches zero folders), with or without a catalog, plus the goal's \"Skills\"; the skill-finder (Step 2) only adds extras. A handoff whose json `skills_read` misses a matched pitfall skill: note it in progress and tell the reviewers, who get the same paths under PITFALLS TO READ. 1 item (or items in the same files). `maxTurns` 220; past ~150 steps the executor stops and reports. Database item: the executor proves it on a local database, never production. The executor commits its own item on the Part branch with `git add` by name; push and PR go at the end through `\u002Ftune-up:ship`, only with the request above.\n\n## Step 4 - Item review\n\n- Up to 3 reviewers (opus, high), ALL in ONE message, receiving ONLY the item's diff + criterion C + `PITFALLS TO READ` (the same absolute paths as the executor's pitfall skills): `tune-up:reviewer-failures` always; `tune-up:reviewer-database` for migration\u002Faccess rules\u002FRPC\u002Ftrigger\u002FSQL; `tune-up:reviewer-security` for auth, personal data, payment, webhook or sending.\n- Reviewers end with a fenced json block `{\"verdict\",\"findings\":[{\"sev\",\"file\",\"line\",\"introduced\",\"proof\",\"title\"}]}` (proof: observed|read|suspected) and the last line `Verdict: ...`. Route by the json: `introduced` and sev CRITICAL\u002FHIGH goes back; the rest goes to the later document. Missing or invalid json: ask again once.\n- All CRITICAL\u002FHIGH from all reviewers become ONE fix round: a NEW executor gets the ORIGINAL order + the findings + the item's cumulative diff (never SendMessage to the old one). A MEDIUM of 1-3 obvious lines may ride along, never alone.\n- MEDIUM, LOW and pre-existing -> the phase `names.later` document (1 line: file:line, finding, reviewer).\n- Next round: only the reviewer(s) that rejected, receiving `PREVIOUS FINDINGS` + the cumulative item diff, marking each finding closed or reopened. Max 2 rounds; CRITICAL\u002FHIGH left or count not dropping -> `names.need_you` and STOP.\n- Record per item in progress: executor, step count and pitfall skills read (from the handoff json, real numbers, not estimates), CRITICAL\u002FHIGH per round (e.g. `HIGH 2->0`, reviewer and 1-line finding each).\n\n## Step 5 - Part gate\n\n1. One `tune-up:checker` per side the Part touched (as the profile splits them; otherwise one call), all in ONE message, in the worktree; each runs the profile's \"Definition of done\", comparing with main (a pre-existing failure is not yours, but name it).\n2. Criteria C measured (query\u002Fcommand) and written in progress with the result.\n3. Project docs updated if the profile asks.\n4. Migration headed for production: hand over the file and steps; apply only via `\u002Ftune-up:migration` on the owner's order.\n5. Say what did NOT run (CI, test, deploy) and why.\n\n## Step 6 - Close and STOP\n\n1. Progress document (local `\u003Cplans_dir>`, then copied into the Part branch): `names.part_closed` (date), what landed, criteria measured, what stays with the owner (merge, deploy, migration), the later document, the next Part's `\u002Fgoal` command ending in ` - follow \u002Ftune-up:part. Stop when: \"\u003Cnames.part_closed>\" in progress OR you wrote \u003Cnames.need_you> OR 40 turns.`\n2. Backlog: copy the open items of the phase `names.later` into the `names.backlog` document in `\u003Cplans_dir>\u002F` (`names.roadmap` and `names.backlog` live in `plans_dir`; `names.vision`, `names.prd`, `names.architecture`, `names.design`, `names.decisions` in `docs\u002F`; create it if missing; skip duplicates).\n3. Knowledge graph: if `graphify-out\u002F` exists AND `command -v graphify` succeeds, run `graphify update .`; otherwise skip silently.\n4. Pitfalls learned: for each CRITICAL\u002FHIGH of this Part that can repeat (a pattern, not a one-off slip), draft 1 line for the pitfall skill of the project's modules whose `paths` match the file (name or description says pitfalls\u002Farmadilhas), in its format: **rule.** Why: what happened (Part, date). Already covered by a line: propose sharpening that line instead, never a duplicate. Show the drafts in ONE `AskUserQuestion` (multiSelect); record the approved ones via `\u002Ftune-up:learn` (it edits the module in `plugin_source`; without it, the rule goes to the project profile). No candidate: write \"no new pitfall\" in progress.\n5. If the project has a Claude memory, record a short note there (+ index line).\n6. Short answer: done, what depends on the owner, pitfalls recorded, next Part command. STOP. Never chain the next Part in this conversation.\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash(sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpy\" scripts\u002Fguarda.py info), Bash(graphify update .), Bash(command -v graphify)","\u003CNNN> \u003CPart>  e.g. 184 B","main","bbde73350fc3c138bffa1e546839b190e0d415bc","skills\u002Fpart",0,"https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up","https:\u002F\u002Fgithub.com\u002Fstage2dev","Tuning the unnecessary.","2026-11-14 05:05:23",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add stage2dev\u002Ftune-up --skill part",{"tool":39,"command":40},"bunx","bunx skills add stage2dev\u002Ftune-up --skill part",{"tool":42,"command":43},"pnpm","pnpm dlx skills add stage2dev\u002Ftune-up --skill part","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Fskills\u002Fpart\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M7F6Z7DAMCW5ES2ED8FGCC8C","instalar","One-step setup of the WhatsApp sales screen on this computer: Docker, the local Evolution API and the sales service, step by step in plain words. Use on: install, set up WhatsApp, prepare sales; instalar, preparar, preparar o WhatsApp, setup WhatsApp, configurar vendas.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Fvendas\u002Fskills\u002Finstalar\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7F6Z0BKKW3MGNAM1NJ16JHV","video","Makes a hook-first, business-oriented silent vertical reel (9:16, 1080x1920 MP4, 10 or 15 s) from a briefing, using only the owner-approved brand: strategy, the reel composition of the studio kit filled with the script and a hero drawn for this briefing, motion by the studio JavaScript engine (seek-safe, no network), render or slide reserve, and the studio QA. Runs unattended from the panel actions estudio.video and estudio.video-motion. Use on: vídeo, reel, reels, story em vídeo.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7F6YS17B793E58C07S5EX5R","post","Makes a hook-first, business-oriented still post or carousel (PNG per frame) from a briefing, using only the owner-approved brand: strategy first, one chosen hook, a composition of the studio kit with a hero drawn for this briefing, one call to action, and every frame checked by the studio QA. Runs unattended from the panel action estudio.post. Use on: post, carrossel, carousel, peça estática, post do Instagram.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fpost\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7F6YFJNJP6PT3YTFEBRQW9V","marca","Discovers the project's brand (colors, fonts, logo, name) from its own files and shows it to the owner for approval in the panel. Use on: discover the brand, descobrir marca, identidade visual do projeto, marca do estúdio.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fmarca\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7F6YBJ20F1GJN7ZFJJK8Y7Y","marca-ler","Reads the project's brand (marca.json) and says whether the owner approved it. Read-only: never approves, edits or writes anything. Use on: read the brand, is the brand approved, ler marca, marca aprovada.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fmarca-ler\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7F6Y4KXCDFMA88EHVM0DRVB","anuncio","Makes a hook-first, business-oriented ad from a briefing, using only the owner-approved brand: one master image plus the aspect-ratio adaptations the platform needs, text variations inside the platform limits, and an import sheet with everything Paused (Google Ads Editor CSV, or an experimental Meta sheet). Publishes nothing and calls no ad API. Runs unattended from the panel action estudio.anuncio. Use on: anúncio, anuncio, ad, Google Ads, Meta Ads.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fanuncio\u002FSKILL.md",[],[]]