Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add cnfeat/top-pm-skills --skill figma-design-critique-pmgit clone --depth 1 https://github.com/cnfeat/top-pm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cnfeat/top-pm-skills/figma-design-critique-pm)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/figma-design-critique-pm"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/figma-design-critique-pm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/figma-design-critique-pm"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/figma-design-critique-pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00076 | $0.00910 |
| Opus 5.5 | $0.00030 | $0.00364 |
| Sonnet 5.5 | $0.00015 | $0.00182 |
| Haiku 4.5 | $0.00008 | $0.00091 |
Grade A, and why
figma-design-critique-pm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Design Critique — PM Perspective Skill
This skill is specifically for product managers critiquing designs — focused on whether the design achieves the user goal and business outcome, not whether it looks good. Different from the general design-critique skill which covers UX aesthetics; this one centres product thinking.
Required Inputs
- Design description or screen summary
- User goal (what is the user trying to accomplish?)
- Business goal (what outcome does the product need?)
- Original requirements (what was this supposed to do?)
- Key metric (what would move if this design works?)
Output Structure
1. PM Critique Summary
User goal, business goal restated. Verdict: On track / Mostly on track / Needs rethinking
One-paragraph summary: what works from a product perspective, and the single most important thing to address.
2. Goal Alignment Check
| Goal | Design supports it? | Evidence |
|---|---|---|
| [User goal] | Yes/Partial/No | [Specific observation] |
| [Business goal] | Yes/Partial/No | [Observation] |
| [Key requirement] | Yes/Partial/No | [Observation] |
3. PM Feedback (Outcome-Focused)
Every concern must tie to an outcome. "I do not like this layout" is not PM feedback. "This layout puts the primary action below the fold, which will reduce mobile conversion" is PM feedback.
[Concern] — High/Medium/Low impact
- Observation: [Neutral description of what the design does]
- User impact: [What this means for the user goal]
- Business impact: [What this means for the metric]
- Evidence basis: [Research/data/analogous patterns/hypothesis — be honest]
- Question for designer: [What to explore — not a directive]
4. What the Design Does Well
2-4 specific things working well from a product perspective — with evidence. Not "colours are nice" but "primary CTA is the most prominent element, aligning with conversion goal." Always include this section.
5. Questions Before Next Iteration
| Question | Who answers | Why it matters |
|---|---|---|
| [Question] | Designer/PM/Eng | [Impact] |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 84 lines · 76 tokens per session scan A fa8caf9d0511
figma-design-critique-pm is a skill published in the GitHub repository cnfeat/top-pm-skills (55 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 910 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
kanban-board
A Kanban board is a visual task list with columns for stages such as To do, In progress, In review, and Done. It can show filters, labels, due dates, assignees, comments, and swimlanes that group cards.
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
acid-blue-business
A visual presentation style for modern business topics, using electric blue with black, white, and grey, directional layouts, and clear spacing. It is intended for business content rather than traditional data dashboards.
architecture-client-presentation
Present a design to a client so they can make a decision rather than react to a picture — the brief restated, the moves explained against it, the options with their trade-offs, and a specific decision requested. Use when asked to present a design to a client, prepare a design review meeting, present concept options…
friction-log
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.