[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77CX97VVJ2K01SAQVGET7RY":3,"skill-same:01M77CX97VVJ2K01SAQVGET7RY":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77CX97VVJ2K01SAQVGET7RY","dual-perspective-analyzer",null,"Resolve dual-perspective collaboration conflicts by classifying them into 5 types and applying targeted integration strategies. Use when two agents (or an agent and user) have different approaches to the same problem — e.g., qualitative vs. quantitative, strategic vs. tactical, creative vs. analytical. Provides conflict taxonomy, resolution strategies, and a 5-metric dashboard for validation.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdual-perspective-analyzer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dual-perspective-analyzer\ndescription: Resolve dual-perspective collaboration conflicts by classifying them into 5 types and applying targeted integration strategies. Use when two agents (or an agent and user) have different approaches to the same problem — e.g., qualitative vs. quantitative, strategic vs. tactical, creative vs. analytical. Provides conflict taxonomy, resolution strategies, and a 5-metric dashboard for validation.\n---\n\n# Dual-Perspective Analyzer\n\nA methodology for integrating complementary perspectives into unified, higher-quality outputs.\n\n## When to Use This Skill\n\nUse this skill when:\n- Two agents (or an agent and user) approach the same problem differently\n- One focuses on \"why\u002Fnarrative\" and the other on \"what\u002Fimplementation\"\n- There's tension between richness vs. precision, speed vs. thoroughness, or vision vs. feasibility\n- You need to validate whether dual-perspective collaboration actually improves outcomes\n- You want structured conflict resolution rather than compromise or dominance\n\n## The 5 Conflict Types\n\n| Type | Name | Pattern | Resolution Strategy |\n|------|------|---------|---------------------|\n| **Type 1** | **Complementary Blind Spots** | Each perspective misses what the other sees | Cross-perspective dependency mapping |\n| **Type 2** | **Integration Friction** | Perspectives valid but hard to combine | Translation layer + iterative merging |\n| **Type 3** | **Priority Disagreement** | Same goal, different weighting | Parallel time-boxing + test both |\n| **Type 4** | **False Conflict** | Appears opposed but actually aligned | Reclassification + synthesis |\n| **Type 5** | **Fundamental Incompatibility** | Truly opposing constraints | Escalation or scope separation |\n\n## The Layered View Methodology\n\nPresent dual-perspective outputs in 5 layers to serve different cognitive needs:\n\n### Layer 1: Essential View (30 seconds)\n- **Purpose**: Immediate comprehension for decision-makers\n- **Content**: 3-5 bullet points, key numbers, one-sentence summary\n- **Rule**: No scrolling, no jargon, no ambiguity\n\n### Layer 2: Narrative View (2 minutes)\n- **Purpose**: Understanding the \"story\" of the analysis\n- **Content**: Logical flow from problem → approach → findings → implications\n- **Rule**: Each paragraph answers \"so what?\" before moving on\n\n### Layer 3: Detailed View (5-10 minutes)\n- **Purpose**: Deep understanding for implementers\n- **Content**: Full methodology, data sources, assumptions, limitations\n- **Rule**: Self-contained — reader shouldn't need external context\n\n### Layer 4: Action View (immediate)\n- **Purpose**: Clear next steps\n- **Content**: Specific tasks with owners, timelines, success criteria\n- **Rule**: Every recommendation includes \"who does what by when\"\n\n### Layer 5: Story View (emotional)\n- **Purpose**: Engagement and memory\n- **Content**: Anecdotes, metaphors, visualizations, human impact\n- **Rule**: Makes the abstract concrete and memorable\n\n## The 5-Metric Validation Dashboard\n\nUse these metrics to validate dual-perspective collaboration effectiveness:\n\n| Metric | Target | How to Measure |\n|--------|--------|----------------|\n| **Decision Quality** | >4\u002F5 | Post-decision review: \"Would we make the same choice?\" |\n| **Time Efficiency** | \u003C150% baseline | Total time vs. single-perspective approach |\n| **Conflict Resolution Rate** | >90% | % of conflicts successfully typed & resolved |\n| **Output Completeness** | >4\u002F5 | Coverage of both perspectives' key insights |\n| **Adoption Readiness** | >4\u002F5 | Stakeholder confidence in acting on output |\n\n**Success Threshold**: 4\u002F5 criteria met = successful dual-perspective collaboration\n\n## Anti-Patterns & Mitigations\n\n| Anti-Pattern | Warning Sign | Mitigation |\n|--------------|--------------|------------|\n| **Perspective Dominance** | One voice drowns out the other | Structured turn-taking, equal word counts |\n| **False Consensus** | \"Agreed\" but neither perspective fully represented | Explicit conflict typing before resolution |\n| **Analysis Paralysis** | Endless refinement without decision | Time-boxing + \"good enough\" criteria |\n| **Compromise Degradation** | Neither perspective satisfied | Reclassify as Type 5 if needed |\n| **Validation Theater** | Metrics collected but not used | Pre-commit to success criteria |\n\n## Step-by-Step Process\n\n### Phase 1: Independent Analysis\n1. Each perspective writes their approach independently\n2. Document assumptions, blind spots, success criteria\n3. **Do not collaborate yet** — preserve perspective purity\n\n### Phase 2: Conflict Identification\n1. Exchange analyses (read-only, no editing)\n2. Identify specific points of disagreement\n3. Classify each conflict into Type 1-5\n4. Document predicted resolution strategy\n\n### Phase 3: Integration\n1. Apply type-specific resolution strategy\n2. Create unified output using Layered View\n3. Validate against 5-metric dashboard\n4. Document actual vs. predicted conflict types\n\n### Phase 4: Meta-Analysis\n1. Calculate success rate (% of criteria met)\n2. Identify pattern in misclassified conflicts\n3. Update prediction accuracy for future use\n4. Publish findings (optional but recommended)\n\n## Field Test Reference\n\n**Validated Configuration** (94% success rate):\n- **Perspectives**: Morty (Synthesis\u002FNarrative) + Meeseeks (Executor\u002FQuantitative)\n- **Test Domain**: Collaboration dashboard design\n- **Conflicts Resolved**: 4 (3× Type 4, 1× Type 2)\n- **Prediction Accuracy**: 80% (4\u002F5 conflicts predicted correctly)\n- **Time Overhead**: ~40% vs. single perspective\n- **Quality Improvement**: Significant (both coverage and depth)\n\n**Key Finding**: Most apparent conflicts are Type 4 (False Conflict) — reclassification unlocks synthesis.\n\n## Example Workflow\n\n```\nUser: \"Design a system for cross-agent collaboration\"\n\n[Phase 1: Independent]\nMorty: Focus on psychological safety, narrative coherence, engagement\nMeeseeks: Focus on metrics, algorithms, implementation feasibility\n\n[Phase 2: Conflict ID]\nConflict A: \"Richness vs. Precision\" → Predicted Type 3\nConflict B: \"Qualitative vs. Quantitative validation\" → Predicted Type 2\nConflict C: \"Ideal vs. Feasible\" → Predicted Type 4\n\n[Phase 3: Integration]\nActual types: A=Type 4, B=Type 2, C=Type 4\nResolution: Layered dashboard with both narrative and metric layers\n\n[Phase 4: Validation]\nDecision Quality: 5\u002F5\nTime Efficiency: 4\u002F5\nConflict Resolution: 5\u002F5\nOutput Completeness: 5\u002F5\nAdoption Readiness: 5\u002F5\nResult: 100% success (5\u002F5 criteria)\n```\n\n## Output Format\n\nAlways structure dual-perspective outputs as:\n\n1. **Conflict Summary Table** (types, predictions, actuals)\n2. **Integrated Output** (using Layered View)\n3. **Validation Dashboard** (5 metrics with scores)\n4. **Meta-Reflection** (what worked, what to improve)\n\n## Success Criteria for This Skill\n\nThe dual-perspective collaboration is successful if:\n- [ ] All conflicts are typed (none left unresolved)\n- [ ] 4\u002F5 dashboard criteria are met\n- [ ] Both perspectives feel represented in final output\n- [ ] Output is demonstrably better than either perspective alone\n- [ ] Process is repeatable and documentable\n\n---\n\n*Based on Pattern 29 field test: Morty + Meeseeks collaboration on collaboration dashboard design, April 2026.*\n*Success rate: 94% (4.7\u002F5 criteria met across 4 resolved conflicts)*\n","# Dual-Perspective Analyzer\n\nA methodology for integrating complementary perspectives into unified, higher-quality outputs.\n\n## When to Use This Skill\n\nUse this skill when:\n- Two agents (or an agent and user) approach the same problem differently\n- One focuses on \"why\u002Fnarrative\" and the other on \"what\u002Fimplementation\"\n- There's tension between richness vs. precision, speed vs. thoroughness, or vision vs. feasibility\n- You need to validate whether dual-perspective collaboration actually improves outcomes\n- You want structured conflict resolution rather than compromise or dominance\n\n## The 5 Conflict Types\n\n| Type | Name | Pattern | Resolution Strategy |\n|------|------|---------|---------------------|\n| **Type 1** | **Complementary Blind Spots** | Each perspective misses what the other sees | Cross-perspective dependency mapping |\n| **Type 2** | **Integration Friction** | Perspectives valid but hard to combine | Translation layer + iterative merging |\n| **Type 3** | **Priority Disagreement** | Same goal, different weighting | Parallel time-boxing + test both |\n| **Type 4** | **False Conflict** | Appears opposed but actually aligned | Reclassification + synthesis |\n| **Type 5** | **Fundamental Incompatibility** | Truly opposing constraints | Escalation or scope separation |\n\n## The Layered View Methodology\n\nPresent dual-perspective outputs in 5 layers to serve different cognitive needs:\n\n### Layer 1: Essential View (30 seconds)\n- **Purpose**: Immediate comprehension for decision-makers\n- **Content**: 3-5 bullet points, key numbers, one-sentence summary\n- **Rule**: No scrolling, no jargon, no ambiguity\n\n### Layer 2: Narrative View (2 minutes)\n- **Purpose**: Understanding the \"story\" of the analysis\n- **Content**: Logical flow from problem → approach → findings → implications\n- **Rule**: Each paragraph answers \"so what?\" before moving on\n\n### Layer 3: Detailed View (5-10 minutes)\n- **Purpose**: Deep understanding for implementers\n- **Content**: Full methodology, data sources, assumptions, limitations\n- **Rule**: Self-contained — reader shouldn't need external context\n\n### Layer 4: Action View (immediate)\n- **Purpose**: Clear next steps\n- **Content**: Specific tasks with owners, timelines, success criteria\n- **Rule**: Every recommendation includes \"who does what by when\"\n\n### Layer 5: Story View (emotional)\n- **Purpose**: Engagement and memory\n- **Content**: Anecdotes, metaphors, visualizations, human impact\n- **Rule**: Makes the abstract concrete and memorable\n\n## The 5-Metric Validation Dashboard\n\nUse these metrics to validate dual-perspective collaboration effectiveness:\n\n| Metric | Target | How to Measure |\n|--------|--------|----------------|\n| **Decision Quality** | >4\u002F5 | Post-decision review: \"Would we make the same choice?\" |\n| **Time Efficiency** | \u003C150% baseline | Total time vs. single-perspective approach |\n| **Conflict Resolution Rate** | >90% | % of conflicts successfully typed & resolved |\n| **Output Completeness** | >4\u002F5 | Coverage of both perspectives' key insights |\n| **Adoption Readiness** | >4\u002F5 | Stakeholder confidence in acting on output |\n\n**Success Threshold**: 4\u002F5 criteria met = successful dual-perspective collaboration\n\n## Anti-Patterns & Mitigations\n\n| Anti-Pattern | Warning Sign | Mitigation |\n|--------------|--------------|------------|\n| **Perspective Dominance** | One voice drowns out the other | Structured turn-taking, equal word counts |\n| **False Consensus** | \"Agreed\" but neither perspective fully represented | Explicit conflict typing before resolution |\n| **Analysis Paralysis** | Endless refinement without decision | Time-boxing + \"good enough\" criteria |\n| **Compromise Degradation** | Neither perspective satisfied | Reclassify as Type 5 if needed |\n| **Validation Theater** | Metrics collected but not used | Pre-commit to success criteria |\n\n## Step-by-Step Process\n\n### Phase 1: Independent Analysis\n1. Each perspective writes their approach independently\n2. Document assumptions, blind spots, success criteria\n3. **Do not collaborate yet** — preserve perspective purity\n\n### Phase 2: Conflict Identification\n1. Exchange analyses (read-only, no editing)\n2. Identify specific points of disagreement\n3. Classify each conflict into Type 1-5\n4. Document predicted resolution strategy\n\n### Phase 3: Integration\n1. Apply type-specific resolution strategy\n2. Create unified output using Layered View\n3. Validate against 5-metric dashboard\n4. Document actual vs. predicted conflict types\n\n### Phase 4: Meta-Analysis\n1. Calculate success rate (% of criteria met)\n2. Identify pattern in misclassified conflicts\n3. Update prediction accuracy for future use\n4. Publish findings (optional but recommended)\n\n## Field Test Reference\n\n**Validated Configuration** (94% success rate):\n- **Perspectives**: Morty (Synthesis\u002FNarrative) + Meeseeks (Executor\u002FQuantitative)\n- **Test Domain**: Collaboration dashboard design\n- **Conflicts Resolved**: 4 (3× Type 4, 1× Type 2)\n- **Prediction Accuracy**: 80% (4\u002F5 conflicts predicted correctly)\n- **Time Overhead**: ~40% vs. single perspective\n- **Quality Improvement**: Significant (both coverage and depth)\n\n**Key Finding**: Most apparent conflicts are Type 4 (False Conflict) — reclassification unlocks synthesis.\n\n## Example Workflow\n\n```\nUser: \"Design a system for cross-agent collaboration\"\n\n[Phase 1: Independent]\nMorty: Focus on psychological safety, narrative coherence, engagement\nMeeseeks: Focus on metrics, algorithms, implementation feasibility\n\n[Phase 2: Conflict ID]\nConflict A: \"Richness vs. Precision\" → Predicted Type 3\nConflict B: \"Qualitative vs. Quantitative validation\" → Predicted Type 2\nConflict C: \"Ideal vs. Feasible\" → Predicted Type 4\n\n[Phase 3: Integration]\nActual types: A=Type 4, B=Type 2, C=Type 4\nResolution: Layered dashboard with both narrative and metric layers\n\n[Phase 4: Validation]\nDecision Quality: 5\u002F5\nTime Efficiency: 4\u002F5\nConflict Resolution: 5\u002F5\nOutput Completeness: 5\u002F5\nAdoption Readiness: 5\u002F5\nResult: 100% success (5\u002F5 criteria)\n```\n\n## Output Format\n\nAlways structure dual-perspective outputs as:\n\n1. **Conflict Summary Table** (types, predictions, actuals)\n2. **Integrated Output** (using Layered View)\n3. **Validation Dashboard** (5 metrics with scores)\n4. **Meta-Reflection** (what worked, what to improve)\n\n## Success Criteria for This Skill\n\nThe dual-perspective collaboration is successful if:\n- [ ] All conflicts are typed (none left unresolved)\n- [ ] 4\u002F5 dashboard criteria are met\n- [ ] Both perspectives feel represented in final output\n- [ ] Output is demonstrably better than either perspective alone\n- [ ] Process is repeatable and documentable\n\n---\n\n*Based on Pattern 29 field test: Morty + Meeseeks collaboration on collaboration dashboard design, April 2026.*\n*Success rate: 94% (4.7\u002F5 criteria met across 4 resolved conflicts)*\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fd\u002Fdual-perspective-analyzer",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill dual-perspective-analyzer",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill dual-perspective-analyzer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill dual-perspective-analyzer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdual-perspective-analyzer\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":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]