How do I install the Critique skill?

Run npx skillmds add majiayu000/critique in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Critique safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Critique?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Critique free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Critique?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Critique by majiayu000 — Agent Skill

Name: Critique
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

/critique

Skeptical, VC-style evaluation of a project idea.

Usage

/critique                        # Critique current project
/critique --project coordinatr   # Specific project
/critique --focus market         # Market validation focus
/critique --focus technical      # Technical feasibility focus
/critique --focus business       # Business model focus

Output Location

ideas/[project]/critiques/YYYY-MM-DD.md

Prerequisites

REQUIRED: project-brief.md must exist

ls ideas/{project}/project-brief.md
# If missing: "Run /brief first"

Execution Flow

1. Load Project Context

Read: ideas/{project}/project-brief.md
Read: ideas/{project}/competitive-analysis.md (if exists)
Read: ideas/{project}/README.md
Glob: resources/research/*.md

2. Invoke idea-critic Agent

Analysis areas:

Problem Validity - Is this a real problem? Evidence?
Market Opportunity - Size? Timing? Competition?
Solution Fit - Does solution address root cause?
Differentiation - Why will this win?
Business Model - Revenue? Unit economics?
Execution Risk - Team? Timeline? Resources?
Technical Feasibility - Can this be built?

3. Generate Critique Document

---
created: YYYY-MM-DD
verdict: strong | promising | needs_work | reconsider
confidence: high | medium | low
---

# Critique: [Project Name]

## Executive Summary
[Honest 1-2 paragraph assessment]

## Critical Concerns

### High Priority
1. **[Concern]**: [Why concerning]
   - Evidence needed: [What would resolve]

### Medium Priority
1. **[Concern]**: [Why matters]
   - Suggestion: [How to address]

### Strengths
1. **[Strength]**: [Why valuable]

## Analysis by Area
[Problem Validity, Market, Solution Fit, etc.]

## Hard Questions to Answer
1. [Tough question]
2. [Another challenge]

## Recommendations

### If You Proceed
- [De-risk action]
- [Research needed]

### If You Pivot
- [Alternative direction]

Focus Modes

`--focus market`

Market size/dynamics
Competition landscape
Customer validation
Timing and trends

`--focus technical`

Technical feasibility
Architecture complexity
Skill requirements

`--focus business`

Revenue model
Pricing strategy
Unit economics
Go-to-market

When to Use

After completing project brief
Before significant time investment
When seeking honest feedback
Before presenting to others

Not for: Ideas still forming (use /brief), when needing encouragement

Workflow

/brief -> /critique -> /research -> /spec

---name: critiquedescription: Challenge idea assumptions with skeptical VC-style evaluation. Use when user requests critique, validation, or 'is this a good idea' assessment.--- # /critique Skeptical, VC-style evaluation of a project idea. ## Usage ```bash /critique # Critique current project /critique --project coordinatr # Specific project /critique --focus market # Market validation focus /critique --focus technical # Technical feasibility focus /critique --focus business # Business model focus ``` ## Output Location ``` ideas/[project]/critiques/YYYY-MM-DD.md ``` ## Prerequisites **REQUIRED**: `project-brief.md` must exist ```bash ls ideas/{project}/project-brief.md # If missing: "Run /brief first" ``` ## Execution Flow ### 1. Load Project Context ```bash Read: ideas/{project}/project-brief.md Read: ideas/{project}/competitive-analysis.md (if exists) Read: ideas/{project}/README.md Glob: resources/research/*.md ``` ### 2. Invoke idea-critic Agent Analysis areas: 1. **Problem Validity** - Is this a real problem? Evidence? 2. **Market Opportunity** - Size? Timing? Competition? 3. **Solution Fit** - Does solution address root cause? 4. **Differentiation** - Why will this win? 5. **Business Model** - Revenue? Unit economics? 6. **Execution Risk** - Team? Timeline? Resources? 7. **Technical Feasibility** - Can this be built? ### 3. Generate Critique Document ```markdown --- created: YYYY-MM-DD verdict: strong | promising | needs_work | reconsider confidence: high | medium | low --- # Critique: [Project Name] ## Executive Summary [Honest 1-2 paragraph assessment] ## Critical Concerns ### High Priority 1. **[Concern]**: [Why concerning] - Evidence needed: [What would resolve] ### Medium Priority 1. **[Concern]**: [Why matters] - Suggestion: [How to address] ### Strengths 1. **[Strength]**: [Why valuable] ## Analysis by Area [Problem Validity, Market, Solution Fit, etc.] ## Hard Questions to Answer 1. [Tough question] 2. [Another challenge] ## Recommendations ### If You Proceed - [De-risk action] - [Research needed] ### If You Pivot - [Alternative direction] ``` ## Focus Modes ### `--focus market` - Market size/dynamics - Competition landscape - Customer validation - Timing and trends ### `--focus technical` - Technical feasibility - Architecture complexity - Skill requirements ### `--focus business` - Revenue model - Pricing strategy - Unit economics - Go-to-market ## When to Use - After completing project brief - Before significant time investment - When seeking honest feedback - Before presenting to others **Not for**: Ideas still forming (use /brief), when needing encouragement ## Workflow ``` /brief -> /critique -> /research -> /spec ```

Frequently asked questions