Loading...
Loading...
Found 21 Skills
OKR trees, KPI dashboards, North Star Metric, leading/lagging indicators, and experiment design. Use when setting team goals, defining success metrics, building measurement frameworks, or designing A/B experiment guardrails.
Help a PhD student set and revise a realistic 3-month research plan that connects to their longer-term goals. Use this skill whenever the user wants to plan a new quarter, review how the last quarter went, set research goals for the next few months, think about what papers to aim for, or reorient after things drift off course. Trigger on phrases like "quarterly plan", "next 3 months", "plan my quarter", "what should I work on this quarter", "review last quarter", "my research goals", or whenever the user talks about mid-range planning (longer than a week, shorter than a year). Also trigger if the user is feeling directionless about what to focus on next.
Universal project planning for non-technical projects. Domains: business, personal, creative, academic, organizational, events. Capabilities: goal setting, milestone planning, resource allocation, timeline creation, risk assessment, progress tracking. Actions: create, plan, structure, breakdown, track projects. Keywords: project plan, roadmap, strategy, goal setting, milestones, timeline, action plan, project management, business plan, personal goals, creative project, academic planning, event planning, organizational change, OKRs, SMART goals, Gantt chart. Use when: creating project plans, setting goals/milestones, planning business initiatives, organizing events, structuring academic work, developing strategies/roadmaps.
Product Management frameworks, methodologies, and best practices library. Provides PM knowledge including prioritization (RICE, MoSCoW), goal setting (OKR, SMART), customer research (JTBD, Personas), and product strategy. Use when needing PM methodology guidance or framework application.
Define, track, and analyze product metrics with frameworks for goal setting and dashboard design. Use when setting up OKRs, building metrics dashboards, running weekly metrics reviews, identifying trends, or choosing the right metrics for a product area.
Use when a user wants to define done-criteria or a stop condition for an autonomous multi-turn agent run — setting a Claude Code /goal, a Definition of Done for a Codex or external-orchestrator loop, or turning a vague task into a verifiable completion condition an evaluator can check.
Clarify the outcome you want - a change in user behavior, not a feature shipped. Use at the start of any work to ground the session in strategic intent.
Decide what a company-run technical event is funded to accomplish, before anyone plans it - the goal mix (ecosystem goodwill, developer adoption, customer retention, sales pipeline, or a blend), who owns the budget line and which functions co-fund it, and the measurement commitment written before registration opens. Use whenever a company asks why it is running a user conference, community day, developer summit or roadshow, which goal to optimise, who should pay for it, or how to prove it worked to the people funding it, even when they only say "what is the ROI of our conference". Strategy layer only. Do NOT use to pick the event shape - use samber/dev-event-organizer-skills@business-event-formats - or to model the P&L - use samber/dev-event-organizer-skills@event-budget.
Set social media goals and KPIs — measurable targets and north-star metrics that aren't vanity numbers. Use when someone wants to "set social media goals," "define our KPIs," "what should we be aiming for," "what's our north-star metric," "OKRs for social," or to turn vague ambitions ("grow our following," "go viral") into measurable targets. Builds a cascade: business goal -> SMART objective -> North Star KPI (one per channel by its win condition) -> supporting metrics, with benchmark-set targets and action thresholds. Uses the NORTH framework. Reads brand-profile + social-strategy first. It SETS the targets; analytics-and-reporting MEASURES against them. Targets come from real benchmarks (never fabricated baselines), KPIs must be controllable and non-vanity, and guardrails prevent gaming. Distinct from analytics-and-reporting (measures) and social-strategy (the whole plan).