[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BQ3GFJX9AD1EAR21FFPNK":3,"skill-same:01M75BQ3GFJX9AD1EAR21FFPNK":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75BQ3GFJX9AD1EAR21FFPNK","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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Farticle-writing\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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.\norigin: ECC\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,"origin":23,"description":7},"ECC","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Farticle-writing",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill article-writing",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill article-writing",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill article-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Farticle-writing\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]