Updated 3mo ago
by Uxcel-Lab
product-skills
Expert UX design and product management skills for AI assistants, built from the Uxcel learning library.
33 GitHub stars (33)
+19 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | +9 |
| Oct 3 | +3 |
| Oct 4 | 0 |
| Oct 5 | +2 |
| Oct 6 | +1 |
| Oct 7 | 0 |
| Oct 8 | +2 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | +2 |
| Oct 16 | 0 |
- 30 skills (30 skills found in its SKILL.md files)
- 7 forks (7 forks)
- 3mo ago last update (Last updated 3mo ago)
Install
Skills CLI
npx skills add Uxcel-Lab/product-skills
Asks which skills and agents to install. Just one: npx skills add Uxcel-Lab/product-skills --skill pm-assumption-rigor-audit — add -g for every project.
Claude Code
git clone https://github.com/Uxcel-Lab/product-skillscp -r "product-skills/pm/audits/assumption-rigor" ~/.claude/skills/
Copies the pm-assumption-rigor-audit skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add Uxcel-Lab/product-skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 59 files.
-
pm-assumption-rigor-audit
Run a structured rigor audit on how a team validated (or plans to validate) its assumptions — for a discovery plan, experiment, test, or any "we validated it" claim. Produces a severity-rated issue list with concrete fixes — catches testing the comfortable assumption instead of the riskiest, untestable phrasing, method fidelity mismatched to decision risk, stated intent mistaken for behavior, suc…
pm/audits/assumption-rigor/SKILL.md on GitHub (opens in a new tab) -
pm-decision-quality-audit
Run a structured quality audit on a product decision or its rationale — a build/buy/sunset/re-platform/pricing call, a decision log, a retrospective, or any "we decided X because…". Produces a severity-rated issue list with concrete fixes — catches outcome-based reasoning (resulting), deliberation mismatched to reversibility, uncalibrated confidence, confirmation/anchoring/framing/sunk-cost bias,…
pm/audits/decision-quality/SKILL.md on GitHub (opens in a new tab) -
pm-okr-metric-validity-audit
Run a structured validity audit on OKRs, KPIs, North Star Metrics, or any success-metric set. Produces a severity-rated issue list with concrete fixes — catches vanity metrics, unfalsifiable key results, outputs disguised as outcomes, gameable targets without guardrails, and metrics disconnected from business value. Use when reviewing OKRs, goals, KPIs, dashboards, or success metrics, or as a val…
pm/audits/okr-metric-validity/SKILL.md on GitHub (opens in a new tab) -
pm-prioritization-rigor-audit
Run a structured rigor audit on prioritization decisions, scored backlogs, RICE/ICE/MoSCoW outputs, or roadmap orderings. Produces a severity-rated issue list with concrete fixes — catches invented scores with false precision, priorities unmoored from strategy, feature-factory ordering, everything-is-a-must-have inflation, and trade-offs left implicit. Use when reviewing a prioritized backlog, sc…
pm/audits/prioritization-rigor/SKILL.md on GitHub (opens in a new tab) -
pm-spec-quality-audit
Run a structured quality audit on a product spec, PRD, or requirements document. Produces a severity-rated issue list with concrete fixes — catches untestable requirements, happy-path-only flows, missing scope exclusions, absent dependencies/constraints/assumptions, implementation details leaking into functional specs, and unvalidated assumptions presented as facts. Use when reviewing a spec, PRD…
pm/audits/spec-quality/SKILL.md on GitHub (opens in a new tab) -
pm-competitive-analysis
Produce or critique a competitive/market analysis that yields a strategic edge — not a flat feature table. Scopes to a research objective and industry context, finds direct/indirect/potential competitors, profiles them from honest public sources, applies the right framework (perceptual map, feature matrix, SWOT, Porter's, TAM/SAM/SOM), and ends with strategic implications and a positioning conclu…
pm/deliverables/competitive-analysis/SKILL.md on GitHub (opens in a new tab) -
pm-gtm-plan
Build a go-to-market plan that's a stage-appropriate system — customers, channels, pricing, timing, and partnerships that fit the company's maturity — not a generic launch checklist. Gates on GTM readiness (validated demand) and company stage, picks the right channel and entry timing, and treats the buyer journey as non-linear. Catches the defaults Claude misses: GTM-as-one-time-launch, stage-ski…
pm/deliverables/gtm-plan/SKILL.md on GitHub (opens in a new tab) -
pm-okrs-kpis
Write OKRs, KPIs, or a North Star Metric derived from product strategy — or review an existing goal set. Enforces outcome-based key results with baselines and targets, one focus objective per team per cycle, leading+lagging balance, and guardrails against gameable targets. Trigger when asked to write OKRs, set quarterly goals, define KPIs or success metrics, choose a North Star Metric, or run goa…
pm/deliverables/okrs-kpis/SKILL.md on GitHub (opens in a new tab) -
pm-product-spec
Write a product requirements document (PRD) or spec anchored to a validated problem, with measurable requirements and surfaced risks — or review an existing one. Trigger when asked to write a PRD, product spec, user stories, technical requirements, or to review/critique an existing spec document.
pm/deliverables/product-spec/SKILL.md on GitHub (opens in a new tab) -
pm-roadmap
Create or critique a product roadmap — outcome-oriented, theme-based, confidence-aware (Now-Next-Later) roadmaps tied to strategy, instead of dated feature lists. Gates format and detail by audience and planning horizon. Trigger when the user asks to build, write, review, or restructure a product roadmap, quarterly/annual plan, Now-Next-Later view, or roadmap presentation.
pm/deliverables/roadmap/SKILL.md on GitHub (opens in a new tab) -
pm-vision-strategy
Produce or critique a product vision and/or product strategy — an aspirational destination and the deliberate, trade-off-driven choices to reach it — not a buzzword poster or a feature list. Distinguishes the vision/strategy/roadmap/mission artifacts, ladders product vision up to company vision, forces a focused segment + differentiation + explicit "won't do", and sets the stability rule (stubbor…
pm/deliverables/vision-strategy/SKILL.md on GitHub (opens in a new tab) -
pm-personas-jtbd
Build or critique an audience-understanding artifact — research-based user personas, a Jobs-to-Be-Done framing, or the choice between them. Grounds the work in real research (never invented demographic fiction), keeps only detail that changes a decision, and picks the lens by research objective, stage, and resources. Applies the always-true core and gates context-dependent decisions (personas vs.…
pm/foundations/personas-jtbd/SKILL.md on GitHub (opens in a new tab) -
pm-problem-statement
Write or critique a product problem statement — turning a vague prompt, signal, or feature request into a clear, evidence-grounded, testable statement of the real problem before any solution. Separates the problem from solutions, symptoms, goals, and constraints; applies the always-true core (gap not feature, root cause not symptom, specific and measurable, grounded in evidence, bridges user and…
pm/foundations/problem-statement/SKILL.md on GitHub (opens in a new tab) -
pm-user-story
Write or critique a user story — a small unit of user value framed from a real persona's need, not a restated task. Frames stories around who/what/why, keeps them INVEST and testable, maps them across the journey, and resists writing stories that add no clarity. Applies the always-true core and gates context-dependent decisions (strict formula vs. free-form, whether to write a story at all, accep…
pm/foundations/user-story/SKILL.md on GitHub (opens in a new tab) -
pm-analytics
Run a product-analytics analysis that produces a decision, not a dashboard — start from the question, pick actionable over vanity metrics, separate signal from noise, segment (averages lie), pair quant with qual, and end in an insight→impact→action story. Catches the defaults Claude misses: vanity metrics, correlation-as-causation, reacting to small samples/short windows, survivorship/selection b…
pm/processes/analytics/SKILL.md on GitHub (opens in a new tab) -
pm-assumption-testing
Plan how to test the assumptions behind a product idea before building — decompose the idea into its load-bearing beliefs, prioritize the riskiest, phrase them as falsifiable hypotheses, and pick the cheapest method that answers the question. Or critique an existing validation plan. Trigger when asked to validate an idea, de-risk a feature, plan discovery/experiments, test assumptions or a hypoth…
pm/processes/assumption-testing/SKILL.md on GitHub (opens in a new tab) -
pm-discovery
Plan or critique a product discovery process — figuring out what to build before building it. Establishes which risk you're de-risking and how much certainty the decision needs, applies the always-true core (continuous not phased, outcomes over output, problem before solution, ask about past behavior, match evidence to risk, generate solutions from validated problems, research ethically) and gate…
pm/processes/discovery/SKILL.md on GitHub (opens in a new tab) -
pm-experimentation-ab
Design or critique an A/B test or controlled product experiment with statistical rigor — pre-registered falsifiable hypothesis, sample-size/power up front, a full business cycle, one primary metric plus guardrails, segment + long-term reads, and a pre-set iterate/pivot/persevere decision. Catches the defaults Claude misses: peeking/early stopping, tiny samples, no guardrails, vanity metrics, "it…
pm/processes/experimentation-ab/SKILL.md on GitHub (opens in a new tab) -
pm-prioritization
Decide what to build first, or critique a prioritization. Derives criteria from strategy, picks the right framework for the context (RICE/ICE/MoSCoW/Kano/Impact-Effort), scores to expose trade-offs rather than manufacture false precision, sequences for flow, and says no with strategic context. Applies the always-true core and gates context-dependent decisions (which framework, scoring rigor, road…
pm/processes/prioritization/SKILL.md on GitHub (opens in a new tab) -
pm-idea-to-plan
Orchestrated, idea-to-plan PM workflow. Establishes context once, then composes the PM generative ladder in order — problem → discovery → users → riskiest-assumption test → prioritization → spec → metrics — gating each step, enforcing evidence before the spec, and handing the result to product-review. Trigger when the user wants to go from a raw idea to a build-ready plan ("take me from problem t…
pm/workflows/idea-to-plan/SKILL.md on GitHub (opens in a new tab) -
pm-product-review
Orchestrated review of a PM artifact (spec, PRD, OKRs, roadmap, prioritization, strategy). Routes by artifact type to the right audits, auto-runs the always-relevant assumption check, and returns one prioritized report. Trigger when the user asks for a full review of a PM document, "review my spec/roadmap/OKRs", "is this PRD solid", or general PM feedback — but NOT when they name a single specifi…
pm/workflows/product-review/SKILL.md on GitHub (opens in a new tab) -
ux-accessibility-audit
Run a structured WCAG 2.1 AA accessibility audit on a design, screen, component, or page. Produces a prioritized issue list — each finding cites the violated WCAG criterion, a severity rating (Critical/Major/Minor), and a concrete fix. Use when auditing for a11y compliance or as a validation step after generating UI.
ux/audits/accessibility/SKILL.md on GitHub (opens in a new tab) -
ux-aesthetics-audit
Audit the visual quality of a UI against established visual-design principles — hierarchy, emphasis, contrast, spacing, alignment, grouping, consistency, and depth. Produces a severity-rated issue list with concrete fixes. Specializes in catching overdesign, clutter, and competing focal points. Use when reviewing whether a screen looks professional, or as a validation step after generating UI.
ux/audits/aesthetics/SKILL.md on GitHub (opens in a new tab) -
ux-dark-patterns-audit
Audit a UI, flow, or copy for dark (deceptive) patterns — design that manipulates users into unintended actions. Produces a prioritized findings list naming each pattern, its intent, severity, and an honest-design fix. Use when reviewing conversion flows, checkouts, paywalls, sign-ups, or cancellation flows for ethical design issues.
ux/audits/dark-patterns/SKILL.md on GitHub (opens in a new tab) -
ux-heuristics-audit
Run a structured usability audit of any UI against Nielsen's 10 heuristics. Produces a severity-rated, prioritized issue list — each finding tagged with the violated heuristic and a concrete fix. Use when auditing a screen, flow, or component for usability problems, or as a validation step after generating UI.
ux/audits/heuristics/SKILL.md on GitHub (opens in a new tab) -
ux-information-architecture-audit
Run a structured information architecture audit on a sitemap, navigation tree, category structure, menu labels, or multi-screen product. Produces a severity-rated issue list with concrete fixes — catches scheme/task mismatches, narrow-and-deep hierarchies, low-information-scent labels, inconsistent labeling systems, single-path findability, and dead-end pages. Use when auditing IA, site structure…
ux/audits/information-architecture/SKILL.md on GitHub (opens in a new tab) -
ux-microcopy-audit
Audit interface copy — labels, buttons, errors, empty states, tooltips, notifications, form hints — against UX-writing standards. Produces a severity-rated issue list with concrete rewrites. Use when reviewing UI copy for clarity, tone, and consistency, or as a validation step on any generated screen.
ux/audits/microcopy/SKILL.md on GitHub (opens in a new tab) -
ux-mobile-responsiveness-audit
Run a structured mobile-responsiveness audit on a design, screen, or component — viewport adaptation and reflow, orientation, touch-target size and spacing, thumb reachability, mobile input ergonomics, gesture safety, and mobile readability/content priority. Produces a severity-rated issue list with concrete fixes. Use when reviewing whether a UI works on phones/tablets, or as a validation step a…
ux/audits/mobile-responsiveness/SKILL.md on GitHub (opens in a new tab) -
ux-buttons
Design or critique UI buttons — pick the right button type for the action's importance, apply sizing/label/state best practices, and gate stylistic levers like shape, shadows, FABs, and icon-only buttons. Trigger when the user asks to design, choose, style, or review buttons, CTAs, button labels, button hierarchy, or button states.
ux/components/buttons/SKILL.md on GitHub (opens in a new tab) -
ux-cards
Design or critique UI cards — one-topic, scannable cards with clear hierarchy, the right container style (elevated, outlined, flat), and restrained shadows. Trigger when the user asks to design or review cards, card layouts, card grids, content tiles, user/profile cards, or a browse view built from cards.
ux/components/cards/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.