# Postkit Review

> Critique a draft post against the brand profile (memory/brand_*.md) and theme.css across three lenses — strategy (hook, angle, value arc), copy (CTA, word economy, tone), and design (layout, density, rhythm, typography). Returns HIGH/MEDIUM/LOW findings. Use when the user asks to review, critique, polish, or improve a draft before rendering.

- **Type:** Skill
- **Install:** `agentstack add skill-trystan-sa-postkit-postkit-review`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Trystan-SA](https://agentstack.voostack.com/s/trystan-sa)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Trystan-SA](https://github.com/Trystan-SA)
- **Source:** https://github.com/Trystan-SA/postkit/tree/main/templates/project/.claude/skills/postkit-review
- **Website:** https://www.npmjs.com/package/postkit

## Install

```sh
agentstack add skill-trystan-sa-postkit-postkit-review
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# /postkit-review — three-lens critique

You review a post draft (one or more slides) against the user's brand and
design system, surfacing the changes that will materially improve performance.

Do not rewrite the post yourself. Your job is to **identify issues** and
**propose specific fixes** so the user (or the next run of `/postkit-new`) can
apply them.

## Inputs

1. The target post folder (default: most recently modified `posts//`).
   If ambiguous, ask.
2. **The brand profile in `memory/`** — read every `memory/brand_*.md` file
   at the project root: `brand_identity.md`, `brand_audience.md`,
   `brand_goals.md`, `brand_voice.md`, `brand_visual.md`, `brand_hooks.md`.
   If any are missing, stop and send the user to `/postkit-setup`. Don't
   read brand state from Claude Code internal memory.
3. `theme.css` at the project root — palette, tokens, component classes.
4. Any review logs left by a previous `/postkit-review` run in
   `posts//review.md` — don't repeat findings the user already addressed.

Read all slide files, `post.json`, and **every `caption*.md` file** in the
post folder before forming opinions. Each caption file targets a specific
platform (filename pattern `caption-.md`); critique each one
against that platform's length and formatting conventions, not just the
brand voice. Flag a caption that ignores its platform's norms (e.g. a
LinkedIn-length caption saved as `caption-x.md`, or hashtag spam on
LinkedIn) as HIGH.

**Alt text check.** Any post with slides must have an `## Alt text` section
in each caption file with one bullet per slide. Flag missing alt text as
HIGH (accessibility regression). Also flag alt copy that just repeats the
caption, exceeds ~125 chars, uses emojis/hashtags, or describes the
strategic purpose instead of what's visually on the slide — these as
MEDIUM.

## Three lenses, one pass

Do all three in the same response. Don't spawn sub-agents.

### 1. Strategy

- **Hook strength.** Does slide 1 stop a thumb in  You're reading HTML/CSS source, not rendered PNGs. Reason about visual
> weight from markup structure, class names, and inline styles. If you genuinely
> can't tell without seeing pixels, ask the user to run `/postkit-render` first
> and describe what they see, or check the `posts//output/` folder if
> PNGs already exist there.

## Output

Return one structured report:

```markdown
## /postkit-review — posts/

### HIGH IMPACT (fix these)
- **[Strategy | Copy | Design] · slide-N:** What's wrong → Specific fix
  (include the exact replacement text or CSS change).

### MEDIUM (consider)
- [Observation]

### LOW (logged)
- [Observation]

### Verdict
[REVISE | APPROVED]  — one-line summary.
```

APPROVED = zero HIGH items. REVISE otherwise.

After the report, offer to save it to `posts//review.md` so the next
review skips addressed items.

## Important

- Don't touch slide HTML. Suggest, don't edit.
- Don't re-critique decisions the user explicitly confirmed earlier in the
  conversation.
- Skip `/postkit-render` unless the user asks — this is a source-level review.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Trystan-SA](https://github.com/Trystan-SA)
- **Source:** [Trystan-SA/postkit](https://github.com/Trystan-SA/postkit)
- **License:** MIT
- **Homepage:** https://www.npmjs.com/package/postkit

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-trystan-sa-postkit-postkit-review
- Seller: https://agentstack.voostack.com/s/trystan-sa
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.