Explore skills
Showing 17491–17520 of 77079 skills
Structure 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 CodeCodexHand over a spreadsheet so it survives its author leaving — the README tab that decodes the sheet's logic, the update runbook with sources and cadence, the fragility warnings, and the walkthrough that transfers the judgment. Use when asked document this spreadsheet before I leave, hand over the model to the team, make this sheet survivable without me, or we inherited a workbook nobody understands. Produces the README tab content, the update runbook, the known-fragilities list, and the handover walkthrough agenda.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexDecide honestly when a spreadsheet should become a database or app — the five outgrowth signals (concurrent editing, relational strain, permission needs, scale, process-in-comments), what staying costs vs what migrating costs, and the incremental escape paths. Use when asked should this be a database, our spreadsheet is breaking, is it time to move off sheets, or what should replace this monster workbook. Produces the signal assessment on the actual workbook, the stay-vs-move verdict with costs both ways, and the migration path sized to the team.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexAudit the recurring meetings a team has accreted — each standing slot tested against its original purpose, current attendance reality, and outcomes, with keep/shrink/merge/kill verdicts and the two-week cancellation experiment that settles arguments. Use when asked audit our recurring meetings, our calendar is all standing syncs, which meetings should die, or reset the team's meeting load. Produces the inventory with per-meeting verdicts, the experiment protocol, the merge map, and the re-accretion guard.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexBuild the pipeline that turns team updates into the rollup report without the Friday scramble — the collection format that aggregates cleanly, the altitude translation (team detail → leadership signal), and the automation-lite assembly that takes minutes. Use when asked I compile status from five teams every week, streamline our reporting chain, my Friday is spent chasing updates, or make the rollup write itself. Produces the collection design, the translation rules, the assembly routine, and the chase-elimination mechanics.
mohitagw15856/pm-claude-skills
Stars: 1.5kClaude CodeCodexReviews a pull request in a separate subagent that has not seen this conversation, applying the rules in REVIEW.md. TRIGGER when: this session has just opened a pull request, for example with `gh pr create`; the user asks for a review of a pull request by URL or number; or a hook reports that large changes were pushed to a pull request. DO NOT TRIGGER when: answering existing review comments → addressing-review; watching CI → monitoring-pull-requests.
opsmill/infrahub
Stars: 553Claude CodeCodexRefresh the managed Spec Kit section in coding agent context file(s)
opsmill/infrahub
Stars: 553Claude CodeCodexCommit changes at meaningful checkpoints throughout the workflow
opsmill/infrahub
Stars: 553Claude CodeCodex生成小红书和 B 站 AI 工具实操视频封面,支持脚本模式与 Agent 自主模式、真实视频证据、三画幅输出和可选创作者头像。仅在用户明确提到 oil-cover、$oil-cover、使用 oil-cover 或指定本 Skill 时触发;普通封面、首图、视频封面请求不要自动触发。
oil-oil/oil-cover
Stars: 302Claude CodeCodexCreate, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts. Use for migration/release/package, routing, evals/tests, install/trust checks, 优化已有 skill, 补 trigger 评测. Exclude summary/translation/docs, brainstorming, one-off prompts, copy-only edits, outline-only requests.
yaojingang/yao-meta-skill
Stars: 2.7kClaude CodeCodexUse when crafting or rewriting ONE Medium story so it earns reads, claps and Boost curation — the title, subtitle and kicker as a hook system, fixing a story with views but a low read ratio, making a draft scannable and curation-eligible, or reshaping a blog post or newsletter into Medium-native form. NOT scheduling, tags or submitting to a publication (that is `medium-publishing`), NOT deciding topics or cadence (that is `medium-strategy`).
ericrisco/rsc-harness
Stars: 622Claude CodeCodexUse when someone hands you an open question whose answer must survive scrutiny — a tech choice, a regulation, a what-is-actually-true-about-X — with every non-obvious claim dated and sourced, source disagreements surfaced rather than averaged away, and a cited memo as the deliverable. Also for refreshing a stale research memo. NOT sizing a market with TAM/SAM/SOM (that is `market-research`), NOT a standing cadence watch on named rivals (that is `competitor-watch`).
ericrisco/rsc-harness
Stars: 622Claude CodeCodexUse when a YouTube channel needs a system-level decision — positioning and niche, upload cadence, how videos chain into playlists and series, end-screen routing, or a what-is-working review — read from and written back to the channel's own learning wiki rather than one video's choices. NOT generating next-video topics (that is `youtube-ideation`), NOT per-video titles or thumbnail text (that is `youtube-packaging`), NOT designing the thumbnail image (that is `youtube-thumbnails`), NOT fetching metrics from the Data API (that is `youtube-api`).
ericrisco/rsc-harness
Stars: 622Claude CodeCodexUse when 用户希望在 macOS 或 Windows 安装、制作、应用、暂停、恢复或设置 HeiGe Codex Desktop 皮肤常驻,或给腾讯 CodeBuddy 桌面端(WorkBuddy)一次性换肤。
HeiGeAi/heige-codex-skin-studio
Stars: 511Claude CodeCodexNative macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces. Use when asked to profile, attach, record, or analyze Instruments .trace files, find hotspots, or optimize native app performance without opening Instruments UI.
harperreed/dotfiles
Stars: 337Claude CodeCodexUse when preparing a release, tagging a version, or when user says "release", "tag", "ship it", "push to production" - ensures all release artifacts are verified before tagging to avoid the retag-four-times failure pattern
harperreed/dotfiles
Stars: 337Claude CodeCodexImplement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.
harperreed/dotfiles
Stars: 337Claude CodeCodexAudit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
harperreed/dotfiles
Stars: 337Claude CodeCodexRefactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.
harperreed/dotfiles
Stars: 337Claude CodeCodex