skills/brief2web/SKILL.md
Converts a business brief document (Word, PDF, or PowerPoint) into structured website content including messaging framework, webpage copy, visual strategy, and LinkedIn posts. Triggers when user says 'brief2web', 'convert brief', 'brief to website', 'business brief to webpage', or uploads a .docx/.pdf/.pptx and asks for website content.
npx skillsauth add asets-gobizit/claude-skills converting-briefs-to-websitesInstall 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.
Converts a business brief into a complete website content package: messaging framework, webpage structure, copy, visual strategy, and LinkedIn posts. Operates as a Senior Conversion Copywriter / Web Marketing Strategist. All business facts must come from the brief — never invented.
| Script | Purpose |
|--------|---------|
| brief2web.py | Reads brief doc text, saves LinkedIn posts as .docx |
Run directly: python "C:/Users/dansk/.claude/skills/brief2web/brief2web.py" --file "filename.docx"
/brief2web
Or: user provides a brief document name and asks to generate website content.
Run these steps in order. Do not skip or reorder.
Ask these questions one at a time (not all at once):
Q1 — Existing website (optional):
"Do you have an existing website? If yes, share the URL and I'll match its design."
Q2 — New page URL:
"What will be the URL of the new page? (e.g. https://gobizit.ai/ai-crm-automation)"
Q3 — Brief document name(s):
"What is the filename of your brief? It should be in the Vid-Trrasncipts-Files folder. If multiple files, separate with commas."
Brief document folder: C:/Users/dansk/Zoho WorkDrive (Go Biz IT)/00 Claude.ai/@CoWorkAccess/Vid-Trrasncipts-Files/
Supported formats: .docx, .pdf, .ppt, .pptx
Read brief using:
python "C:/Users/dansk/.claude/skills/brief2web/brief2web.py" --file "filename.docx"
Scan: C:/Users/dansk/Zoho WorkDrive (Go Biz IT)/00 Claude.ai/@CoWorkAccess/Vid-Trrasncipts-Files/
Extract only information explicitly present in the document:
Required (must find):
Extract only if present:
Constraint: Do NOT invent or assume any business facts not in the document.
Generate and display:
MESSAGING FRAMEWORK
────────────────────────────────────────
Target Audience: [who they serve]
Problem: [what pain they solve]
Desired Outcome: [what customers want to achieve]
Unique Value Prop: [what makes them different]
Core Offer: [what they provide]
CTA Strategy: [only if CTA found in brief — otherwise omit this line]
────────────────────────────────────────
Ask:
"Do you approve this messaging framework before I generate the webpage?"
Do not proceed until user confirms approval.
Assess if a new service/product offer should be suggested based on the brief.
If appropriate, generate:
SUGGESTED OFFER
────────────────────────────────────────
[Offer title]
[1-2 sentence description]
Deliverables:
• [Item 1]
• [Item 2]
• [Item 3]
────────────────────────────────────────
Ask:
"Would you like this suggested offer included on the webpage?"
Only include if user approves.
Generate a structured layout. Adapt sections to content available in the brief:
| # | Section | Include When | |---|---------|-------------| | 1 | Hero | Always | | 2 | Problem | If customer problem found in brief | | 3 | Solution | Always | | 4 | Benefits | If benefits/outcomes found | | 5 | Products / Services | Always | | 6 | Credibility / Proof | If credibility indicators found | | 7 | Call to Action | Only if CTA found in brief |
Generate full copy for each included section.
Output before generating any images:
VISUAL STRATEGY
────────────────────────────────────────
Hero Image: [description]
Section Graphics: [description]
Background Style: [description]
Color Palette: [from existing site OR derived from industry]
────────────────────────────────────────
Before finalizing output, run:
CONVERSION CHECK
────────────────────────────────────────
Headline clarity: [ PASS / FAIL ]
Value proposition clarity: [ PASS / FAIL ]
CTA visibility: [ PASS / FAIL ] (skip if no CTA)
Credibility signals: [ PASS / FAIL ]
────────────────────────────────────────
If any item FAILS:
Generate 1–2 LinkedIn posts that:
Save as .docx using:
python "C:/Users/dansk/.claude/skills/brief2web/brief2web.py" --linkedin "post text here" --slug "page-slug"
Output folder: C:/Users/dansk/Zoho WorkDrive (Go Biz IT)/00 Claude.ai/@CoWorkAccess/Vid-Trrasncipts-Files/
File naming: linkedin-post-[page-slug]-[YYYY-MM-DD].docx
| Tool | Install |
|------|---------|
| python-docx | pip install python-docx |
| pdfplumber | pip install pdfplumber |
| python-pptx | pip install python-pptx |
data-ai
Automated backup skill for PKA + Obsidian + Claude memory. Snapshots pka.db (via SQLite .backup so WAL is handled safely), the Obsidian vault, Claude memory files, agent profiles, and the help-content Excel into a single timestamped zip in Zoho WorkDrive. Daily/weekly/monthly retention rotation built in. USE WHEN Danny says "backup", "run backup", "snapshot pka", or to recover from a snapshot.
testing
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology, packaged as the stress-test skill. MANDATORY TRIGGERS: 'stress-test this', 'stress test this', 'pressure-test this', 'pressure test this', 'war room this', 'council this', 'run the council', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a stress-test question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.
content-media
Weekly scan of Obsidian vault for empty/low-content notes. Moves them to zToBeDeleted/ for user review. Use when the user says "tidy obsidian", "clean obsidian", "obsidian cleanup", or on scheduled weekly run.
development
Design-first website builder. Accepts a Claude Design export (HTML or screenshot) as a visual blueprint, collects business inputs, calls Claude API to generate a design-matched index.html, and publishes to GitHub Pages. Falls back to vibe-based generation if no design is provided. Use when the user says "make-website-design", "design website", "build from design", or provides a Claude Design export for website generation.