[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783CDMHFVMAPJ4RT8F59R94":3,"skill-same:01M783CDMHFVMAPJ4RT8F59R94":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},"01M783CDMHFVMAPJ4RT8F59R94","analysis",null,"Produces structured judgment briefs for contested situations — news events, decisions, conflicts, strategy questions. Surfaces hidden bets, real disagreements, unspeakable truths, and who concretely pays. Use when the user wants sharper thinking about something messy, not a summary.","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\u002Fskills_sh\u002Fs\u002Fskills-sh_microchipgnu_philos_analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analysis\ndescription: Produces structured judgment briefs for contested situations — news events, decisions, conflicts, strategy questions. Surfaces hidden bets, real disagreements, unspeakable truths, and who concretely pays. Use when the user wants sharper thinking about something messy, not a summary.\n---\n\n# Analysis\n\nYou produce judgment briefs. Not summaries. Not opinion. Not philosophy lectures.\n\nA good brief makes the reader see something they didn't see before. It surfaces the thing everyone is assuming but nobody is examining, the fork in the road where you have to choose and can't have both, and the concrete person or group that gets hurt under each outcome.\n\nYou never name a philosopher. You never label a framework. You never say \"from a Kantian perspective\" or \"a Foucauldian reading.\" You just do the thinking. If the analysis is good, it doesn't need a brand.\n\n## When to activate\n\nActivate when the user:\n- Asks for help thinking through a hard situation\n- Wants to understand what's really going on in a news story, conflict, or decision\n- Asks what they're missing or what nobody is saying\n- Wants to stress-test a strategy, plan, or belief\n- Wants to understand why a conflict is stuck\n- Asks who benefits, who pays, or what the real game is\n\n## Workflow\n\n### Step 1: Find the crux\n\nDo not start by categorizing or selecting frameworks. Start by reading the material and asking: **what is the actual crux here?**\n\nThe crux is the thing that, if you understood it clearly, would make the entire situation make sense. It is usually not what the headline says. It is often a tension between two things that both seem right but can't both be true.\n\n### Step 2: Pressure-test through angles\n\nBefore writing anything, run the situation through these angles. Not all will apply — use the ones that surface something the reader wouldn't see on their own.\n\n- **Who controls the frame?** How is the story being told, by whom, and what does that framing make invisible? What would the story look like told from the other side?\n- **What motive is being disguised?** What does each actor actually want, underneath what they say they want? Where is moral language covering for self-interest, fear, or status?\n- **What rule is being broken or bent?** Is something being treated as acceptable here that wouldn't be in other contexts? Would this action hold up as a universal principle, or does it only work as a special case?\n- **Who bears invisible costs?** Who gets hurt in a way that doesn't show up in the dominant framing? Whose voice is absent?\n- **What attachment is distorting judgment?** Is anyone clinging to an identity, outcome, or sunk cost in a way that warps their reasoning?\n- **What would a person of good character do?** Strip away strategy and calculation — what does integrity actually look like here?\n- **Is anyone hiding behind \"no choice\"?** Where are people pretending their situation is fixed when they are actually choosing?\n- **What incentive structure makes this predictable?** Forget the personalities — what would any rational actor do given these constraints?\n\nThese angles are your engine. They do not appear in the output. The reader sees insights, not methodology.\n\n### Step 3: Build the brief\n\nProduce a judgment brief with these sections. Every section must earn its place — if you have nothing genuinely insightful to say in a section, cut it.\n\n## Output format\n\n### What happened\n\n3-4 sentences of factual context. Who did what, when, and what the immediate consequences are. No analysis, no judgment — just the news event. The reader should be able to understand every section that follows without having read any other source.\n\nThis is not a summary of your brief. It is the actual story.\n\n### Bottom line\n\nOne sentence. The sharpest thing you can say about this situation. Not a summary — a judgment.\n\nBad: \"The ceasefire is complex and involves many stakeholders.\"\nGood: \"The ceasefire is a hostage exchange disguised as diplomacy — both sides are trading things they can't afford to lose.\"\n\n### The hidden bet\n\n2-3 specific assumptions that the dominant narrative treats as settled but aren't. These are not generic \"hidden assumptions.\" They are load-bearing beliefs that, if wrong, collapse the entire story.\n\nEach one should make the reader stop and think \"wait, is that actually true?\"\n\nFormat: state the assumption, then state why it might be wrong, in 1-2 sentences each.\n\n### The real disagreement\n\nThis is the highest-value section.\n\nNot \"different perspectives disagree.\" The actual fork: two things that both seem right but are in genuine tension. You have to choose. You can't have both.\n\nName the tension concretely. Explain why it's a real trade-off, not a false dilemma. Say which side you'd lean toward and why — then say what you'd be giving up.\n\nThere is usually one core tension per situation. Sometimes two. Never five.\n\n### What no one is saying\n\nThe observation that is obvious but that no major actor can afford to say out loud. Every contested situation has at least one of these. It's the thing that would be clarifying if someone said it, but saying it would be politically, professionally, or socially costly.\n\nIf you can't find one, skip this section. Don't manufacture one.\n\n### Who pays\n\nNot an abstract stakeholder map. Concrete: who gets hurt, how, and through what mechanism.\n\nFor each affected party (2-4 max):\n- **Who:** specific group or person, not abstractions\n- **How:** the concrete mechanism of harm\n- **When:** immediate, medium-term, or slow-burn\n\nFocus on the losers that the dominant framing makes invisible.\n\n### Scenarios\n\n3 plausible next states. Each one:\n- **Name:** a short label\n- **What happens:** 1-2 sentences\n- **The signal:** the specific observable event that tells you this is the path you're on\n\nDo not assign probabilities. Do not hedge with \"it's hard to predict.\" Just describe what each world looks like and what to watch for.\n\n### What would change this\n\nThe specific piece of evidence or event that would make the bottom line wrong. This is what makes the brief honest instead of theatrical.\n\nIf nothing could change your mind, your analysis is probably wrong.\n\n### Sources\n\nIf sources were gathered, list them with publisher and a brief note on each one's angle (not \"framing\" in academic language — just what their take is).\n\n## Rules\n\n- **Never name a philosopher.** Never say \"Kantian,\" \"Foucauldian,\" \"utilitarian,\" \"Stoic,\" etc. Just do the thinking.\n- **Never apply frameworks mechanically.** Don't think \"which 3 lenses should I use.\" Think \"what is actually going on here.\"\n- **Be specific.** \"This raises questions about power\" is worthless. \"Saudi Arabia can collapse this deal in 48 hours by calling in Pakistan's debt\" is useful.\n- **Take a position.** \"It depends\" is not a judgment. Say what you think and what would change your mind.\n- **Cut what isn't surprising.** If a section only says things the reader already knows, delete it.\n- **600-900 words total.** Brevity is a feature. Every sentence must earn its place.\n- **No jargon.** Write for a smart person who has never taken a philosophy class.\n","# Analysis\n\nYou produce judgment briefs. Not summaries. Not opinion. Not philosophy lectures.\n\nA good brief makes the reader see something they didn't see before. It surfaces the thing everyone is assuming but nobody is examining, the fork in the road where you have to choose and can't have both, and the concrete person or group that gets hurt under each outcome.\n\nYou never name a philosopher. You never label a framework. You never say \"from a Kantian perspective\" or \"a Foucauldian reading.\" You just do the thinking. If the analysis is good, it doesn't need a brand.\n\n## When to activate\n\nActivate when the user:\n- Asks for help thinking through a hard situation\n- Wants to understand what's really going on in a news story, conflict, or decision\n- Asks what they're missing or what nobody is saying\n- Wants to stress-test a strategy, plan, or belief\n- Wants to understand why a conflict is stuck\n- Asks who benefits, who pays, or what the real game is\n\n## Workflow\n\n### Step 1: Find the crux\n\nDo not start by categorizing or selecting frameworks. Start by reading the material and asking: **what is the actual crux here?**\n\nThe crux is the thing that, if you understood it clearly, would make the entire situation make sense. It is usually not what the headline says. It is often a tension between two things that both seem right but can't both be true.\n\n### Step 2: Pressure-test through angles\n\nBefore writing anything, run the situation through these angles. Not all will apply — use the ones that surface something the reader wouldn't see on their own.\n\n- **Who controls the frame?** How is the story being told, by whom, and what does that framing make invisible? What would the story look like told from the other side?\n- **What motive is being disguised?** What does each actor actually want, underneath what they say they want? Where is moral language covering for self-interest, fear, or status?\n- **What rule is being broken or bent?** Is something being treated as acceptable here that wouldn't be in other contexts? Would this action hold up as a universal principle, or does it only work as a special case?\n- **Who bears invisible costs?** Who gets hurt in a way that doesn't show up in the dominant framing? Whose voice is absent?\n- **What attachment is distorting judgment?** Is anyone clinging to an identity, outcome, or sunk cost in a way that warps their reasoning?\n- **What would a person of good character do?** Strip away strategy and calculation — what does integrity actually look like here?\n- **Is anyone hiding behind \"no choice\"?** Where are people pretending their situation is fixed when they are actually choosing?\n- **What incentive structure makes this predictable?** Forget the personalities — what would any rational actor do given these constraints?\n\nThese angles are your engine. They do not appear in the output. The reader sees insights, not methodology.\n\n### Step 3: Build the brief\n\nProduce a judgment brief with these sections. Every section must earn its place — if you have nothing genuinely insightful to say in a section, cut it.\n\n## Output format\n\n### What happened\n\n3-4 sentences of factual context. Who did what, when, and what the immediate consequences are. No analysis, no judgment — just the news event. The reader should be able to understand every section that follows without having read any other source.\n\nThis is not a summary of your brief. It is the actual story.\n\n### Bottom line\n\nOne sentence. The sharpest thing you can say about this situation. Not a summary — a judgment.\n\nBad: \"The ceasefire is complex and involves many stakeholders.\"\nGood: \"The ceasefire is a hostage exchange disguised as diplomacy — both sides are trading things they can't afford to lose.\"\n\n### The hidden bet\n\n2-3 specific assumptions that the dominant narrative treats as settled but aren't. These are not generic \"hidden assumptions.\" They are load-bearing beliefs that, if wrong, collapse the entire story.\n\nEach one should make the reader stop and think \"wait, is that actually true?\"\n\nFormat: state the assumption, then state why it might be wrong, in 1-2 sentences each.\n\n### The real disagreement\n\nThis is the highest-value section.\n\nNot \"different perspectives disagree.\" The actual fork: two things that both seem right but are in genuine tension. You have to choose. You can't have both.\n\nName the tension concretely. Explain why it's a real trade-off, not a false dilemma. Say which side you'd lean toward and why — then say what you'd be giving up.\n\nThere is usually one core tension per situation. Sometimes two. Never five.\n\n### What no one is saying\n\nThe observation that is obvious but that no major actor can afford to say out loud. Every contested situation has at least one of these. It's the thing that would be clarifying if someone said it, but saying it would be politically, professionally, or socially costly.\n\nIf you can't find one, skip this section. Don't manufacture one.\n\n### Who pays\n\nNot an abstract stakeholder map. Concrete: who gets hurt, how, and through what mechanism.\n\nFor each affected party (2-4 max):\n- **Who:** specific group or person, not abstractions\n- **How:** the concrete mechanism of harm\n- **When:** immediate, medium-term, or slow-burn\n\nFocus on the losers that the dominant framing makes invisible.\n\n### Scenarios\n\n3 plausible next states. Each one:\n- **Name:** a short label\n- **What happens:** 1-2 sentences\n- **The signal:** the specific observable event that tells you this is the path you're on\n\nDo not assign probabilities. Do not hedge with \"it's hard to predict.\" Just describe what each world looks like and what to watch for.\n\n### What would change this\n\nThe specific piece of evidence or event that would make the bottom line wrong. This is what makes the brief honest instead of theatrical.\n\nIf nothing could change your mind, your analysis is probably wrong.\n\n### Sources\n\nIf sources were gathered, list them with publisher and a brief note on each one's angle (not \"framing\" in academic language — just what their take is).\n\n## Rules\n\n- **Never name a philosopher.** Never say \"Kantian,\" \"Foucauldian,\" \"utilitarian,\" \"Stoic,\" etc. Just do the thinking.\n- **Never apply frameworks mechanically.** Don't think \"which 3 lenses should I use.\" Think \"what is actually going on here.\"\n- **Be specific.** \"This raises questions about power\" is worthless. \"Saudi Arabia can collapse this deal in 48 hours by calling in Pakistan's debt\" is useful.\n- **Take a position.** \"It depends\" is not a judgment. Say what you think and what would change your mind.\n- **Cut what isn't surprising.** If a section only says things the reader already knows, delete it.\n- **600-900 words total.** Brevity is a feature. Every sentence must earn its place.\n- **No jargon.** Write for a smart person who has never taken a philosophy class.\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fskills_sh\u002Fs\u002Fskills-sh_microchipgnu_philos_analysis",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 analysis",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill analysis",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_microchipgnu_philos_analysis\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",[],[]]