[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAMJEYC0AX4T1TP6YDD5KA":3,"skill-same:01M7FAMJEYC0AX4T1TP6YDD5KA":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},"01M7FAMJEYC0AX4T1TP6YDD5KA","access-and-identity",null,"Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.","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\u002Faccess-and-identity\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: access-and-identity\ndescription: Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.\n---\n\n# Access and identity\n\nAccess accumulates. People change roles and keep the old permissions, services get broad credentials\nbecause narrow ones were inconvenient, and contractors' accounts outlive their contracts. Left alone,\nentitlement always grows and never shrinks.\n\n## Principles that actually hold\n\n- **Least privilege, and it must be practical.** A model so restrictive that people share accounts\n  to get work done is worse than a looser one they follow.\n- **Role-based, not person-based.** Grants attached to individuals are ungovernable at any scale.\n- **Time-bound elevation over standing privilege.** Nobody should hold administrative access\n  continuously because they occasionally need it. Elevation on request, with a reason, expiring\n  automatically.\n- **Separate duties where the consequence is severe.** The person who requests a payment does not\n  approve it; the person who writes the deploy does not solely authorize the production change.\n\n## Authentication\n\nSingle sign-on wherever possible — the value is not convenience, it is that offboarding becomes one\naction rather than forty. Every system outside SSO is a system someone will still have access to\nafter they leave.\n\nMulti-factor everywhere it is available, and phishing-resistant factors for administrative access.\nSMS is better than nothing and is the weakest option worth deploying.\n\n## Joiner, mover, leaver\n\n**Mover is the one everyone gets wrong.** Joining and leaving are events with a process; changing\nrole usually adds permissions and removes none, which is how a long-tenured employee ends up with\naccess to everything.\n\nMake role change a revoke-and-regrant rather than an addition. It is the single highest-value change\nmost organizations can make to their access posture.\n\nOffboarding needs to be same-day, cover everything including systems outside SSO, and be verified\nrather than assumed. Keep a list of what exists to be revoked — the fastest way to find the shadow\nsystems is to try to offboard someone thoroughly.\n\n## Service and machine credentials\n\nUsually more numerous and less governed than human ones. Each needs a named human owner, a scope\nlimited to its actual use, a rotation path, and an expiry.\n\nPrefer short-lived, automatically issued credentials over long-lived keys. A key that never expires\nwill eventually appear in a repository, a log, or a support ticket.\n\n## Access reviews\n\nPeriodic, by system, with the reviewer being the person accountable for the data rather than IT.\nReviewers who cannot say why someone needs access should remove it — the burden belongs on\nretention, not removal.\n\nReview dormant accounts as a separate pass. An account nobody has used in six months is either\nunnecessary or belongs to someone who left.\n\n## Diagnosing sprawl\n\nLook for: permissions granted to individuals rather than roles, roles nobody can define, standing\nadministrative access, accounts whose owner has left, service credentials with no owner, and systems\noutside SSO. Each is a specific fix, and the list is nearly always the same list.\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## Tooling\n\nIdentity providers: Okta, Microsoft Entra ID, Google Workspace, JumpCloud, and similar.\n\nPrivileged access and secrets: CyberArk, HashiCorp Vault, 1Password, Doppler, and similar.\n\nAccess reviews and provisioning: Okta Identity Governance, Entra ID Governance, Lumos,\nConductorOne, and similar. Worth buying at the point a manual quarterly review stops\nfinishing rather than the point it gets tedious.\n\n## Never\n\n- Grant standing access where time-bound access would do the same job.\n- Leave an account active while an offboarding ticket works its way through. Cut access first, reconcile after.\n- Share a credential between people. If two people can use it, no log tells you which one did.\n- Approve your own access request, or review a group you belong to.\n","# Access and identity\n\nAccess accumulates. People change roles and keep the old permissions, services get broad credentials\nbecause narrow ones were inconvenient, and contractors' accounts outlive their contracts. Left alone,\nentitlement always grows and never shrinks.\n\n## Principles that actually hold\n\n- **Least privilege, and it must be practical.** A model so restrictive that people share accounts\n  to get work done is worse than a looser one they follow.\n- **Role-based, not person-based.** Grants attached to individuals are ungovernable at any scale.\n- **Time-bound elevation over standing privilege.** Nobody should hold administrative access\n  continuously because they occasionally need it. Elevation on request, with a reason, expiring\n  automatically.\n- **Separate duties where the consequence is severe.** The person who requests a payment does not\n  approve it; the person who writes the deploy does not solely authorize the production change.\n\n## Authentication\n\nSingle sign-on wherever possible — the value is not convenience, it is that offboarding becomes one\naction rather than forty. Every system outside SSO is a system someone will still have access to\nafter they leave.\n\nMulti-factor everywhere it is available, and phishing-resistant factors for administrative access.\nSMS is better than nothing and is the weakest option worth deploying.\n\n## Joiner, mover, leaver\n\n**Mover is the one everyone gets wrong.** Joining and leaving are events with a process; changing\nrole usually adds permissions and removes none, which is how a long-tenured employee ends up with\naccess to everything.\n\nMake role change a revoke-and-regrant rather than an addition. It is the single highest-value change\nmost organizations can make to their access posture.\n\nOffboarding needs to be same-day, cover everything including systems outside SSO, and be verified\nrather than assumed. Keep a list of what exists to be revoked — the fastest way to find the shadow\nsystems is to try to offboard someone thoroughly.\n\n## Service and machine credentials\n\nUsually more numerous and less governed than human ones. Each needs a named human owner, a scope\nlimited to its actual use, a rotation path, and an expiry.\n\nPrefer short-lived, automatically issued credentials over long-lived keys. A key that never expires\nwill eventually appear in a repository, a log, or a support ticket.\n\n## Access reviews\n\nPeriodic, by system, with the reviewer being the person accountable for the data rather than IT.\nReviewers who cannot say why someone needs access should remove it — the burden belongs on\nretention, not removal.\n\nReview dormant accounts as a separate pass. An account nobody has used in six months is either\nunnecessary or belongs to someone who left.\n\n## Diagnosing sprawl\n\nLook for: permissions granted to individuals rather than roles, roles nobody can define, standing\nadministrative access, accounts whose owner has left, service credentials with no owner, and systems\noutside SSO. Each is a specific fix, and the list is nearly always the same list.\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## Tooling\n\nIdentity providers: Okta, Microsoft Entra ID, Google Workspace, JumpCloud, and similar.\n\nPrivileged access and secrets: CyberArk, HashiCorp Vault, 1Password, Doppler, and similar.\n\nAccess reviews and provisioning: Okta Identity Governance, Entra ID Governance, Lumos,\nConductorOne, and similar. Worth buying at the point a manual quarterly review stops\nfinishing rather than the point it gets tedious.\n\n## Never\n\n- Grant standing access where time-bound access would do the same job.\n- Leave an account active while an offboarding ticket works its way through. Cut access first, reconcile after.\n- Share a credential between people. If two people can use it, no log tells you which one did.\n- Approve your own access request, or review a group you belong to.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Faccess-and-identity",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 access-and-identity",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill access-and-identity",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill access-and-identity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Faccess-and-identity\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",1323,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Faccess-and-identity\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",[],[]]