[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAR4XXGKP2TJNKGDEDEC5S":3,"skill-same:01M7FAR4XXGKP2TJNKGDEDEC5S":47},{"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},"01M7FAR4XXGKP2TJNKGDEDEC5S","chief-content-officer",null,"Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit an existing library for what to update, consolidate, or retire. For deciding what territory to own and why, use `content-strategy` first.","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\u002Fchief-content-officer\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: chief-content-officer\ndescription: Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit an existing library for what to update, consolidate, or retire. For deciding what territory to own and why, use `content-strategy` first.\n---\n\n# Chief content officer\n\n`content-strategy` decides what to make and why. This runs the machine that makes it.\n\n## The pipeline\n\nContent programs fail on throughput, not ideas. Define the stages and who owns each: idea → brief →\ndraft → edit → assets → publish → distribute → measure.\n\nThe two stages that jam are **brief** and **distribution**. A piece that reaches a writer without a\nbrief gets rewritten twice. A piece that publishes without a distribution plan reaches whoever\nhappens to be looking.\n\nWork in progress is the enemy. Fewer pieces moving through completely beats many pieces half-done —\na program with fifteen drafts and two publishes has a queue problem, not a capacity problem.\n\n## Briefs\n\nEvery piece gets one before drafting, stating: the job (reach, trust, conversion, or retention), the\naudience, the single argument, the evidence available, the format and length, and what success\nlooks like. Briefs are cheap and prevent the most expensive failure, which is a finished piece\npointed at nothing.\n\n## Calendar\n\nBuild against capacity at your worst week, not your best. Plan a mix by job rather than by topic —\na calendar of only reach content builds an audience that never converts.\n\nLeave deliberate gaps. A calendar with no slack cannot respond to anything timely, and timely is\nwhere outsized results come from.\n\n## The repurposing engine\n\nPlan derivatives at brief time, not after publishing. One substantial piece should be conceived as:\nthe long-form source, several short-form extracts, one visual asset, one email, and one talk track.\nSegments intended to stand alone get written to stand alone.\n\nExtracting derivatives from a piece not built for it produces fragments that need context they do\nnot have.\n\n## Competitive content intelligence\n\nLook at what competitors publish, what actually performs for them, and — most usefully — what they\nconsistently avoid. Gaps in a competitor's coverage are either an opportunity or a lesson someone\nalready learned. Work out which before committing.\n\nTrack their publishing cadence and format mix. A competitor who abandoned a format probably found\nit did not work.\n\n## Ranking ideas\n\nScore on reach potential, strategic fit, evidence available, and effort. Force a stack rank rather\nthan tiers. Then check the top of the list against the format budget — if everything ranked highly\nis reach content, the ranking is measuring popularity rather than value.\n\n## Expanding a chosen idea\n\nOnce an idea is picked, expand it before drafting. An idea is a title; a piece needs an argument.\n\nWork out: the claim, the two or three things that must be established for the claim to hold, the\nevidence available for each, the strongest counter-argument, and what the reader should do\ndifferently afterward.\n\nIf the counter-argument cannot be answered, that is the more interesting piece — write that one\ninstead.\n\nOnly then choose the format. Choosing format first is how a topic that wanted six hundred words\nbecomes a video series.\n\n## Auditing an existing library\n\nInventory everything with its traffic, conversions, and last-updated date, then sort into four\npiles: **update** (performing, stale), **consolidate** (several thin pieces on one topic),\n**promote** (good, undistributed — usually the largest and most neglected pile), and **retire**\n(no traffic, no links, no strategic value).\n\nMost libraries have more value in the promote pile than in anything unwritten.\n\n## Never\n\n- Start production before the brief names the argument. An idea is a title; a piece needs a claim.\n- Fill the calendar to capacity. A pipeline with no slack cannot absorb the one piece worth dropping everything for.\n- Choose the format before the argument. That is how a topic that wanted six hundred words becomes a video series.\n- Retire a piece that has inbound links without redirecting it.\n","# Chief content officer\n\n`content-strategy` decides what to make and why. This runs the machine that makes it.\n\n## The pipeline\n\nContent programs fail on throughput, not ideas. Define the stages and who owns each: idea → brief →\ndraft → edit → assets → publish → distribute → measure.\n\nThe two stages that jam are **brief** and **distribution**. A piece that reaches a writer without a\nbrief gets rewritten twice. A piece that publishes without a distribution plan reaches whoever\nhappens to be looking.\n\nWork in progress is the enemy. Fewer pieces moving through completely beats many pieces half-done —\na program with fifteen drafts and two publishes has a queue problem, not a capacity problem.\n\n## Briefs\n\nEvery piece gets one before drafting, stating: the job (reach, trust, conversion, or retention), the\naudience, the single argument, the evidence available, the format and length, and what success\nlooks like. Briefs are cheap and prevent the most expensive failure, which is a finished piece\npointed at nothing.\n\n## Calendar\n\nBuild against capacity at your worst week, not your best. Plan a mix by job rather than by topic —\na calendar of only reach content builds an audience that never converts.\n\nLeave deliberate gaps. A calendar with no slack cannot respond to anything timely, and timely is\nwhere outsized results come from.\n\n## The repurposing engine\n\nPlan derivatives at brief time, not after publishing. One substantial piece should be conceived as:\nthe long-form source, several short-form extracts, one visual asset, one email, and one talk track.\nSegments intended to stand alone get written to stand alone.\n\nExtracting derivatives from a piece not built for it produces fragments that need context they do\nnot have.\n\n## Competitive content intelligence\n\nLook at what competitors publish, what actually performs for them, and — most usefully — what they\nconsistently avoid. Gaps in a competitor's coverage are either an opportunity or a lesson someone\nalready learned. Work out which before committing.\n\nTrack their publishing cadence and format mix. A competitor who abandoned a format probably found\nit did not work.\n\n## Ranking ideas\n\nScore on reach potential, strategic fit, evidence available, and effort. Force a stack rank rather\nthan tiers. Then check the top of the list against the format budget — if everything ranked highly\nis reach content, the ranking is measuring popularity rather than value.\n\n## Expanding a chosen idea\n\nOnce an idea is picked, expand it before drafting. An idea is a title; a piece needs an argument.\n\nWork out: the claim, the two or three things that must be established for the claim to hold, the\nevidence available for each, the strongest counter-argument, and what the reader should do\ndifferently afterward.\n\nIf the counter-argument cannot be answered, that is the more interesting piece — write that one\ninstead.\n\nOnly then choose the format. Choosing format first is how a topic that wanted six hundred words\nbecomes a video series.\n\n## Auditing an existing library\n\nInventory everything with its traffic, conversions, and last-updated date, then sort into four\npiles: **update** (performing, stale), **consolidate** (several thin pieces on one topic),\n**promote** (good, undistributed — usually the largest and most neglected pile), and **retire**\n(no traffic, no links, no strategic value).\n\nMost libraries have more value in the promote pile than in anything unwritten.\n\n## Never\n\n- Start production before the brief names the argument. An idea is a title; a piece needs a claim.\n- Fill the calendar to capacity. A pipeline with no slack cannot absorb the one piece worth dropping everything for.\n- Choose the format before the argument. That is how a topic that wanted six hundred words becomes a video series.\n- Retire a piece that has inbound links without redirecting it.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fchief-content-officer",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 chief-content-officer",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill chief-content-officer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill chief-content-officer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fchief-content-officer\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":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":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]