[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAS7C5JFHJ7NH2M89MYBYD":3,"skill-same:01M7FAS7C5JFHJ7NH2M89MYBYD":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},"01M7FAS7C5JFHJ7NH2M89MYBYD","chief-information-officer",null,"The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost center rather than an enabler.","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-information-officer\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: chief-information-officer\ndescription: The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost center rather than an enabler.\n---\n\n# Chief Information Officer\n\nThe CIO runs the technology the company works *on*. The CTO runs the technology the company\n*sells*. Confusing the two is why IT ends up owning a product roadmap it cannot resource, or why\nengineering ends up running a help desk badly.\n\n## What this department owns\n\nThe systems every employee depends on and nobody markets: identity, endpoints, network, corporate\napplications, the service desk, and the backup and restore path. Its output is measured in\navailability, time-to-resolution, and how little anyone has to think about it.\n\n- `it-operations:service-desk` — the front door, and the honest measure of whether any of this works\n- `it-operations:systems-administration` and `it-operations:network-administration` — the estate\n- `it-operations:endpoint-management` — the most exposed surface, because it leaves the building\n- `it-operations:identity-lifecycle-administration` — execution of joiner-mover-leaver\n- `it-operations:it-asset-management` — what you have, who has it, what it costs\n- `it-operations:backup-and-recovery` — the restore, tested rather than assumed\n- `it-operations:virtualization-operations` — the hypervisor layer the servers actually run on\n- `it-operations:cloud-administration` — the corporate cloud and SaaS estate, distinct from the product's\n- `it-operations:telephony-and-conferencing` — voice, rooms, and the obligations they carry\n- `it-operations:collaboration-platform-administration` — mail, chat, meetings and file sharing,\n  where most of the organization's unstructured data actually lives\n\n## The boundaries that cause arguments\n\nState them once, in writing, and the recurring turf disputes stop:\n\n- **Security sets policy; IT executes it.** `security:access-and-identity` decides what a role should\n  be entitled to; this department provisions it. `security:vulnerability-management` decides what is\n  urgent; `it-operations:systems-administration` runs the cadence.\n- **Engineering owns the product estate; IT owns the corporate estate.**\n  `technology:cloud-infrastructure` designs the environment the product runs in. Where a corporate\n  system runs in the same cloud, ownership follows who the users are, not where it is hosted.\n- **Continuity objectives are the business's; the restore is IT's.**\n  `operations:business-continuity-and-resilience` sets RTO and RPO with the process owners; this\n  department has to deliver against them and should say plainly when it cannot.\n\n## Build, buy, or outsource\n\nDefault to buy for anything that is not a differentiator. Building an internal tool that a mature\nproduct already solves is a decision to maintain it forever, staffed by people who would rather be\ndoing something else.\n\nOutsource where the work is commoditized and the failure is recoverable — first-line support out of\nhours, hardware logistics. Keep in-house what needs institutional context or carries irreversible\nrisk: identity, data, and anything where a bad decision is discovered a year later.\n\n## The recovery you have never tested is a plan, not a capability\n\nBackups that have never been restored, failovers never exercised, and runbooks never followed under\npressure are all assertions. The characteristic discovery during a real incident is that one of them\nwas wrong in a way nobody could have known without trying.\n\nTest on a schedule, with the person who would actually do it rather than the one who designed it,\nand time the restore — recovery time is the number the business will ask for, and the only honest\nanswer comes from having done it. The same logic applies to the communication plan: its first real\nexercise should not be its first real incident.\n\n## Spend, and the cost-center trap\n\nAttribute IT cost to the functions consuming it rather than reporting one aggregate. An\nundifferentiated IT budget invites across-the-board cuts, because nobody can see what any of it buys.\n\nThe trap is real: a department judged only on cost is asked only to be cheaper, and the first\ncasualties are refresh cycles and patching, which surface as incidents two years later with no\nvisible cause. Report service outcomes alongside cost, and be specific about what a proposed cut\nremoves.\n\nTrack the split between running the estate and changing it, and defend it as a target rather than\nletting it be the residue after everything else. An estate consuming everything on keeping the\nlights on has no capacity to improve, and next year it will consume more — the ratio decays on its\nown unless someone holds it.\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- Accept a continuity objective you have not demonstrated you can meet.\n- Let identity policy and identity execution sit with the same reviewer.\n- Build an internal tool for a solved commodity problem.\n- Report IT cost without reporting what it delivered.\n- Count an untested restore as a recovery capability.\n","# Chief Information Officer\n\nThe CIO runs the technology the company works *on*. The CTO runs the technology the company\n*sells*. Confusing the two is why IT ends up owning a product roadmap it cannot resource, or why\nengineering ends up running a help desk badly.\n\n## What this department owns\n\nThe systems every employee depends on and nobody markets: identity, endpoints, network, corporate\napplications, the service desk, and the backup and restore path. Its output is measured in\navailability, time-to-resolution, and how little anyone has to think about it.\n\n- `it-operations:service-desk` — the front door, and the honest measure of whether any of this works\n- `it-operations:systems-administration` and `it-operations:network-administration` — the estate\n- `it-operations:endpoint-management` — the most exposed surface, because it leaves the building\n- `it-operations:identity-lifecycle-administration` — execution of joiner-mover-leaver\n- `it-operations:it-asset-management` — what you have, who has it, what it costs\n- `it-operations:backup-and-recovery` — the restore, tested rather than assumed\n- `it-operations:virtualization-operations` — the hypervisor layer the servers actually run on\n- `it-operations:cloud-administration` — the corporate cloud and SaaS estate, distinct from the product's\n- `it-operations:telephony-and-conferencing` — voice, rooms, and the obligations they carry\n- `it-operations:collaboration-platform-administration` — mail, chat, meetings and file sharing,\n  where most of the organization's unstructured data actually lives\n\n## The boundaries that cause arguments\n\nState them once, in writing, and the recurring turf disputes stop:\n\n- **Security sets policy; IT executes it.** `security:access-and-identity` decides what a role should\n  be entitled to; this department provisions it. `security:vulnerability-management` decides what is\n  urgent; `it-operations:systems-administration` runs the cadence.\n- **Engineering owns the product estate; IT owns the corporate estate.**\n  `technology:cloud-infrastructure` designs the environment the product runs in. Where a corporate\n  system runs in the same cloud, ownership follows who the users are, not where it is hosted.\n- **Continuity objectives are the business's; the restore is IT's.**\n  `operations:business-continuity-and-resilience` sets RTO and RPO with the process owners; this\n  department has to deliver against them and should say plainly when it cannot.\n\n## Build, buy, or outsource\n\nDefault to buy for anything that is not a differentiator. Building an internal tool that a mature\nproduct already solves is a decision to maintain it forever, staffed by people who would rather be\ndoing something else.\n\nOutsource where the work is commoditized and the failure is recoverable — first-line support out of\nhours, hardware logistics. Keep in-house what needs institutional context or carries irreversible\nrisk: identity, data, and anything where a bad decision is discovered a year later.\n\n## The recovery you have never tested is a plan, not a capability\n\nBackups that have never been restored, failovers never exercised, and runbooks never followed under\npressure are all assertions. The characteristic discovery during a real incident is that one of them\nwas wrong in a way nobody could have known without trying.\n\nTest on a schedule, with the person who would actually do it rather than the one who designed it,\nand time the restore — recovery time is the number the business will ask for, and the only honest\nanswer comes from having done it. The same logic applies to the communication plan: its first real\nexercise should not be its first real incident.\n\n## Spend, and the cost-center trap\n\nAttribute IT cost to the functions consuming it rather than reporting one aggregate. An\nundifferentiated IT budget invites across-the-board cuts, because nobody can see what any of it buys.\n\nThe trap is real: a department judged only on cost is asked only to be cheaper, and the first\ncasualties are refresh cycles and patching, which surface as incidents two years later with no\nvisible cause. Report service outcomes alongside cost, and be specific about what a proposed cut\nremoves.\n\nTrack the split between running the estate and changing it, and defend it as a target rather than\nletting it be the residue after everything else. An estate consuming everything on keeping the\nlights on has no capacity to improve, and next year it will consume more — the ratio decays on its\nown unless someone holds it.\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- Accept a continuity objective you have not demonstrated you can meet.\n- Let identity policy and identity execution sit with the same reviewer.\n- Build an internal tool for a solved commodity problem.\n- Report IT cost without reporting what it delivered.\n- Count an untested restore as a recovery capability.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fchief-information-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-information-officer",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill chief-information-officer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill chief-information-officer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fchief-information-officer\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",945,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fchief-information-officer\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",[],[]]