# Multica Skill: HTML Blog Approval Preview

Attach this skill to Blog Writer, SEO Consultant, and Chief of Staff.

## Trigger

Use whenever a blog post, article, landing-page draft, content recommendation, or publishable content package is being sent back for human approval.

## Goal

Return the approval draft as a self-contained HTML preview that looks broadly similar to the target website and is clearly labelled as not published.

The preview should help the human judge:

- Does this feel like it belongs on the target site?
- Does the tone match the brand?
- Would the layout make sense for this business?
- Are claims safe and supported?
- What still needs approval before publishing?

## Required process

1. Read the content brief, SEO/research inputs, and target website.
2. Identify lightweight style cues:
   - colours
   - typography feel
   - spacing
   - button/link style
   - card/section style
   - header/footer tone
   - writing voice
3. Draft or package the content.
4. Create a static HTML preview.
5. Keep it self-contained:
   - semantic HTML
   - inline CSS inside `<style>`
   - no external scripts
   - no tracking
6. Add a visible label: `Draft approval preview — not published`.
7. Include approval notes and claim/evidence gaps.
8. Do not publish, deploy, or imply the preview is live.

## Preview content should include

- Draft title
- Meta title/meta description if relevant
- Audience/search intent if relevant
- Draft body or outline
- Suggested internal links if relevant
- Claims needing review
- Evidence/gap notes
- Approval decision needed

## Style rules

Mirror broad cues, not proprietary assets.

Good:

- similar colour palette
- similar spacing/card feel
- similar heading rhythm
- matching tone and vocabulary

Bad:

- copying private assets
- pretending the page is live
- exact clone imitation
- using external tracking/scripts
- publishing without approval

## Handoff format

```md
## HTML preview
File/link: ...

## Draft package
- Title
- Meta description
- Audience/search intent

## Style cues mirrored
What was borrowed from the target site.

## Claims/evidence
- [Confirmed] ...
- [Assumption] ...
- [Gap] ...

## Approval needed
Exact decision before publish/edit/send.
```

## If a full draft is not warranted

If the source evidence is too weak or the content opportunity is not justified, do not force a draft. Return a topic recommendation, outline, or `Hold — blocker/gap` instead.

## Quality bar

The human should be able to review the article as an approval object, not as a wall of markdown pretending to be an approval artifact.