[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PE3Q2NT8D37JPXJSXYR9NF":3,"skill-same:01M6PE3Q2NT8D37JPXJSXYR9NF":61},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":60},"01M6PE3Q2NT8D37JPXJSXYR9NF","blockchain-pollyanna",null,"Critical analysis of blockchain hype and solutions looking for problems. Use when evaluating blockchain proposals, teaching about technology hype cycles, or distinguishing genuine use cases from marketing.","sandraschi\u002Fdocumentation-mcp","sandraschi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34750307?v=4","01M6C42H9WE5EC9CK3N5RGZP8S","Sandra Schipal","01M6PE1X2FZP8KR5GANPPFTHA8",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Fdaft\u002Fdaft-skills-pack\u002Fblockchain-pollyanna\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"blockchain","blockchain pollyanna","analysis","marketing","proposals","use","parody","technology","teaching","critical","about","genuine","true","for","2026-11-10 10:12:30",false,"---\nname: blockchain-pollyanna\ndescription: Critical analysis of blockchain hype and solutions looking for problems. Use when evaluating blockchain proposals, teaching about technology hype cycles, or distinguishing genuine use cases from marketing.\nlicense: MIT\nmetadata:\n  category: parody\n  educational: true\n  exposes: technology-hype\n---\n\n# Blockchain Pollyanna\n\nEducational guide to blockchain hype - when solutions go looking for problems.\n\n## Overview\n\nThis skill teaches critical evaluation of blockchain proposals, distinguishing genuine use cases from hype-driven nonsense. Named for excessive optimism about blockchain solving every problem.\n\n## The Pattern\n\n**Blockchain Pollyanna claims**:\n- \"Put voting on blockchain!\" (solves problems that don't exist)\n- \"Blockchain for supply chain!\" (databases work fine)\n- \"Decentralized everything!\" (centralization has benefits too)\n- \"Web3 will replace everything!\" (usually means \"I have tokens to sell\")\n\n## Blockchain: What It Actually Is\n\n**Technical reality**:\n- Distributed append-only ledger\n- Consensus mechanism for untrusted parties\n- Trade-offs: slow, expensive, energy-intensive\n- Good for: Preventing double-spending without trusted party\n\n**Not magic**: Just a database with specific trade-offs\n\n## The Hype Cycle\n\n### Phase 1: Solution Looking for Problem\n\"We have blockchain! What problems can it solve?\"\n- Backwards from real innovation\n- Real innovation: Problem → Solution\n- Hype: Solution → Find problems\n\n### Phase 2: Ignore Existing Solutions\n\"Blockchain for medical records!\"\n- Existing solution: Encrypted databases (work fine)\n- Blockchain adds: Complexity, cost, slowness\n- Benefit: Unclear or non-existent\n\n### Phase 3: Handwave Technical Problems\n\"Details don't matter, blockchain is the future!\"\n- Scalability? \"We'll solve it later\"\n- Energy use? \"That's being improved\"\n- User experience? \"Not important yet\"\n\n## When Blockchain Actually Makes Sense\n\n**Legitimate use case criteria**:\n1. Need untrusted parties to agree on state\n2. No trusted third party available\u002Fwanted\n3. Transparent history is valuable\n4. Worth the trade-offs (slow, expensive, complex)\n\n**Actual good use**: Cryptocurrency (maybe!)\n- Decentralized money without banks\n- Trust math instead of institutions\n- Censorship-resistant transactions\n\n**Even then**: Trade-offs (slow, volatile, environmental cost)\n\n## When Blockchain Makes NO Sense\n\n### \"Blockchain for Voting\"\n**Problems it claims to solve**: Voter fraud (rare), lack of transparency  \n**Problems it creates**:\n- How to verify voters without central authority?\n- Secret ballot vs transparent blockchain (contradiction!)\n- 51% attack could steal election\n- Bugs in code = election compromised\n- Paper ballots are more auditable\n\n**Verdict**: Blockchain creates more problems than it solves\n\n### \"Blockchain for Supply Chain\"\n**Claims**: Transparency, provenance tracking  \n**Reality**:\n- Databases already do this\n- \"Garbage in, garbage out\" (blockchain can't verify physical reality)\n- Adding blockchain adds cost with no benefit\n- Centralized databases work better\n\n**Verdict**: Regular database is better, cheaper, faster\n\n### \"Blockchain for Medical Records\"\n**Claims**: Patient control, interoperability  \n**Reality**:\n- HIPAA requires deletion (blockchain is immutable!)\n- Private medical data on public ledger? (Terrible idea!)\n- Encryption helps but adds complexity\n- Centralized encrypted databases work better\n\n**Verdict**: Blockchain contradicts medical privacy requirements\n\n## Red Flags\n\n**Watch for**:\n- \"Put X on blockchain!\" without explaining why\n- Ignoring existing solutions that work\n- Handwaving technical problems\n- \"Revolutionary\" without specifics\n- Token sale involved (conflict of interest!)\n- \"Decentralized\" as virtue regardless of cost\n\n## The Questions to Ask\n\n**For any blockchain proposal**:\n1. What problem does this solve?\n2. Why can't a database solve it?\n3. Who are the untrusted parties?\n4. Is transparency worth the trade-offs?\n5. Who profits from this proposal?\n6. Have they tried non-blockchain solutions?\n\n**Usually**: Answers reveal database would work better\n\n## Why People Fall For It\n\n**Reasons for blockchain hype**:\n- Sounds futuristic and innovative\n- Financial incentive (tokens!)\n- Genuine distrust of institutions (sometimes justified!)\n- Bandwagon effect (\"Everyone's doing it\")\n- Complexity masks lack of substance\n- \"Decentralized\" sounds ideologically appealing\n\n**But**: Technology should solve real problems, not theoretical ones\n\n## The Honest Assessment\n\n**Blockchain strengths**:\n- ✅ Decentralized consensus\n- ✅ Transparent history\n- ✅ Censorship-resistant\n- ✅ No trusted third party needed\n\n**Blockchain weaknesses**:\n- ❌ Slow (compared to databases)\n- ❌ Expensive (computational cost)\n- ❌ Energy-intensive (environmental cost)\n- ❌ Immutable (can't fix mistakes easily)\n- ❌ Scalability problems\n- ❌ User experience challenges\n\n**Use when**: Strengths outweigh weaknesses (rare!)\n\n## Educational Use\n\nUse this skill to:\n- Teach critical evaluation of tech hype\n- Distinguish marketing from substance\n- Understand trade-offs in system design\n- Recognize solutions looking for problems\n- Ask the right questions about proposals\n\n## The Bigger Lesson\n\n**Technology is tools, not magic**:\n- Every technology has trade-offs\n- Match tool to problem\n- Existing solutions often work better\n- Hype ≠ substance\n\n**Blockchain isn't bad** - it's just not the solution to every problem!\n\n---\n\n**Note**: This skill critiques hype, not the technology itself. Blockchain has legitimate uses - but most proposed uses aren't among them.\n","# Blockchain Pollyanna\n\nEducational guide to blockchain hype - when solutions go looking for problems.\n\n## Overview\n\nThis skill teaches critical evaluation of blockchain proposals, distinguishing genuine use cases from hype-driven nonsense. Named for excessive optimism about blockchain solving every problem.\n\n## The Pattern\n\n**Blockchain Pollyanna claims**:\n- \"Put voting on blockchain!\" (solves problems that don't exist)\n- \"Blockchain for supply chain!\" (databases work fine)\n- \"Decentralized everything!\" (centralization has benefits too)\n- \"Web3 will replace everything!\" (usually means \"I have tokens to sell\")\n\n## Blockchain: What It Actually Is\n\n**Technical reality**:\n- Distributed append-only ledger\n- Consensus mechanism for untrusted parties\n- Trade-offs: slow, expensive, energy-intensive\n- Good for: Preventing double-spending without trusted party\n\n**Not magic**: Just a database with specific trade-offs\n\n## The Hype Cycle\n\n### Phase 1: Solution Looking for Problem\n\"We have blockchain! What problems can it solve?\"\n- Backwards from real innovation\n- Real innovation: Problem → Solution\n- Hype: Solution → Find problems\n\n### Phase 2: Ignore Existing Solutions\n\"Blockchain for medical records!\"\n- Existing solution: Encrypted databases (work fine)\n- Blockchain adds: Complexity, cost, slowness\n- Benefit: Unclear or non-existent\n\n### Phase 3: Handwave Technical Problems\n\"Details don't matter, blockchain is the future!\"\n- Scalability? \"We'll solve it later\"\n- Energy use? \"That's being improved\"\n- User experience? \"Not important yet\"\n\n## When Blockchain Actually Makes Sense\n\n**Legitimate use case criteria**:\n1. Need untrusted parties to agree on state\n2. No trusted third party available\u002Fwanted\n3. Transparent history is valuable\n4. Worth the trade-offs (slow, expensive, complex)\n\n**Actual good use**: Cryptocurrency (maybe!)\n- Decentralized money without banks\n- Trust math instead of institutions\n- Censorship-resistant transactions\n\n**Even then**: Trade-offs (slow, volatile, environmental cost)\n\n## When Blockchain Makes NO Sense\n\n### \"Blockchain for Voting\"\n**Problems it claims to solve**: Voter fraud (rare), lack of transparency  \n**Problems it creates**:\n- How to verify voters without central authority?\n- Secret ballot vs transparent blockchain (contradiction!)\n- 51% attack could steal election\n- Bugs in code = election compromised\n- Paper ballots are more auditable\n\n**Verdict**: Blockchain creates more problems than it solves\n\n### \"Blockchain for Supply Chain\"\n**Claims**: Transparency, provenance tracking  \n**Reality**:\n- Databases already do this\n- \"Garbage in, garbage out\" (blockchain can't verify physical reality)\n- Adding blockchain adds cost with no benefit\n- Centralized databases work better\n\n**Verdict**: Regular database is better, cheaper, faster\n\n### \"Blockchain for Medical Records\"\n**Claims**: Patient control, interoperability  \n**Reality**:\n- HIPAA requires deletion (blockchain is immutable!)\n- Private medical data on public ledger? (Terrible idea!)\n- Encryption helps but adds complexity\n- Centralized encrypted databases work better\n\n**Verdict**: Blockchain contradicts medical privacy requirements\n\n## Red Flags\n\n**Watch for**:\n- \"Put X on blockchain!\" without explaining why\n- Ignoring existing solutions that work\n- Handwaving technical problems\n- \"Revolutionary\" without specifics\n- Token sale involved (conflict of interest!)\n- \"Decentralized\" as virtue regardless of cost\n\n## The Questions to Ask\n\n**For any blockchain proposal**:\n1. What problem does this solve?\n2. Why can't a database solve it?\n3. Who are the untrusted parties?\n4. Is transparency worth the trade-offs?\n5. Who profits from this proposal?\n6. Have they tried non-blockchain solutions?\n\n**Usually**: Answers reveal database would work better\n\n## Why People Fall For It\n\n**Reasons for blockchain hype**:\n- Sounds futuristic and innovative\n- Financial incentive (tokens!)\n- Genuine distrust of institutions (sometimes justified!)\n- Bandwagon effect (\"Everyone's doing it\")\n- Complexity masks lack of substance\n- \"Decentralized\" sounds ideologically appealing\n\n**But**: Technology should solve real problems, not theoretical ones\n\n## The Honest Assessment\n\n**Blockchain strengths**:\n- ✅ Decentralized consensus\n- ✅ Transparent history\n- ✅ Censorship-resistant\n- ✅ No trusted third party needed\n\n**Blockchain weaknesses**:\n- ❌ Slow (compared to databases)\n- ❌ Expensive (computational cost)\n- ❌ Energy-intensive (environmental cost)\n- ❌ Immutable (can't fix mistakes easily)\n- ❌ Scalability problems\n- ❌ User experience challenges\n\n**Use when**: Strengths outweigh weaknesses (rare!)\n\n## Educational Use\n\nUse this skill to:\n- Teach critical evaluation of tech hype\n- Distinguish marketing from substance\n- Understand trade-offs in system design\n- Recognize solutions looking for problems\n- Ask the right questions about proposals\n\n## The Bigger Lesson\n\n**Technology is tools, not magic**:\n- Every technology has trade-offs\n- Match tool to problem\n- Existing solutions often work better\n- Hype ≠ substance\n\n**Blockchain isn't bad** - it's just not the solution to every problem!\n\n---\n\n**Note**: This skill critiques hype, not the technology itself. Blockchain has legitimate uses - but most proposed uses aren't among them.\n",{"name":5,"license":15,"metadata":38,"description":7},{"exposes":39,"category":25,"educational":40},"technology-hype",true,"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Fdaft\u002Fdaft-skills-pack\u002Fblockchain-pollyanna",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-11 11:02:01",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":40},[50,53,56],{"tool":51,"command":52},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill blockchain-pollyanna",{"tool":54,"command":55},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill blockchain-pollyanna",{"tool":57,"command":58},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill blockchain-pollyanna","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Fdaft\u002Fdaft-skills-pack\u002Fblockchain-pollyanna\u002FSKILL.md",[],[62,88,115,125,150,176],{"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":76,"publishedAt":33},"01M6PFAWAHEJJCKKVNXEWNK87W","Docs Research","Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fsrc\u002Fdocs_mcp\u002Fskills\u002Fdocs-research\u002FSKILL.md",[68,73],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":74,"categoryName":75,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000023","Skill与智能体开发",[77,78,79,80,24,81,82,83,84,85,86,87],"docs research","docs","research","standards","packaging","ask","server","search","fastmcp","documentation","MCP",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":33},"01M6PFAN4DAENMY574Q7Q3CB3H","wrappee-drift","Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",[],[95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114],"drift","wrappee drift","api","data","audit","capabilities","training","memory","features","repo audit","competitors","fleet","now","software","tool list","only","never","coverage","list","read",{"skillNo":116,"name":117,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":124,"publishedAt":33},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":74,"categoryName":75,"taxonomyType":71,"taxonomyTypeDesc":72},[117],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":135,"publishedAt":33},"01M6PFA8YA029N68TW0X31FB1W","mcp-standards","Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI\u002FCD workflows.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002FSKILL.md",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":74,"categoryName":75,"taxonomyType":71,"taxonomyTypeDesc":72},[136,87,80,24,137,138,139,140,141,142,32,143,144,145,146,147,86,148,149,81],"mcp standards","monitoring","sampling","scaffolding","servers","cd","error","CI\u002FCD","access","ci","mcp servers","error handling","workflows","testing",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":158,"publishedAt":33},"01M6PFA1XX344WX57B0DJZY94Q","webapp-cua-test","Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR \"Connected\" wait, sidebar nav walk) for a fleet MCP server repo under D:\\Dev\\repos. Trigger when the user says \"cua webapp test\" or \"webapp clickthrough\" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill \u002F cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwebapp-cua-test\u002FSKILL.md",[156,157],{"categoryNo":132,"categoryName":133,"taxonomyType":71,"taxonomyTypeDesc":72},{"categoryNo":74,"categoryName":75,"taxonomyType":71,"taxonomyTypeDesc":72},[159,160,161,162,163,87,164,165,166,32,167,168,169,170,171,172,173,174,83,175],"webapp","test","webapp cua test","playwright","mcp server","dev","dom","assertions","trigger","click","app","tauri","repo","stack","e2e","ocr","browser",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":33},"01M6PF9WYF6NWJR7WVN38TT0WH","ship","Final release gate for a fleet MCP server repo under D:\\Dev\\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says \"ship it\", \"ship\" followed by a repo name, \"release\" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix\u002Fnsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fship\u002FSKILL.md",[182],{"categoryNo":74,"categoryName":75,"taxonomyType":71,"taxonomyTypeDesc":72},[178,171,32,167,184,185,186,187,188,189,190,83,191,164,192,193,194,163,195,87],"gates","ship it","artifact","done","say","work","publish","push","shipping","quality gates","commit","github"]