[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FB8SYWDX751F1FNG65BZA8":3,"skill-same:01M7FB8SYWDX751F1FNG65BZA8":53},{"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},"01M7FB8SYWDX751F1FNG65BZA8","newsletter-writer",null,"Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fnewsletter-writer\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: newsletter-writer\ndescription: Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.\n---\n\n# Newsletter writer\n\nA newsletter is a standing invitation that can be withdrawn at any time. Every issue either renews\nit or spends it.\n\n## Decide the job before writing\n\nOne issue, one job: teach something, argue something, or sell something. Issues attempting all three\nachieve the first two badly and the third not at all.\n\n## Subject line and preview\n\nThey are read together and should not repeat each other — the preview extends the subject rather\nthan echoing it. Never leave the preview to default to the first line of the body, which is usually\n\"View in browser.\"\n\nWhat works: specific over clever, a claim over a topic, curiosity that the issue actually resolves.\nWhat does not: questions the reader can answer \"no\" to, manufactured urgency, and anything that\noverpromises relative to the body. Overpromising buys one open and costs the next five.\n\n## Opening\n\nThe first sentence decides whether the rest is read. Start inside the story or with the claim — no\nthroat-clearing, no \"hope you're well,\" no explaining what the newsletter is about.\n\nCut your first paragraph after drafting. It is almost always warm-up you needed to write and the\nreader does not need to read.\n\n## Structure\n\nShort paragraphs. One idea each. Enough white space that the issue looks readable before it is read\n— people decide whether to read from the shape of the thing.\n\nSignpost where the issue turns, so someone skimming still gets the argument. Most readers skim.\n\n## Voice\n\nThe thing that makes a newsletter worth opening is that it sounds like a person. Specifically:\n\n- **First-hand detail.** What you actually did, saw, or got wrong. This is the part nobody else can\n  write, and the part most drafts leave out.\n- **Opinions with a stance.** Balanced surveys of both sides are forgettable.\n- **Varied rhythm.** Uniform sentence length reads as generated, because it is what generated text\n  does.\n- **Concrete nouns and real numbers** in place of abstractions.\n\nAvoid the register tells: \"In today's fast-paced world,\" \"it's no secret that,\" \"let's dive in,\"\ntricolon everywhere, and every paragraph the same length.\n\n## Selling without spending trust\n\nEarn the ask. When an issue sells, the value comes first and the pitch is clearly marked — readers\nforgive a clear pitch and resent a disguised one.\n\nOne call to action per issue. Multiple asks split attention and reduce all of them.\n\n## Getting replies\n\nReplies are the strongest signal a newsletter is working, and they improve deliverability more than\nany technical fix.\n\nAsk one specific question, occasionally rather than every issue, and make it easy to answer in a\nsentence. \"What did I get wrong here?\" outperforms \"let me know your thoughts,\" which asks the\nreader to do the work of deciding what to say.\n\nThen reply to the replies. A newsletter where the author answers is a different product from one\nwhere they do not, and readers tell each other about the first kind.\n\n## Editing\n\nThree passes, in order: **structure** (is the order right, is anything missing), **cut** (remove\nwhat does not advance the argument), **read aloud** (anything you stumble over gets rewritten). The\nread-aloud pass catches what silent reading never does.\n\n## Repurposing\n\nOne issue contains several short-form posts, a talk track, and often a longer piece. Plan which\nbefore writing, so the sections that should stand alone are written to.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Write a subject line the opening does not pay off. It buys one open and costs the next.\n- Sell in an issue that gave nothing else. The trust spent is not recovered by the next good one.\n- Send an offer to the whole list when it applies to part of it.\n","# Newsletter writer\n\nA newsletter is a standing invitation that can be withdrawn at any time. Every issue either renews\nit or spends it.\n\n## Decide the job before writing\n\nOne issue, one job: teach something, argue something, or sell something. Issues attempting all three\nachieve the first two badly and the third not at all.\n\n## Subject line and preview\n\nThey are read together and should not repeat each other — the preview extends the subject rather\nthan echoing it. Never leave the preview to default to the first line of the body, which is usually\n\"View in browser.\"\n\nWhat works: specific over clever, a claim over a topic, curiosity that the issue actually resolves.\nWhat does not: questions the reader can answer \"no\" to, manufactured urgency, and anything that\noverpromises relative to the body. Overpromising buys one open and costs the next five.\n\n## Opening\n\nThe first sentence decides whether the rest is read. Start inside the story or with the claim — no\nthroat-clearing, no \"hope you're well,\" no explaining what the newsletter is about.\n\nCut your first paragraph after drafting. It is almost always warm-up you needed to write and the\nreader does not need to read.\n\n## Structure\n\nShort paragraphs. One idea each. Enough white space that the issue looks readable before it is read\n— people decide whether to read from the shape of the thing.\n\nSignpost where the issue turns, so someone skimming still gets the argument. Most readers skim.\n\n## Voice\n\nThe thing that makes a newsletter worth opening is that it sounds like a person. Specifically:\n\n- **First-hand detail.** What you actually did, saw, or got wrong. This is the part nobody else can\n  write, and the part most drafts leave out.\n- **Opinions with a stance.** Balanced surveys of both sides are forgettable.\n- **Varied rhythm.** Uniform sentence length reads as generated, because it is what generated text\n  does.\n- **Concrete nouns and real numbers** in place of abstractions.\n\nAvoid the register tells: \"In today's fast-paced world,\" \"it's no secret that,\" \"let's dive in,\"\ntricolon everywhere, and every paragraph the same length.\n\n## Selling without spending trust\n\nEarn the ask. When an issue sells, the value comes first and the pitch is clearly marked — readers\nforgive a clear pitch and resent a disguised one.\n\nOne call to action per issue. Multiple asks split attention and reduce all of them.\n\n## Getting replies\n\nReplies are the strongest signal a newsletter is working, and they improve deliverability more than\nany technical fix.\n\nAsk one specific question, occasionally rather than every issue, and make it easy to answer in a\nsentence. \"What did I get wrong here?\" outperforms \"let me know your thoughts,\" which asks the\nreader to do the work of deciding what to say.\n\nThen reply to the replies. A newsletter where the author answers is a different product from one\nwhere they do not, and readers tell each other about the first kind.\n\n## Editing\n\nThree passes, in order: **structure** (is the order right, is anything missing), **cut** (remove\nwhat does not advance the argument), **read aloud** (anything you stumble over gets rewritten). The\nread-aloud pass catches what silent reading never does.\n\n## Repurposing\n\nOne issue contains several short-form posts, a talk track, and often a longer piece. Plan which\nbefore writing, so the sections that should stand alone are written to.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Write a subject line the opening does not pay off. It buys one open and costs the next.\n- Sell in an issue that gave nothing else. The trust spent is not recovered by the next good one.\n- Send an offer to the whole list when it applies to part of it.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fnewsletter-writer",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill newsletter-writer",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill newsletter-writer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill newsletter-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fnewsletter-writer\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",1903,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fnewsletter-writer\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\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":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]