The Local Content Briefs Skill: Complete Briefs That Writers Can Execute
You have the content strategy. You know you need a storm damage roofing page for your client in Charlotte. You open a doc and stare at it.
You know the page needs to cover storm damage repair — but which aspects of storm damage repair? How deep on insurance claims? Should it cover temporary tarping? What about the inspection process after a storm? How do you work in the local entities without it reading like keyword stuffing? Where does the FAQ section go? What schema does this page need? What questions should use direct-answer formatting for AI Overview eligibility?
You’ve done this fifty times and it still takes an hour to brief properly.
The alternative is not briefing properly. Write a quick outline, hand it to a writer, get back 800 words that hit the keyword but miss the concept. The page ranks weakly because it doesn’t demonstrate expertise. It gets ignored by AI systems because it doesn’t answer the questions searchers actually ask. Six months later, you’re rewriting it.
The briefing step determines whether the content works. Skip it or do it poorly, and the content underperforms. Do it well, and the content earns its rankings.
The Shift
One prompt. A complete content brief specifying every concept the page needs to cover, the depth of treatment for each concept, the local entities to weave in and where, the questions the page must answer, the schema to implement, the internal links to place, and the sections that should use direct-answer formatting for AI Overview eligibility.
The brief a good writer needs — or that Claude CLI needs to generate the full page — produced in one session.
Not an outline. A complete specification that makes thin content impossible.
What This Looks Like
Prompt: "Write a complete content brief for the Storm Damage Roofing
location page for Peak Roofing in Charlotte NC.
Include concept coverage plan, required local entities,
schema requirements, internal linking, and AI Overview formatting."
Skills fired: dispatch → local-content-briefs
CONTENT BRIEF: Storm Damage Roof Repair — Charlotte NC
═══════════════════════════════════════════════════════════════
CORE CONCEPT
How a Charlotte homeowner evaluates storm damage, navigates the
insurance claim process, and works with a roofing contractor to
restore their roof — from identifying damage through completed repair.
This is not a page about "storm damage roof repair" as a keyword.
It's a page that demonstrates complete expertise on the topic of
storm damage roofing in the Charlotte market.
═══════════════════════════════════════════════════════════════
CONTENT VEHICLE: Location Page
TARGET WORD COUNT: 1,400–1,800 words
PRIMARY KEYWORD: "storm damage roof repair charlotte" | 140/mo
═══════════════════════════════════════════════════════════════
CONCEPT COVERAGE PLAN
COMPREHENSIVE COVERAGE (400-500 words each):
1. Identifying Storm Damage on Your Roof
Why comprehensive: This is the entry point. Users searching this
term have experienced a storm and need to know if they have damage.
Key points to cover:
- Visual signs of hail damage (dented vents, granule loss)
- Visual signs of wind damage (lifted shingles, exposed underlayment)
- When it's safe to inspect yourself vs. call a professional
- Time sensitivity — why waiting makes damage worse
Local specificity:
- Charlotte hail patterns (spring/early summer storms)
- Typical wind speeds in Charlotte severe weather
- How Carolina humidity affects damage progression
2. The Insurance Claim Process for Roof Damage
Why comprehensive: This is the decision gate. Users need to know
whether insurance covers repair before they commit.
Key points to cover:
- What homeowner's insurance typically covers
- Documentation required before filing
- The adjuster visit — expectations and preparation
- Working with a contractor on insurance claims
- Timeline from claim to completion
Local specificity:
- NC Department of Insurance as regulatory reference
- NC-specific insurance considerations
- Common Charlotte-area insurers
───────────────────────────────────────────────────────────────
STANDARD COVERAGE (200-300 words each):
3. Emergency Tarping and Temporary Protection
Cover: When tarping is needed, what it protects against,
duration, cost considerations
Link to: Emergency roof repair page
4. The Professional Inspection Process
Cover: What inspection includes, how long it takes,
what the report contains, free vs. paid inspections
5. Repair vs. Full Replacement Decision
Cover: Factors determining repair vs. replace, age of roof,
extent of damage, insurance considerations
───────────────────────────────────────────────────────────────
BRIEF COVERAGE (75-150 words each):
6. Timeline from Claim to Completion
Key point: Typical timeline, factors affecting speed
7. What If the Adjuster Underestimates?
Key point: Options for disputing, supplemental claims
8. Choosing a Storm Damage Contractor
Key point: What to look for, red flags, questions to ask
═══════════════════════════════════════════════════════════════
REQUIRED LOCAL ENTITIES
| Entity | Type | Context for Mention |
|--------|------|---------------------|
| Peak Roofing | Business | Intro paragraph, CTA sections |
| Charlotte, NC | Geography | Throughout — primary geo signal |
| Mecklenburg County | Geography | Service area section |
| NC Dept. of Insurance | Regulatory | Insurance section reference |
| Key neighborhoods | Geography | Service area list |
| Charlotte storm season | Local fact | April-September timing |
═══════════════════════════════════════════════════════════════
QUESTIONS THIS CONTENT ANSWERS
| Question | Section | AI Overview? |
|----------|---------|--------------|
| How do I know if my roof has storm damage? | Section 1 | YES |
| Does insurance cover storm damage? | Section 2 | YES |
| How long does storm damage repair take? | Section 6 | YES |
| Should I tarp my roof after a storm? | Section 3 | NO |
| Should I repair or replace after storm damage? | Section 5 | NO |
| What does a roof inspection include? | Section 4 | NO |
| How do I file an insurance claim? | Section 2 | YES |
| What if my claim is denied? | Section 7 | NO |
═══════════════════════════════════════════════════════════════
SCHEMA TO IMPLEMENT
LocalBusiness:
- @type: RoofingContractor
- name, address, telephone, areaServed
- openingHours, priceRange
FAQPage:
- Mark up 4 questions with AI Overview formatting
- Each question/answer pair as separate FAQ item
Service:
- @type: Service
- name: Storm Damage Roof Repair
- provider: [LocalBusiness reference]
- areaServed: Charlotte, NC
═══════════════════════════════════════════════════════════════
INTERNAL LINKS
| Link to | Anchor text | Placement |
|---------|-------------|-----------|
| /roofing-company-charlotte-nc/ | Charlotte roofing | Intro |
| /emergency-roof-repair-charlotte/ | emergency roof repair | Section 3 |
| /blog/roof-insurance-claims-nc/ | insurance claim process | Section 2 |
| /roof-replacement-charlotte-nc/ | roof replacement | Section 5 |
═══════════════════════════════════════════════════════════════
AI OVERVIEW FORMATTING
These questions use direct-answer format:
H3 question heading → 2-3 sentence direct answer → expanded content
- How do I know if my roof has storm damage?
- Does homeowner's insurance cover storm damage?
- How long does storm damage roof repair take?
- How do I file an insurance claim for roof damage?
Format each as:
H3: [Question exactly as users ask it]
[2-3 sentence direct answer that could stand alone]
[Expanded content with detail, examples, local specificity]
═══════════════════════════════════════════════════════════════
RECOMMENDED STRUCTURE
H1: Storm Damage Roof Repair in Charlotte NC
[Opening: 100 words establishing expertise, Charlotte storm context,
urgency acknowledgment, Peak Roofing as solution]
H2: How to Identify Storm Damage on Your Roof
H3: Signs of Hail Damage
H3: Signs of Wind Damage
H3: When to Call a Professional
H2: Navigating the Insurance Claim Process
H3: What Does Insurance Cover?
H3: How do I file an insurance claim for roof damage?
H3: Working With Your Contractor on the Claim
H2: Emergency Tarping and Temporary Protection
H2: The Professional Inspection Process
H2: Repair vs. Replacement: Making the Decision
H2: Frequently Asked Questions
H3: How long does storm damage roof repair take?
H3: What if my insurance claim is underestimated?
H3: How do I choose a storm damage contractor?
H2: Get Your Free Storm Damage Inspection
[CTA: phone, form, service area]
═══════════════════════════════════════════════════════════════
QUALITY CHECKLIST
- [ ] 15+ distinct concepts covered
- [ ] All local entities mentioned in natural context
- [ ] All 8 reader questions answerable from content
- [ ] NAP appears naturally in 2+ locations
- [ ] 4 sections use AI Overview direct-answer format
- [ ] Internal links placed with concept-based anchors
- [ ] No keyword stuffing — concepts appear because relevant
- [ ] Opening 100 words establish concept + local context
- [ ] CTA at end and mid-page
- [ ] Schema requirements implementable as specifiedThat’s the output. A complete specification. Hand it to a writer or feed it to Claude CLI — the content that comes back will cover the concept completely because the brief doesn’t allow otherwise.
What This Skill Covers
Concept coverage plans with depth assignments. Not every concept needs equal treatment. The brief specifies comprehensive coverage (400-500 words) for core concepts, standard coverage (200-300 words) for supporting concepts, and brief coverage (75-150 words) for tertiary mentions. The depth is calibrated to what each concept requires.
Local entity integration with placement guidance. Which local entities belong in this content, and where they should appear naturally. Business name, city, neighborhoods, local landmarks, regulatory bodies — specified with context for natural mention, not keyword stuffing.
Question mapping to sections. The 8-10 questions the target reader would have, mapped to which section answers each one, flagged for whether direct-answer formatting makes sense for AI Overview eligibility.
AI Overview formatting specifications. Which questions should use direct-answer format (H3 question heading, 2-3 sentence direct answer, then expanded content). The sections most likely to be retrieved and cited by AI systems.
Schema requirements per page type. LocalBusiness schema properties, FAQPage markup for Q&A sections, Service schema for specific service offerings. Specified precisely enough for a developer or schema tool to implement.
Internal linking targets with anchor text. Which other pages this content should link to, what anchor text to use, where in the content the link should appear. The brief builds the internal link structure that the content strategy designed.
Recommended H1/H2/H3 structure. The section architecture that sequences information in the order a user making a decision needs it. Not a suggestion — a structure the writer follows.
Quality checklist. The verification criteria that ensure the brief was executed correctly. 15+ concepts covered. Local entities present. Questions answered. Schema implementable. The checklist catches gaps before publishing.
Who Uses This and When
After every content strategy session. The local-content-strategy skill identifies what to build. This skill specifies what each piece must contain. They chain together — run strategy, then run briefs for each piece identified.
Agencies briefing writers. Instead of a vague outline, hand writers a complete specification. The brief makes expectations clear and reduces revision cycles.
Practitioners running CLI generation loops. Each brief is self-contained input for Claude generation. Brief in, complete content out. The brief format is designed for this use case.
Any time a content piece needs to be fully specified before writing starts. Location pages, blog posts, FAQ content, service pages, pillar pages — the skill produces briefs for all local content types.
Brief Types by Content Vehicle
The skill adapts briefs to content type:
Location page briefs emphasize local entity density, GBP consistency, LocalBusiness schema, NAP placement, service area specificity, and what makes this location genuinely unique. Not a template with the city name swapped — content specific to this market.
Blog/FAQ briefs emphasize informational intent, direct-answer formatting for AI retrieval, FAQPage schema, depth on research-phase questions, and internal links to transactional pages. Content that answers real questions completely.
Pillar page briefs emphasize comprehensive concept coverage across the full topic domain, hub-and-spoke internal linking, E-E-A-T signals, multiple schema types. Target 2,500-4,000 words with 20+ distinct concepts.
Service page briefs emphasize transactional intent, specific service scope, trust signals, conversion-oriented structure. Content that converts visitors who’ve already decided they need this service.
The same skill, adapted output. Specify the content vehicle in your prompt; get a brief calibrated for that type.
Cost of Absence
Without this skill, content gets written toward keywords rather than concept completeness.
The resulting pages are thin:
They rank weakly. Google’s systems evaluate topic authority, not keyword presence. A page that mentions “storm damage roof repair” twelve times but doesn’t explain the insurance claim process, the inspection timeline, or the repair vs. replacement decision doesn’t demonstrate expertise. It ranks accordingly.
AI systems ignore them. AI Overviews and ChatGPT retrieve from sources that comprehensively address topics. A page that gestures at a concept without covering it completely doesn’t get cited.
They need rewriting. Six months after publishing, the thin content isn’t performing. Now you’re rewriting — or more likely, starting over with a proper brief. The skipped step catches up with you.
With this skill, every piece is briefed for complete concept coverage from the start. The content performs longer, requires less maintenance, and doesn’t need the rewrite cycle.
How It Chains
The skill sits at the end of the content planning workflow:
local-keyword-research → local-content-strategy → local-content-briefsInput: Concept cluster from local-content-strategy, or a topic and business context directly. The skill can work from strategy output or from a simple prompt like “brief me on emergency plumbing services for [Business] in [City].”
Output: Complete semantic content brief. Concept coverage plan, local entities, schema requirements, question mapping, AI formatting, structure, quality checklist.
What comes next: A writer executes the brief. Or Claude CLI generates from the brief. The brief is the specification; execution is the next step.
For bulk production, run briefs for all pieces in the content strategy. Each brief is a separate file; each file is one generation call. The skills chain was designed for this workflow.
The First Prompt
After local-content-strategy identifies your content vehicles:
"Write a complete content brief for the [concept cluster] location page
for [Business Name] in [City].
Include concept coverage plan, required local entities,
schema requirements, internal linking, and AI Overview formatting."The brief specifies exactly what the content must contain. Thin content is no longer possible — the brief doesn’t allow it.