[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARZPQAJJ47FMJ4XFERCKTP":3,"skill-same:01M7ARZPQAJJ47FMJ4XFERCKTP":44},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M7ARZPQAJJ47FMJ4XFERCKTP","thinking-model-combination",null,"When one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.","ham-zax\u002Fwebharness","ham-zax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81289670?v=4","01M7AQGHAV4TPYCAZY23S7SVSC","Ahmed Hamza","01M7AQGHBCFJYE7KWZ34W9HEGH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fthinking\u002Fthinking-model-combination\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: thinking-model-combination\ndescription: When one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.\ndisable-model-invocation: true\n---\n\n# Model Combination\n\n**Core rule:** Combine only when each model answers a different named question. Cap at three, name the conflict rule before applying, then synthesize once.\n\n## When to Use\n\n- One model already applied (or clearly primary) still leaves a material blind spot that another mechanism covers.\n- Problem spans domains (e.g. risk + choice + system structure) and stakes justify multi-lens work.\n- You need independent checks, not confirmation of the same conclusion.\n- You can name a distinct role per model before running them.\n\n## When NOT to Use\n\n- A single catalog skill fully answers the unknown — apply that skill alone.\n- Routine, local, or fully reversible work where multi-lens cost exceeds upside.\n- You cannot state what unique question each extra model answers (checkbox \u002F model soup).\n- Near-duplicate mechanisms (two diagnosis skills that ask the same causal question).\n- Time budget cannot support genuine synthesis — prefer one honest model over contradictory partials.\n\n## Procedure\n\n1. **State the unknown and the gap.** Write the decision question. If one model already covers it, stop and use that model alone. Otherwise name the specific blind spot (e.g. \"failure modes unexamined\", \"displaced alternative unknown\").\n2. **Pick 2–3 models with distinct roles.** For each, record: model id, role (narrow \u002F decide \u002F stress \u002F cost \u002F …), and the unique question it answers. Drop any model that only rephrases another. Prefer sequential pipeline (narrow → stress → decide) over parallel unless independent concurrent checks are required.\n3. **Lock the relation and conflict rule before applying.** Choose pattern: sequential, parallel, nested (macro→meso→micro), or adversarial (for\u002Fagainst). Predeclare the tiebreaker (e.g. reversibility class, evidence strength, ruin constraint, primary decision owner). Incompatible worldviews run sequential or adversarial — never blended.\n4. **Apply each model fully for its role only.** Capture one key insight per model plus what only that model revealed. Do not re-run a model that adds no new insight.\n5. **Synthesize once.** Record convergence, divergence, how the conflict rule resolves divergence, and a single combined recommendation with residual uncertainty. Stop when the recommendation is decision-ready or when further models would only reconfirm.\n\n## Output\n\n```text\nproblem: \u003Cdecision question>\ngap: \u003Cnamed blind spot justifying combination>\npattern: sequential | parallel | nested | adversarial\nmodels:\n  - id: \u003Cskill>\n    role: \u003Cnamed job>\n    unique_question: \u003Cwhat only this answers>\n    insight: \u003Ckey finding>\nconflict_rule: \u003Cpredeclared tiebreaker>\nconvergence: \u003Cwhere models agree>\ndivergence: \u003Cwhere they conflict + resolution>\nrecommendation: \u003Csingle decision-ready answer>\nstop_reason: gap_closed | single_model_suffices | budget\n```\n\n## Verification\n\n- **Falsify \u002F stop:** Remove a model only when it changes none of the recommendation, supporting evidence, confidence, residual risks, or mitigations; then re-synthesize with fewer. If no predeclared conflict rule exists and models disagree, do not average — pick one primary model or stop and re-route.\n- **Over-application guard:** Never exceed three models. Never add a model for thoroughness theater. If the first adequate single model already closes the gap, combination is wrong for this task.\n","# Model Combination\n\n**Core rule:** Combine only when each model answers a different named question. Cap at three, name the conflict rule before applying, then synthesize once.\n\n## When to Use\n\n- One model already applied (or clearly primary) still leaves a material blind spot that another mechanism covers.\n- Problem spans domains (e.g. risk + choice + system structure) and stakes justify multi-lens work.\n- You need independent checks, not confirmation of the same conclusion.\n- You can name a distinct role per model before running them.\n\n## When NOT to Use\n\n- A single catalog skill fully answers the unknown — apply that skill alone.\n- Routine, local, or fully reversible work where multi-lens cost exceeds upside.\n- You cannot state what unique question each extra model answers (checkbox \u002F model soup).\n- Near-duplicate mechanisms (two diagnosis skills that ask the same causal question).\n- Time budget cannot support genuine synthesis — prefer one honest model over contradictory partials.\n\n## Procedure\n\n1. **State the unknown and the gap.** Write the decision question. If one model already covers it, stop and use that model alone. Otherwise name the specific blind spot (e.g. \"failure modes unexamined\", \"displaced alternative unknown\").\n2. **Pick 2–3 models with distinct roles.** For each, record: model id, role (narrow \u002F decide \u002F stress \u002F cost \u002F …), and the unique question it answers. Drop any model that only rephrases another. Prefer sequential pipeline (narrow → stress → decide) over parallel unless independent concurrent checks are required.\n3. **Lock the relation and conflict rule before applying.** Choose pattern: sequential, parallel, nested (macro→meso→micro), or adversarial (for\u002Fagainst). Predeclare the tiebreaker (e.g. reversibility class, evidence strength, ruin constraint, primary decision owner). Incompatible worldviews run sequential or adversarial — never blended.\n4. **Apply each model fully for its role only.** Capture one key insight per model plus what only that model revealed. Do not re-run a model that adds no new insight.\n5. **Synthesize once.** Record convergence, divergence, how the conflict rule resolves divergence, and a single combined recommendation with residual uncertainty. Stop when the recommendation is decision-ready or when further models would only reconfirm.\n\n## Output\n\n```text\nproblem: \u003Cdecision question>\ngap: \u003Cnamed blind spot justifying combination>\npattern: sequential | parallel | nested | adversarial\nmodels:\n  - id: \u003Cskill>\n    role: \u003Cnamed job>\n    unique_question: \u003Cwhat only this answers>\n    insight: \u003Ckey finding>\nconflict_rule: \u003Cpredeclared tiebreaker>\nconvergence: \u003Cwhere models agree>\ndivergence: \u003Cwhere they conflict + resolution>\nrecommendation: \u003Csingle decision-ready answer>\nstop_reason: gap_closed | single_model_suffices | budget\n```\n\n## Verification\n\n- **Falsify \u002F stop:** Remove a model only when it changes none of the recommendation, supporting evidence, confidence, residual risks, or mitigations; then re-synthesize with fewer. If no predeclared conflict rule exists and models disagree, do not average — pick one primary model or stop and re-route.\n- **Over-application guard:** Never exceed three models. Never add a model for thoroughness theater. If the first adequate single model already closes the gap, combination is wrong for this task.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","59ee67804bc373a9bd079a3a27f47277a6efe564","skill-library\u002Fpacks\u002Fthinking\u002Fthinking-model-combination","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness","https:\u002F\u002Fgithub.com\u002Fham-zax","2026-11-15 01:18:51",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":24},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ham-zax\u002Fwebharness --skill thinking-model-combination",{"tool":37,"command":38},"bunx","bunx skills add ham-zax\u002Fwebharness --skill thinking-model-combination",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ham-zax\u002Fwebharness --skill thinking-model-combination","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fthinking\u002Fthinking-model-combination\u002FSKILL.md",[],[45,52,59,66,75,82],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7AS6BAQQ2WQJYS3WBNJPB2G","x-content","Create, rewrite, critique, select formats for, discover opportunities for, and learn from X\u002FTwitter content and X Articles for a technical AI-native developer\u002Fbuilder account. Use when turning ideas, source posts, releases, benchmarks, results, conversations, authenticated For You or creator-watch opportunities, or project evidence into an Original, Quote, Thread, Reply, or Article; reviewing article titles\u002Foutlines\u002Fvisual briefs\u002Flaunch hooks; improving drafts; choosing additive contributions from live X context; or learning from own-account outcomes. Own content intelligence only; compose with agent-browser for live X state and Growth OS for discovery provenance, approvals, measurement, and publication.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fx-content\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AS66FXQR8FEQYW8G8RJB2N","writing-plans","Create detailed implementation plans for multi-step software work before editing code. Use when requirements or a specification must become concrete file-level tasks, interfaces, acceptance criteria, risks, rollout, or explicitly required validation. Default to no test creation, test modification, test execution, TDD, regression-test, or coverage work unless the user, authoritative specification, or mandatory repository policy explicitly requires testing.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"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},"01M7AS5ZCJX21NF2RESA2QDWPP","systematic-debugging","Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\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":70,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AS548FQ63SAB9G0X81VPGJ","skill-creator","Guide for creating and updating high-quality skills by translating workflows, conventions, and reusable processes into well-structured skills. Includes context, use case examples and spec for skills. Use this skill whenever a user asks to create, update, edit, improve, package, or troubleshoot a skill, and also for conversational questions about skills in ChatGPT (e.g., \"What are skills?\", \"What can I use skills for?\", \"What are the best skill use cases for me?\", \"Where can I find my skills?\").","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AS4XD121Q85Y06EXRGYS4F","reflexion","Self-refinement, multi-perspective critique, verification, and durable lesson curation adapted from NeoLabHQ Reflexion. Use when the user asks to reflect, self-review, critique, double-check, verify and improve prior work, run a rigorous review, memorize lessons, or says \"then reflect\" after a coding, analysis, or writing task. Supports repository-aware evidence gathering and works without subagents or Claude hooks.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Freflexion\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AS4RN5TYMA4P6SK6K7NVSR","ponytail","Enforce Ponytail's lazy-senior-developer approach for coding, fixing, refactoring, design, dependency choices, and explicit Ponytail modes such as review, audit, debt, gain, and help. Prefer YAGNI, existing code, standard library, native platform features, existing dependencies, low reader load, and the smallest correct diff. For source mutation, keep Causal Coding authoritative for scope, testing authorization, verification cadence, and stopping. On connected WSL\u002FLinux targets, compose with MCP Harness Router and use `wsl-web-harness` for authoritative repository work.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002FSKILL.md",[],[]]