Claude Skills by shwetank

Use to set up or work with a SHARED, git-backed team workspace for artifacts a team co-owns — team charters, strategy docs, decision records — kept strictly separate from your private reflections, which never leave your machine. Trigger phrases include "share our team charter with the team", "set up a shared bettersense workspace", "put our strategy doc in the team repo", "how do teams use bettersense together". Establishes `$BETTERSENSE_TEAM_HOME` (a separate git repo), enforces a hard wall ...

Use when a senior IC (staff/principal engineer, architect, tech lead) needs to write a technical strategy or direction doc — where a system or domain should go over 12–24 months and why. Trigger phrases include "write a tech strategy for [domain]", "I need a technical direction doc", "our platform needs a north star doc", "help me write the tech vision for [area]". The staff+ artifact: turning engineering judgment into direction others can follow without you in the room. Distinct from strateg...

Use when the user's work is better than their visibility — building deliberate, non-gross sponsor awareness so the right people know what they do before the promo/calibration moment. Trigger phrases include "nobody knows what I do", "how do I get more visibility", "I need a sponsor", "my work speaks for itself but nobody's listening", "I was passed over because people don't know me", "how do I self-promote without being obnoxious". The ongoing drip between formal moments: who needs to know, w...

Use for the user's recurring weekly review ritual — one guided session (~15 minutes) that wraps the whole bettersense maintenance loop. Trigger phrases include "run my weekly review", "Friday review", "weekly check-in", "start my week", "Monday planning", "/bettersense:weekly", or any "it's been a week, what should I catch up on" moment. Runs four time-boxed segments — wins capture, most-overdue stakeholder reflection, cross-cutting patterns, pulse glance — by composing wins-due, stakeholder-...