.claude/skills/ln-005-agent-reviewer/SKILL.md
Universal context reviewer: delegates arbitrary context (plans, decisions, documents, architecture proposals) to external agents (Codex + Gemini) for independent review with debate protocol. Context always passed via files.
npx skillsauth add cbbkrd-tech/jl-finishes ln-005-agent-reviewerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
Runs parallel external agent reviews on arbitrary context, critically verifies suggestions, returns filtered improvements.
| Parameter | Value |
|-----------|-------|
| review_type | contextreview |
| skill_group | 005 |
| prompt_template | shared/agents/prompt_templates/context_review.md |
| verdict_acceptable | CONTEXT_ACCEPTABLE |
| Input | Required | Description |
|-------|----------|-------------|
| context_files | Yes | List of file paths containing context to review (relative to CWD) |
| identifier | No | Short label for file naming (default: review_YYYYMMDD_HHMMSS) |
| focus | No | List of areas to focus on (default: all 6) |
| review_title | No | Human-readable title (default: "Context Review") |
Context delivery rule: Context is ALWAYS passed via files.
.agent-review/context/ with the content, then passes the file pathMANDATORY READ: Load shared/references/agent_review_workflow.md for Health Check, Ensure .agent-review/, Load Review Memory, Run Agents, Critical Verification + Debate, Aggregate + Return, Save Review Summary, Fallback Rules, Critical Rules, and Definition of Done. Load shared/references/agent_delegation_pattern.md for Reference Passing Pattern, Review Persistence Pattern, Agent Timeout Policy, and Debate Protocol.
Health check: per shared workflow, filter by skill_group = 005.
Resolve identifier: If identifier not provided, generate review_YYYYMMDD_HHMMSS. Sanitize: lowercase, replace spaces with hyphens, ASCII only.
Ensure .agent-review/: per shared workflow. Additionally create .agent-review/context/ subdir if it doesn't exist (for materialized context files).
Materialize context (if needed): If context is from chat/conversation (not an existing file):
.agent-review/context/{identifier}_context.mdcontext_files listBuild prompt: Read template shared/agents/prompt_templates/context_review.md.
{review_title} with title or "Context Review"{context_refs} with bullet list: - {path} per context file{focus_areas} with filtered subset or "All default areas" if no focus specified.agent-review/{identifier}_contextreview_prompt.md (single shared file -- both agents read the same prompt)6-9) Load Review Memory, Run agents, Critical Verification + Debate, Aggregate + Return: per shared workflow.
{review_type} in challenge template = review_title or "Context Review"{story_ref} in challenge template = identifierverdict: CONTEXT_ACCEPTABLE | SUGGESTIONS | SKIPPED
suggestions:
- area: "logic | feasibility | completeness | consistency | best_practices | risk"
issue: "What is wrong or could be improved"
suggestion: "Specific actionable change"
confidence: 95
impact_percent: 15
source: "codex-review"
resolution: "accepted | accepted_after_debate | accepted_after_followup | rejected"
Agent stats and debate log per shared workflow output schema.
shared/references/agent_review_workflow.mdshared/references/agent_delegation_pattern.mdshared/agents/prompt_templates/context_review.mdshared/agents/schemas/context_review_schema.jsonVersion: 1.0.0 Last Updated: 2026-02-25
testing
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
development
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
development
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
development
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.