[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6WTZPQAEQYMTHS6CYB5J3":3,"skill-same:01M7E6WTZPQAEQYMTHS6CYB5J3":52},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7E6WTZPQAEQYMTHS6CYB5J3","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.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fecc-upstream\u002F.agents\u002Fskills\u002Farticle-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.\nlicense: MIT\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,"license":15,"description":7},"main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fecc-upstream\u002F.agents\u002Fskills\u002Farticle-writing",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill article-writing",{"tool":38,"command":39},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill article-writing",{"tool":41,"command":42},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill article-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fecc-upstream\u002F.agents\u002Fskills\u002Farticle-writing\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",273,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fecc-upstream\u002F.agents\u002Fskills\u002Farticle-writing\u002Fagents\u002Fopenai.yaml",[53,60,68,77,85,92],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\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},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]