[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"org-bitwarden":3,"repo-skills-v-0-3-0":62},{"org":4,"repos":46},{"slug":5,"name":6,"logoUrl":7,"githubOrg":5,"website":8,"skillCount":9,"repoCount":10,"topRepos":11,"topTags":14,"lastUpdatedAt":45},"bitwarden","Bitwarden","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fbitwarden.png","https:\u002F\u002Fbitwarden.com",5,1,[12],{"name":13,"skillCount":9},"bitwarden\u002Fai-plugins",[15,18,21,24,27,30,33,36,39,42],{"slug":16,"name":17},"engineering","Engineering",{"slug":19,"name":20},"operations","Operations",{"slug":22,"name":23},"project-management","Project Management",{"slug":25,"name":26},"adr","ADR",{"slug":28,"name":29},"agile","Agile",{"slug":31,"name":32},"architecture","Architecture",{"slug":34,"name":35},"code-review","Code Review",{"slug":37,"name":38},"documentation","Documentation",{"slug":40,"name":41},"git","Git",{"slug":43,"name":44},"productivity","Productivity","2026-05-08T05:03:15.197555",[47],{"name":48,"fullName":13,"repoUrl":49,"skillCount":9,"stars":50,"forks":51,"description":52,"topics":53,"topTags":54,"topTagCount":61,"lastUpdatedAt":45},"ai-plugins","https:\u002F\u002Fgithub.com\u002Fbitwarden\u002Fai-plugins",127,14,"AI plugin marketplace.",[],[55,56,57,58,59,60],{"slug":16,"name":17},{"slug":19,"name":20},{"slug":22,"name":23},{"slug":25,"name":26},{"slug":28,"name":29},{"slug":31,"name":32},15,{"items":63,"total":9},[64,80,91,101,116],{"slug":65,"name":65,"fn":66,"description":67,"org":68,"tags":69,"stars":50,"repoUrl":49,"updatedAt":79},"architecting-solutions","architect and review system designs","Framework for architecting solutions inside a team's domain while staying coherent with Bitwarden's holistic architecture. Covers security mindset, blast radius assessment, architectural judgment, Bitwarden-specific constraints, working with the architecture group, and working with initiative shepherds. Use when planning a solution, reviewing architecture within a team's scope, assessing blast radius, evaluating trade-offs, or deciding whether a choice needs architecture-group input.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[70,72,73,76],{"name":26,"slug":25,"type":71},"tag",{"name":32,"slug":31,"type":71},{"name":74,"slug":75,"type":71},"Risk Assessment","risk-assessment",{"name":77,"slug":78,"type":71},"System Design","system-design","2026-04-29T05:36:35.460171",{"slug":81,"name":81,"fn":82,"description":83,"org":84,"tags":85,"stars":50,"repoUrl":49,"updatedAt":90},"committing-changes","manage Git commits and conventions","Git commit conventions and workflow for Bitwarden repositories. Use when committing code, writing commit messages, or preparing changes for commit. Triggered by \"commit\", \"git commit\", \"commit message\", \"prepare commit\", \"stage changes\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[86,87],{"name":41,"slug":40,"type":71},{"name":88,"slug":89,"type":71},"Workflow Automation","workflow-automation","2026-04-29T05:36:32.816824",{"slug":92,"name":92,"fn":93,"description":94,"org":95,"tags":96,"stars":50,"repoUrl":49,"updatedAt":45},"navigating-the-initiative-funnel","navigate the Bitwarden initiative funnel","Phase-by-phase guidance for participating in Bitwarden's Software Initiative Funnel. Covers ownership boundaries between shepherd and tech lead at each phase, how to run an epic breakdown after handoff, sizing and estimation, cross-team dependency tracking, and the escalation paths that protect team autonomy. Use when a team is about to receive an initiative epic, when participating in an Architectural Assessment or PoC, when preparing a team breakdown, or when surfacing concerns back to the shepherd or engineering leadership.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[97,98,99,100],{"name":29,"slug":28,"type":71},{"name":17,"slug":16,"type":71},{"name":20,"slug":19,"type":71},{"name":23,"slug":22,"type":71},{"slug":102,"name":102,"fn":103,"description":104,"org":105,"tags":106,"stars":50,"repoUrl":49,"updatedAt":115},"perform-preflight","run quality gate preflight checklists","Quality gate checklist to run before committing or creating a PR. Use when finishing implementation, checking work quality, or preparing to commit. Triggered by \"preflight\", \"self review\", \"ready to commit\", \"check my work\", \"quality gate\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[107,108,109,112],{"name":35,"slug":34,"type":71},{"name":44,"slug":43,"type":71},{"name":110,"slug":111,"type":71},"QA","qa",{"name":113,"slug":114,"type":71},"Testing","testing","2026-04-29T05:36:31.512969",{"slug":117,"name":117,"fn":118,"description":119,"org":120,"tags":121,"stars":50,"repoUrl":49,"updatedAt":126},"running-work-transitions","run ownership transitions for software work","Six-phase playbook for running ownership transitions in either direction — receiving work from another team (initiative handoffs from shepherds, frameworks from Platform, operational responsibilities from SRE), or originating a transition (handing off a built framework, transitioning a shepherded initiative, or moving operational responsibilities). Applies Bitwarden's Work Transition Playbook from whichever side a team is on. Use when a team is about to take on or hand off transferred work, when preparing materials or sessions, when the support period is underway, or when running a pulse check or retrospective on a handoff.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[122,123,124,125],{"name":38,"slug":37,"type":71},{"name":17,"slug":16,"type":71},{"name":20,"slug":19,"type":71},{"name":23,"slug":22,"type":71},"2026-05-08T05:03:13.935149"]