Explore skills
Showing 14011–14040 of 37595 skills
Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring multiplier that turns a weekly 30-minutes into a real annual number, and the cost-vs-outcome read that decides what the price buys. Use when asked what does this meeting cost, price our meeting culture, is this recurring meeting worth it, or make the case for fewer attendees. Produces the cost computation with stated assumptions, the recurring annualization, the cost-per-outcome read, and the reduction levers ranked.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexArrive at a meeting armed in fifteen minutes — the prep pack: what this meeting decides, your position with its reasons, the other attendees' likely stances, the questions to ask, and the outcome you're steering toward. Use when asked prep me for this meeting, what should I know before this call, I have 15 minutes before a big meeting, or help me not wing it. Produces the one-page prep pack with position, stances, questions, and the walk-away-with list.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexSet the shared-space norms that end the small daily frictions — meeting room booking discipline (the ghost-booking cure), hybrid-call room behavior, the shared kitchen/space contracts, and the enforcement that works without a hall monitor. Use when asked set office space norms, rooms are always booked but empty, hybrid meetings are terrible for remote people, or write the office etiquette guide. Produces the norms card by space type, the ghost-booking fix, the hybrid-room checklist, and the no-hall-monitor enforcement design.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexMove a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only afterlife. Use when asked we're moving from Dropbox to Drive, migrate our files to SharePoint, plan the file migration day, or how do we switch platforms safely. Produces the migration runbook: freeze window, copy-and-verify steps, permissions mapping, the cutover comms, and the rollback line.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexTurn a pile of newsletters and subscriptions into one skimmable brief — the items that matter to YOUR interests extracted with sources, the noise dropped with a count, on a cadence that replaces daily trickle-reading. Use when asked digest my newsletters, summarize what my subscriptions said this week, what did I miss that I actually care about, or make my reading pile useful. Produces the interest-filtered brief with per-item sources, the dropped-with-reasons ledger, and the cadence that makes trickle-reading obsolete.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexReplace ad-hoc interruptions with office hours that actually get used — the slot design (cadence, length, format), the routing rules that tell people what goes there vs. what shouldn't wait, and the empty-hours and overflow failure modes handled in advance. Use when asked set up office hours, I'm interrupted constantly but want to stay accessible, my office hours sit empty, or design expert time for the team. Produces the slot design, the routing card, the facilitation format, and the tuning rules.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexRun an office move or reconfiguration without losing a week of work — the dependency-ordered plan (internet lead times rule everything), the workstream owners, the comms that keep the team functional through the chaos, and the day-one-that-works checklist. Use when asked plan our office move, we're moving floors/buildings in six weeks, who owns what in the move, or make day one at the new office not a disaster. Produces the workstream map with owners, the dependency timeline, the team comms plan, and the day-one readiness gate.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexPlan a team offsite that earns its cost — the purpose split (connection vs. decisions vs. planning, weighted on purpose), the agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different from before. Use when asked plan our team offsite, design two days for the team, make this offsite not a waste, or what do we actually do at the offsite. Produces the purpose weighting, the day designs, the logistics checklist, and the commitments-capture that survives re-entry.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexDesign the buddy system that makes new-hire onboarding human — the buddy's actual job (context and safety, not training), the 30-day touchpoint plan, the ask-me-anything contract, and the buddy selection that avoids the two classic miscasts. Use when asked set up an onboarding buddy program, I'm buddying the new hire what do I do, our onboarding is docs with no humans, or the new person is drowning quietly. Produces the buddy role definition, the touchpoint schedule, the first-week script, and the escalation line.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexDesign an out-of-office that actually protects the time off — the auto-reply that routes instead of apologizes, the coverage map behind it, and the pre-departure handoff that prevents the beach laptop. Use when asked write my out of office message, going on vacation what do I set up, cover my work while I'm out, or I always come back to chaos. Produces the OOO message with routing, the coverage assignments confirmed, the pre-departure checklist, and the re-entry buffer plan.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexOutline documents before drafting them — the argument skeleton that gets alignment cheaply, the one-line-per-section discipline, and the review-the-outline step that saves rewriting the prose. Use when asked help me start this document, outline before I write, why do my docs get rewritten from scratch in review, or get sign-off before drafting. Produces the outline with each section's claim (not topic), the reader-and-decision header, the outline review step, and the expansion rules.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexCap your work-in-progress so things finish — the personal WIP limit (3 active outcomes, defended), the finish-before-start rule with its exceptions named, the parking lot for the overflow, and the throughput evidence that converts the skeptic. Use when asked I have twelve things half-done, why does nothing ever finish, set a WIP limit for my work, or I start everything and complete nothing. Produces the active-list cap, the parking protocol, the start-gate, and the two-week throughput experiment.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexRescue a photo library drowning in duplicates, screenshots, and 40,000 unsorted items — the triage order that shrinks first (screenshots, bursts, dupes), the album-vs-search philosophy that ends over-organizing, and the backup rule that comes before any deleting. Use when asked organize my photo library, 40k photos help, delete duplicate photos safely, or set up a photo system that lasts. Produces the backup-first step, the shrink passes in order, the light organizing layer, and the monthly habit.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexKnow which talk you're giving — the pitch (drive one decision) vs. the teach (build understanding) — because mixing their structures fails both, and most bad presentations are one wearing the other's clothes. Use when asked is this a pitch or a training, my informative deck didn't land the ask, my pitch felt like a lecture, or structure this talk for the right job. Produces the mode diagnosis, the structural implications, the mixed-mandate split, and the mode-check on an existing deck.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexPlan pivot-table analysis that answers the actual question — the question-to-layout mapping (rows, values, filters chosen on purpose), the data-shape check that pivots require, and the drill-down path from summary to so-what. Use when asked analyze this data with a pivot, what's driving the total, break this down by category and month, or my pivot shows nonsense. Produces the question decomposition, the pivot layout(s) with reasons, the data-shape fixes needed first, and the reading guide.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexRewrite jargon-dense text into plain language without losing precision — the translation pass that keeps every fact and qualifier, the jargon triage (terms to replace, terms to keep-and-define), and the reading-level honesty for the actual audience. Use when asked make this readable, translate this for non-experts, de-jargon this announcement, or rewrite this so my parents/customers/new hires understand it. Produces the rewrite with a fidelity check, the jargon ledger, and the kept-terms glossary line.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexDraft an internal policy people can actually follow — the rule stated plainly with its reason, the bright lines separated from the judgment zones, the edge cases resolved by principle, and the enforcement reality stated honestly. Use when asked write our expense/remote-work/AI-use/security policy, turn this incident into a policy, our policy doc is unreadable, or people keep asking what's allowed. Produces the policy with rules-plus-reasons, the bright-line/judgment split, the worked edge cases, and the honest enforcement section.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexWrite presenter notes that actually help mid-talk — cue-grain phrases instead of scripts, the transitions and numbers that deserve verbatim capture, the timing marks that keep the talk on schedule, and the Q&A crib built in. Use when asked write my speaker notes, I either script everything or wing it, what goes in the notes pane, or I keep running over time. Produces the notes at cue grain, the verbatim-worthy lines, the timing marks, and the Q&A crib.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexStructure an internal proposal that gets a decision — the problem-cost-options-recommendation-ask spine, the objection pre-handling that shortens the meeting, and the reversibility framing that makes yes easier. Use when asked write a proposal for the new tool or process or hire, how do I pitch this internally, structure my case for the change, or my proposals keep dying in review. Produces the proposal skeleton filled from the actual case, the objections table, the decision-sized ask, and the one-page discipline.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexWrite the purchase request that gets approved — the cost-of-not-buying framing, the ROI math at the approver's altitude, the alternatives-considered section that preempts the obvious pushback, and the right-sized ask for the approval tier. Use when asked justify this tool/hire/equipment purchase, write the budget request, my requests keep getting deferred, or make the business case for this spend. Produces the justification memo: the problem priced, the ROI shown, alternatives dispatched, and the ask sized to its approval path.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexPrune your own recurring-meeting load — the personal calendar audit (your role in each, honestly), the four exit moves (leave, delegate, downgrade to notes, halve), and the graceful exit scripts that don't burn standing. Use when asked get me out of some of these meetings, my calendar is 80% recurring, which meetings can I stop attending, or leave a meeting politely. Produces the personal audit with role verdicts, the exit move per meeting, the scripts, and the calendar-shape after.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexDraft email replies that match the sender's register — formality, length, directness, and emoji-tolerance read from their message, so the reply lands as native instead of off-key. Use when asked reply to this email, draft a response that doesn't sound stiff, match their tone, or answer this without sounding like a robot. Produces the tone read of the incoming message, the reply drafted in that register, and the adjustment knobs.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexSet up a research repository the team actually reuses — the atomic-insight format (finding + evidence + source + date), the tagging that makes old research findable by new questions, and the check-the-repo-first norm that stops re-researching. Use when asked set up a research repository, we keep re-learning the same things, where do our user insights live, or make past research findable. Produces the repo structure, the insight-entry format, the intake funnel from studies, and the reuse norms.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexResolve a document's forty review comments systematically — triage by type (accept, push back, conflict, out-of-scope), batch the mechanical fixes, draft the disagreement replies, and reconcile reviewers who contradict each other. Use when asked work through these review comments, two reviewers want opposite things, close out the feedback on this doc, or which comments do I actually have to take. Produces the comment triage, the batched fixes, the push-back replies, the conflict reconciliations, and the closure sweep.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexDecline requests without damaging relationships or your standing — the fast-clear-warm formula, the alternative-attached no, the no-to-the-boss version (tradeoffs, not refusal), and the scripts for the asks that recur. Use when asked how do I say no to this, decline this project politely, I say yes to everything and drown, or push back on my manager's request. Produces the decline scripts by relationship, the tradeoff framing for upward nos, the alternative menu, and the yes-audit that finds what to stop.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexClean up a shared drive nobody owns — the ownership-first move, the top-down audit that finds the 80% (stale projects, duplicates, ex-employee folders), the archive-don't-delete discipline for shared property, and the norms that prevent regrowth. Use when asked our shared drive is a disaster, clean up the team drive, who owns all these folders, or people are scared to delete anything. Produces the audit map, the archive plan with the fear-killing rule, the ownership assignments, and the going-forward norms.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexEnd the workday on purpose — the ten-minute shutdown that closes open loops, stages tomorrow's start, and gives the brain permission to actually stop (the incomplete-task hum has an off switch, and it's written). Use when asked I can't stop thinking about work at night, build an end-of-day routine, my evenings are ruined by open loops, or how do I stop checking one more time. Produces the shutdown checklist, the tomorrow-staging step, the closing phrase, and the after-hours boundary rules.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexFix slides that are documents in landscape mode — the one-point-per-slide rule, the projection-vs-reading fork that decides density, the text diet (headlines and evidence, prose to notes), and the glance test. Use when asked my slides are too busy, how much text per slide, fix this wall-of-bullets deck, or make this readable from the back of the room. Produces the density diagnosis, the per-slide fixes (split, strip, or move-to-notes), the projection/document fork decision, and the glance-test results.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexVerify a claim before repeating it — the independent-sources test (three citations of one press release is one source), the provenance trace to the original, and the confidence grading that separates established from echoed. Use when asked is this claim actually true, verify this stat before the deck, everyone cites this number where's it from, or how solid is this source. Produces the provenance trace, the independence assessment, the confidence grade with its reasoning, and the repeat-it-as phrasing.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexAudit a spreadsheet before trusting it — the error hunt (hardcoded overrides, broken ranges, silent unit mixes), the fragility map (what breaks when rows are added), and the load-bearing-formula review that catches the mistake before the meeting does. Use when asked check this spreadsheet before we present it, why don't these numbers add up, audit this model someone left behind, or is this sheet safe to build on. Produces the findings ranked by damage, the fragility map, the verified-vs-suspect ledger, and the fix list.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodex