human-first-writer · v2.0.0 · 2026-09-06 · sha256 51d44a1a1bc573c3
human-first-writer v2.0.0A
Immutable. This exact content never changes and is served at /api/v1/blob/51d44a1a1bc573c3.
---
name: human-first-writer
description: "Use when the user asks to write authoritative, evidence-backed, human-first SEO content, articles, service pages, or local landing pages. Grounded in the 30-20-20-15-10-5 Editorial Weighting Model: Research Accuracy (30%), Search Intent (20%), Specificity (20%), Natural Flow (15%), SEO Entities (10%), and Subtle Cleanup (5%). Automatically outputs deliverables into markdown (.md) files with Title, Meta Description, Focus Keyword, and primary source citations. Trigger on: write human content, human-first writing, natural SEO article, write without sounding like AI, evidence-backed content."
metadata:
version: "2.0.0"
author: "Antigravity AI"
discipline: "content-engineering"
---
# Human-First Content Writer (The Evidence-First Editorial System)
A production-grade editorial system engineered to produce authoritative, high-converting, and genuinely natural content. Rather than relying on rigid mechanical AI evasion, this skill focuses on **empirical verification, verifiable sources, localized operational realities, and natural cadence**.
---
## ⚖️ The 6-Tier Editorial Priority Framework
```
┌────────────────────────────────────────────────────────┐
│ 1. Research Accuracy & Citation Integrity (30%) │
├────────────────────────────────────────────────────────┤
│ 2. Search Intent & Direct Value (20%) │
├────────────────────────────────────────────────────────┤
│ 3. Granular Specificity & Real Mechanisms (20%) │
├────────────────────────────────────────────────────────┤
│ 4. Natural Voice & Organic Flow (15%) │
├────────────────────────────────────────────────────────┤
│ 5. Technical & Entity-Driven SEO (10%) │
├────────────────────────────────────────────────────────┤
│ 6. Subtle AI-Slop Cleanup (5%) │
└────────────────────────────────────────────────────────┘
```
### 1. Research Accuracy & Citation Integrity (30%) — The Core Anchor
- **No Floating Statistics:** Never state a percentage, timeline, or ranking without naming the institution, survey, or source (e.g. Bangladesh Bureau of Statistics, WHO Database, municipal gazettes).
- **Nuanced Realism over Absolute Claims:** Replace sweeping absolutes ("100% zero waste", "zero traffic") with actual operational parameters (e.g. "implemented across core municipal wards", "significantly lower peak-hour gridlock along the primary arterial corridor").
- **Mandatory Sources Section:** Conclude articles with named public references and methodology notes, NEVER an internal AI audit scorecard.
### 2. Search Intent Resolution (20%)
- Deliver the **Direct Answer Block** in the first 75-100 words. The reader must get their primary answer immediately without introductory throat-clearing.
### 3. Granular Specificity & Mechanisms (20%)
- Replace vague adjectives with exact materials, tools, official standards, or historical dates.
- For local content: Name specific street intersections, wards, regulatory bodies, and regional microclimates.
### 4. Natural Voice & Organic Flow (15%)
- Do not artificially ban natural grammar constructs. Writers use em-dashes and compound sentences when rhythm demands it.
- Focus on **Burstiness and Voice Variation**: Mix punchy analytical statements with detailed, multi-clause explanations.
### 5. Entity-Driven SEO (10%)
- Prepend the document with Title, Meta Description, Primary Focus Keyword, and LSI entities.
- Structure headings (`H2`, `H3`) to match topical search journeys.
### 6. Subtle AI-Slop Cleanup (5%)
- Avoid hollow AI buzzwords (`delve`, `tapestry`, `pivotal`, `paramount`, `elevate`, `seamless`, `in today's fast-paced world`).
- Cut empty introductory setup lines and generic "In conclusion" recaps.
---
## 📌 Deliverable Output Contract
Every content generation MUST:
1. Deliver the final copy into a dedicated `.md` file in the project workspace.
2. Include the metadata frontmatter at the top (Title, Meta, Focus Keyword).
3. Conclude with a verified **Sources & References** section.
4. **NEVER** append internal AI-validation tables or robotic checklists to the public article.