[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XB2EWHJCWG1VXDDXYXPCC":3,"skill-same:01M77XB2EWHJCWG1VXDDXYXPCC":49},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M77XB2EWHJCWG1VXDDXYXPCC","article-writing",null,"Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.","503496348-ops\u002Fmischief-production","503496348-ops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266905914?v=4","01M77X5J7XQWWZGT8998HDGXQM","AtomCollide","01M77X5J8V78Y3NXMY6BBC75X9",2,"MIT","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-article-writing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: article-writing\ndescription: Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.\nmetadata:\n  origin: HCP\n---\n\n# Article Writing\n\nWrite long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.\n\n## When to Activate\n\n- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues\n- turning notes, transcripts, or research into polished articles\n- matching an existing founder, operator, or brand voice from examples\n- tightening structure, pacing, and evidence in already-written long-form copy\n\n## Core Rules\n\n1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.\n2. Explain after the example, not before.\n3. Keep sentences tight unless the source voice is intentionally expansive.\n4. Use proof instead of adjectives.\n5. Never invent facts, credibility, or customer evidence.\n\n## Voice Handling\n\nIf the user wants a specific voice, run `brand-voice` first and reuse its `VOICE PROFILE`.\nDo not duplicate a second style-analysis pass here unless the user explicitly asks for one.\n\nIf no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.\n\n## Banned Patterns\n\nDelete and rewrite any of these:\n- \"In today's rapidly evolving landscape\"\n- \"game-changer\", \"cutting-edge\", \"revolutionary\"\n- \"here's why this matters\" as a standalone bridge\n- fake vulnerability arcs\n- a closing question added only to juice engagement\n- biography padding that does not move the argument\n- generic AI throat-clearing that delays the point\n\n## Writing Process\n\n1. Clarify the audience and purpose.\n2. Build a hard outline with one job per section.\n3. Start sections with proof, artifact, conflict, or example.\n4. Expand only where the next sentence earns space.\n5. Cut anything that sounds templated, overexplained, or self-congratulatory.\n\n## Structure Guidance\n\n### Technical Guides\n\n- open with what the reader gets\n- use code, commands, screenshots, or concrete output in major sections\n- end with actionable takeaways, not a soft recap\n\n### Essays \u002F Opinion\n\n- start with tension, contradiction, or a specific observation\n- keep one argument thread per section\n- make opinions answer to evidence\n\n### Newsletters\n\n- keep the first screen doing real work\n- do not front-load diary filler\n- use section labels only when they improve scanability\n\n## Quality Gate\n\nBefore delivering:\n- factual claims are backed by provided sources\n- generic AI transitions are gone\n- the voice matches the supplied examples or the agreed `VOICE PROFILE`\n- every section adds something new\n- formatting matches the intended medium\n","# Article Writing\n\nWrite long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.\n\n## When to Activate\n\n- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues\n- turning notes, transcripts, or research into polished articles\n- matching an existing founder, operator, or brand voice from examples\n- tightening structure, pacing, and evidence in already-written long-form copy\n\n## Core Rules\n\n1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.\n2. Explain after the example, not before.\n3. Keep sentences tight unless the source voice is intentionally expansive.\n4. Use proof instead of adjectives.\n5. Never invent facts, credibility, or customer evidence.\n\n## Voice Handling\n\nIf the user wants a specific voice, run `brand-voice` first and reuse its `VOICE PROFILE`.\nDo not duplicate a second style-analysis pass here unless the user explicitly asks for one.\n\nIf no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.\n\n## Banned Patterns\n\nDelete and rewrite any of these:\n- \"In today's rapidly evolving landscape\"\n- \"game-changer\", \"cutting-edge\", \"revolutionary\"\n- \"here's why this matters\" as a standalone bridge\n- fake vulnerability arcs\n- a closing question added only to juice engagement\n- biography padding that does not move the argument\n- generic AI throat-clearing that delays the point\n\n## Writing Process\n\n1. Clarify the audience and purpose.\n2. Build a hard outline with one job per section.\n3. Start sections with proof, artifact, conflict, or example.\n4. Expand only where the next sentence earns space.\n5. Cut anything that sounds templated, overexplained, or self-congratulatory.\n\n## Structure Guidance\n\n### Technical Guides\n\n- open with what the reader gets\n- use code, commands, screenshots, or concrete output in major sections\n- end with actionable takeaways, not a soft recap\n\n### Essays \u002F Opinion\n\n- start with tension, contradiction, or a specific observation\n- keep one argument thread per section\n- make opinions answer to evidence\n\n### Newsletters\n\n- keep the first screen doing real work\n- do not front-load diary filler\n- use section labels only when they improve scanability\n\n## Quality Gate\n\nBefore delivering:\n- factual claims are backed by provided sources\n- generic AI transitions are gone\n- the voice matches the supplied examples or the agreed `VOICE PROFILE`\n- every section adds something new\n- formatting matches the intended medium\n",{"name":5,"metadata":24,"description":7},{"origin":25},"HCP","main","c9103dbad48ef3005f163584d0f2abd4591217f6","skills\u002Fecc-article-writing",1,"https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production","https:\u002F\u002Fgithub.com\u002F503496348-ops","https:\u002F\u002F503496348-ops.github.io\u002Fatomcollide-product-matrix\u002F#tree","元素碰撞-AtomCollide-AI 智能体实验室 测试人专属成长社群 正式招募\r\n我们的目标很纯粹：连接每一位测试工程师\u002FAI使用探索与爱好者，让你在这里既能扎实打磨技术硬实力，也能打通职业晋升的新通路，这是一个专注于AI领域的开源组","2026-07-30 00:35:42",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add 503496348-ops\u002Fmischief-production --skill article-writing",{"tool":41,"command":42},"bunx","bunx skills add 503496348-ops\u002Fmischief-production --skill article-writing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add 503496348-ops\u002Fmischief-production --skill article-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-article-writing\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M77YG7NPZHE751W9QGK3H9ED","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-skills\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77YG4HPYH0GJP974DZ6KCPQ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-plans\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77YFZW1FZ1GVC5C89NPE5M8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-verification-before-completion\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},"01M77YFVPWANT5VE5GWBTKHPA2","using-智械工程","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-superpowers\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},"01M77YFQJAW5PX3QYSBCD3B24S","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-git-worktrees\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},"01M77YFMSTB70VX8W2QHNJWYB0","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-test-driven-development\u002FSKILL.md",[],[]]