Archetype Review Base

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

38 stars 11 forksFinance & Crypto

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jeremybrasher/grokbot-skills --skill archetype-review-base
Manual install
git clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/archetype-review-base ~/.claude/skills/archetype-review-base

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Archetype-review-base — shared review framework

Every domain reviewer follows this skeleton. Each reviewer's own
SKILL.md adds the domain heuristics on top. This skill defines the
parts that must be IDENTICAL across all reviewers.

## Output artifact (canonical)

Pre-implementation reviewers (the `*-reviewer` agents — ~30 in `agents/` —
invoked by architect BEFORE senior-dev claims tasks) write a **threat model** at
`docs/sec-threats/TM-{slug}.md` and append a `` block (see
"Workflow scaffold" below). That is the single convention for every reviewer.

**One TM file per feature slug.** Per-reviewer filename suffixes
(`TM-api-{slug}.md`, `TM-extension-{slug}.md`) are deprecated — consumers glob
`TM-{slug}.md` and per-suffix files silently escape their checks. When multiple
domain reviewers run on the same slug, each APPENDS its own `## {reviewer}
findings` section and its own `` block to the shared
`TM-{slug}.md` — never overwrite another reviewer's sections.

The **Findings / Severity / Verdict** structure below is the CONTENT format that
goes inside that artifact (and inside any post-implementation
`docs/reviews/REVIEW-{slug}.md` produced by a review-tier agent). Path differs by
phase; the section grammar is identical.

## Mandatory report sections

The report (TM or REVIEW) MUST contain these sections in this exact order:
Read the full skill on GitHub

Details

Skill name
archetype-review-base
Path
collections/great-cto/skills/archetype-review-base/SKILL.md
Repo updated
15 September 2026

FAQ

What does the Archetype Review Base skill do?

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

How do I install the Archetype Review Base skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill archetype-review-base. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Archetype Review Base popular?

It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.

Related skills

Anti Patterns

38

jeremybrasher/grokbot-skills

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

Software Development11

Anydesign

38

jeremybrasher/grokbot-skills

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t

Frontend & Design11

Avoid AI Writing

38

jeremybrasher/grokbot-skills

Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Observe the text first. Do not use it to decide authorship, hiring, academic integrity, or attribution from the flags. Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.

Writing & Content11

Vertical Onboarding

38

jeremybrasher/grokbot-skills

Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value target. Applied by migration-import-engineer and architect/pm so onboarding is designed as a funnel, not an afterthought. Our whole wedge is "low switching cost"; this skill makes that real on day one.

Finance & Crypto11

Value Proposition

48

sethdford/claude-skills

Define the specific value your product delivers relative to alternatives and trade-offs.

Finance & Crypto10

Accounting Firm Growth

39

lionelsimai/claude-skills-collection

Grow accounting firms. TRIGGERS - Use when user needs help with accounting-firm-growth related tasks.

Finance & Crypto

Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.