[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS3J5WFH5APCTPHQX6HFAV":3,"skill-same:01M7CS3J5WFH5APCTPHQX6HFAV":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CS3J5WFH5APCTPHQX6HFAV","dynamic-workflow-mode",null,"Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fdynamic-workflow-mode\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dynamic-workflow-mode\ndescription: \"Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses.\"\nmetadata:\n  origin: ECC\n---\n\n# Dynamic Workflow Mode\n\nUse this skill when a coding agent can generate or adapt a task-local harness instead of only following a static command flow. The goal is to turn dynamic workflow mode into a disciplined system: temporary harnesses for one-off work, shared skill extraction for repeated work, and observable control pane checkpoints for teams.\n\n## When To Activate\n\n- The user mentions dynamic workflows, custom harnesses, harness-per-task, adaptive workflows, or Claude Code dynamic workflow mode.\n- A task needs a custom loop, evaluator, crawler, fixture generator, watcher, or local dashboard.\n- Multiple agents need the same repeatable process but the process is not yet captured as a shared skill.\n- A workflow needs durable handoff artifacts, eval evidence, or operator approval before merge.\n\n## Core Contract\n\nDynamic workflow mode should produce a task-local harness only when the harness is cheaper and safer than manually driving the same steps. The harness must have:\n\n- **Objective**: the outcome it owns and the outcome it explicitly does not own.\n- **Inputs**: files, URLs, prompts, data sources, credentials policy, and user-provided constraints.\n- **Outputs**: commits, reports, screenshots, status files, or control pane snapshots.\n- **Eval**: at least one pass\u002Ffail check tied to the task, not only \"it ran\".\n- **Handoff**: a short artifact that tells the next operator what happened, what is blocked, and how to resume.\n\n## Dynamic Harness Decision Tree\n\n1. **One-shot task**: keep it inline. Do not invent a harness.\n2. **Repeated task with changing inputs**: create a task-local harness and keep it under a temp or project-local working area.\n3. **Repeated task across teammates or repos**: extract the pattern into a shared skill.\n4. **Task with external state, queueing, or approvals**: add control pane visibility before adding more automation.\n5. **Task with safety risk**: add an eval gate and a human merge gate before autonomous execution.\n\n## Task-Local Harness Template\n\nUse this structure before writing code:\n\n```markdown\n# Dynamic Workflow Harness\n\nObjective:\n- Ship:\n- Do not ship:\n\nInputs:\n- Repo or workspace:\n- External systems:\n- Credentials policy:\n\nLoop:\n1. Discover current state.\n2. Generate or update the smallest useful artifact.\n3. Run eval checks.\n4. Record status and handoff.\n5. Stop on failed gate, unclear ownership, or unsafe external action.\n\nEval:\n- Command:\n- Expected pass signal:\n- Failure owner:\n\nHandoff:\n- Status:\n- Evidence:\n- Next action:\n```\n\n## Shared Skill Extraction\n\nPromote a task-local harness into a shared skill only when at least two of these are true:\n\n- The same workflow appears in multiple sessions, repos, teams, or launches.\n- The workflow needs specific language, tool, or safety sequencing.\n- Failures repeat because operators skip a gate or lose context.\n- The workflow has a stable input\u002Foutput contract.\n- The workflow benefits from a control pane, status board, or team handoff.\n\nWhen extracting, write the skill first in `skills\u002F\u003Cname>\u002FSKILL.md`. Add command shims only if a legacy slash-entry surface is still required.\n\n## Control Pane Checkpoints\n\nDynamic workflow mode becomes team-usable when it exposes state. Record these checkpoints whenever the task spans more than one session:\n\n- **Plan**: objective, owner, acceptance criteria, and risky external systems.\n- **Queue**: work items, assigned agent role, branch\u002Fworktree, and dependency edges.\n- **Run**: active harness, current loop step, recent eval result, and token\u002Fcost signal if available.\n- **Gate**: test results, browser screenshots, security review, and merge readiness.\n- **Handoff**: what is done, what failed, what needs a human decision.\n\nIf the repo has ECC2 state enabled, prefer adding or reading checkpoints through the ECC control pane or state-store-backed scripts instead of scattering untracked notes.\n\n## Eval Gates\n\nEvery dynamic harness needs a task-specific eval. Pick the cheapest reliable gate:\n\n| Work Type | Eval Gate |\n| --- | --- |\n| Code feature | Focused test, lint, coverage, and one integration path |\n| UI\u002Fcontrol pane | Browser smoke with screenshot and overflow\u002Ferror checks |\n| Agent workflow | Fixture transcript or seeded work item with expected routing |\n| Research\u002Fcontent | Source-neutral brief, claim checklist, and publish-ready outline |\n| Integration | Dry-run command, config validation, and no-secret scan |\n\nDo not claim a dynamic workflow is reusable until the eval can be rerun by another teammate.\n\n## Anti-Patterns\n\n- Generating scripts that hide the real decision logic from the operator.\n- Treating dynamic workflow mode as permission to skip tests.\n- Creating one-off docs when a shared skill or status artifact is the real product.\n- Running multiple agents without ownership, merge gate, or conflict policy.\n- Letting raw private research data leak into public docs.\n\n## Output Standard\n\nFinish with:\n\n- The harness or skill path.\n- The eval commands and results.\n- The control pane or handoff artifact path.\n- The next reusable extraction candidate.\n","# Dynamic Workflow Mode\n\nUse this skill when a coding agent can generate or adapt a task-local harness instead of only following a static command flow. The goal is to turn dynamic workflow mode into a disciplined system: temporary harnesses for one-off work, shared skill extraction for repeated work, and observable control pane checkpoints for teams.\n\n## When To Activate\n\n- The user mentions dynamic workflows, custom harnesses, harness-per-task, adaptive workflows, or Claude Code dynamic workflow mode.\n- A task needs a custom loop, evaluator, crawler, fixture generator, watcher, or local dashboard.\n- Multiple agents need the same repeatable process but the process is not yet captured as a shared skill.\n- A workflow needs durable handoff artifacts, eval evidence, or operator approval before merge.\n\n## Core Contract\n\nDynamic workflow mode should produce a task-local harness only when the harness is cheaper and safer than manually driving the same steps. The harness must have:\n\n- **Objective**: the outcome it owns and the outcome it explicitly does not own.\n- **Inputs**: files, URLs, prompts, data sources, credentials policy, and user-provided constraints.\n- **Outputs**: commits, reports, screenshots, status files, or control pane snapshots.\n- **Eval**: at least one pass\u002Ffail check tied to the task, not only \"it ran\".\n- **Handoff**: a short artifact that tells the next operator what happened, what is blocked, and how to resume.\n\n## Dynamic Harness Decision Tree\n\n1. **One-shot task**: keep it inline. Do not invent a harness.\n2. **Repeated task with changing inputs**: create a task-local harness and keep it under a temp or project-local working area.\n3. **Repeated task across teammates or repos**: extract the pattern into a shared skill.\n4. **Task with external state, queueing, or approvals**: add control pane visibility before adding more automation.\n5. **Task with safety risk**: add an eval gate and a human merge gate before autonomous execution.\n\n## Task-Local Harness Template\n\nUse this structure before writing code:\n\n```markdown\n# Dynamic Workflow Harness\n\nObjective:\n- Ship:\n- Do not ship:\n\nInputs:\n- Repo or workspace:\n- External systems:\n- Credentials policy:\n\nLoop:\n1. Discover current state.\n2. Generate or update the smallest useful artifact.\n3. Run eval checks.\n4. Record status and handoff.\n5. Stop on failed gate, unclear ownership, or unsafe external action.\n\nEval:\n- Command:\n- Expected pass signal:\n- Failure owner:\n\nHandoff:\n- Status:\n- Evidence:\n- Next action:\n```\n\n## Shared Skill Extraction\n\nPromote a task-local harness into a shared skill only when at least two of these are true:\n\n- The same workflow appears in multiple sessions, repos, teams, or launches.\n- The workflow needs specific language, tool, or safety sequencing.\n- Failures repeat because operators skip a gate or lose context.\n- The workflow has a stable input\u002Foutput contract.\n- The workflow benefits from a control pane, status board, or team handoff.\n\nWhen extracting, write the skill first in `skills\u002F\u003Cname>\u002FSKILL.md`. Add command shims only if a legacy slash-entry surface is still required.\n\n## Control Pane Checkpoints\n\nDynamic workflow mode becomes team-usable when it exposes state. Record these checkpoints whenever the task spans more than one session:\n\n- **Plan**: objective, owner, acceptance criteria, and risky external systems.\n- **Queue**: work items, assigned agent role, branch\u002Fworktree, and dependency edges.\n- **Run**: active harness, current loop step, recent eval result, and token\u002Fcost signal if available.\n- **Gate**: test results, browser screenshots, security review, and merge readiness.\n- **Handoff**: what is done, what failed, what needs a human decision.\n\nIf the repo has ECC2 state enabled, prefer adding or reading checkpoints through the ECC control pane or state-store-backed scripts instead of scattering untracked notes.\n\n## Eval Gates\n\nEvery dynamic harness needs a task-specific eval. Pick the cheapest reliable gate:\n\n| Work Type | Eval Gate |\n| --- | --- |\n| Code feature | Focused test, lint, coverage, and one integration path |\n| UI\u002Fcontrol pane | Browser smoke with screenshot and overflow\u002Ferror checks |\n| Agent workflow | Fixture transcript or seeded work item with expected routing |\n| Research\u002Fcontent | Source-neutral brief, claim checklist, and publish-ready outline |\n| Integration | Dry-run command, config validation, and no-secret scan |\n\nDo not claim a dynamic workflow is reusable until the eval can be rerun by another teammate.\n\n## Anti-Patterns\n\n- Generating scripts that hide the real decision logic from the operator.\n- Treating dynamic workflow mode as permission to skip tests.\n- Creating one-off docs when a shared skill or status artifact is the real product.\n- Running multiple agents without ownership, merge gate, or conflict policy.\n- Letting raw private research data leak into public docs.\n\n## Output Standard\n\nFinish with:\n\n- The harness or skill path.\n- The eval commands and results.\n- The control pane or handoff artifact path.\n- The next reusable extraction candidate.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","a73152352c0612252131e5cf84e91312a6cf17dc","ai-agents\u002Fdynamic-workflow-mode","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill dynamic-workflow-mode",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill dynamic-workflow-mode",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill dynamic-workflow-mode","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fdynamic-workflow-mode\u002FSKILL.md",true,[],[49,56,63,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]