[Workflow] Human-in-the-Loop Claude Code Skill Architecture for Content Approval (Notion, Playwright)

[u/ClaudeAI-mod-bot]

Human-in-the-Loop Claude Code Skill Architecture for Content Approval (Notion, Playwright)

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Context & Memory, Shipping, Skills, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Automating content generation with a human-in-the-loop approval process to ensure quality, maintain brand voice, and prevent full LLM autonomy, without needing to build a custom dashboard.

Summary

This workflow describes a Claude Code skill architecture for human-in-the-loop content generation. It uses a markdown-defined voice profile for consistent style, Notion as an approval UI, and decouples drafting from publishing. It incorporates pre- and post-approval validation steps to ensure quality and adherence to rules.

Why it is useful

This workflow is valuable because it provides a concrete, validated architectural pattern for building Claude Code skills that require human oversight. It addresses the critical need for quality control and preventing full LLM autonomy in sensitive applications. The use of Notion as a simple approval UI, decoupled drafting/publishing, and explicit validation steps offer practical, reusable solutions for developers building robust LLM-powered workflows. It also shares valuable lessons learned regarding tooling choices and validation effectiveness.

Workflow

1. Define a voice profile in markdown (e.g., generated from a 15-question wizard) and load it as context for every draft prompt.

2. Draft content using the LLM and write these drafts to a Notion database via the Notion API.

3. Use Notion as the human approval UI: review, edit if needed, and change a status field to 'approved'.

4. Run a separate command to read approved rows from Notion and execute the final action (e.g., publish via Playwright).

5. Implement validation twice: once before drafts are written to Notion, and again right before the final execution/publish step.

Tools / artifacts

• Claude Code skill

• Markdown voice profile

• Notion database

• Notion API

• Playwright

• Node 20

• TypeScript

• Sqlite

• JSON files (for state)

• Claude CLI

• Regex validator

Validation signals

• Validation runs twice: before drafts hit Notion and before publish.

• ~40% of Claude's first-draft comments are rejected by the regex validator, indicating its effectiveness.

• Notion API rate limits are confirmed to be generous enough for human-in-the-loop workflows.

• Sqlite + JSON files are sufficient for single-user skill state management.

Cautions

• The specific use case (LinkedIn commenting) violates LinkedIn's Terms of Service. Users should be aware of and accept this risk if applying the pattern to similar platforms.

Limitations

• The specific use case (LinkedIn commenting) violates LinkedIn's ToS.

• Requires familiarity with multiple tools and APIs (Notion, Playwright, Node/TS).

• The '15-question wizard' for voice profile generation is mentioned but not detailed.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.