# Multica Skill: HTML Styled Report Preview

Attach this skill to agents that produce reports, audits, plans, drafts, recommendations, or approval packages.

## Trigger

Use whenever work is being returned to a human and the output is more than a tiny issue comment.

## Goal

Return substantial deliverables as readable, self-contained HTML documents. If a website or brand is part of the task, broadly mirror its style so the approval experience feels contextual and easy to review.

## When HTML is worth it

Use HTML for:

- SEO/site audits
- research reports
- strategy recommendations
- blog/content drafts
- approval packages
- client/customer-facing preview material
- multi-agent final reports

A short ticket comment does not need HTML.

## Required process

1. Identify the target audience for the report.
2. Identify the target website/brand if one is part of the task.
3. Inspect broad style cues where possible:
   - colours
   - typography feel
   - spacing
   - card/section structure
   - button/link style
   - tone and vocabulary
4. Create a static `.html` report or preview.
5. Keep it self-contained:
   - semantic HTML
   - inline CSS inside `<style>`
   - no external scripts
   - no tracking
6. Add a visible status label:
   - `Draft report — not published`
   - `Approval preview — not published`
   - `Internal recommendation — not published`
7. Include evidence labels, gaps, and approval notes.
8. Return the file/link plus a short issue comment.

## Recommended report sections

Use only the sections that fit:

- Status label
- Executive summary
- What was requested
- What was inspected
- Findings
- Evidence and gaps
- Recommended actions
- Priority table/list
- Risks and assumptions
- Approval questions
- Appendix/source links

## Constraints

- Do not publish or deploy the HTML without explicit approval.
- Do not load external tracking scripts.
- Do not copy proprietary assets unless safe and public.
- Do not imply the report is live or final if it is for approval.
- Do not make a pixel-perfect clone of a site; mirror broad style cues only.
- If HTML cannot be created, explain why and return the most readable fallback possible.

## Output handback

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

## Summary
2–5 bullets.

## Style cues mirrored
Colours, layout, typography feel, voice.

## Evidence/gaps
Key labelled claims or unresolved gaps.

## Approval needed
Exact decision required, if any.
```

## Quality bar

The report should make review faster. If it is prettier but harder to decide from, it failed. Design serves judgment, not assumptions.