最強通用型SEO文章寫作
指令
# Universal SEO Batch Writing Skill (English Version)
## Skill Overview
This Skill is designed to generate **high-quality, original, EEAT-compliant SEO articles** for **any product or service**, using a competitor article library in the current Board.
It can:
* Automatically select **10 best competitor SEO articles** from the current Board as references
* Intelligently avoid **topic overlap** with your existing articles
* Deeply integrate **your product's unique features, data, and positioning**
* Follow **Google EEAT** principles and pass originality checks
* Run a built-in **Quality Assurance system** to ensure each article meets standards
* Output **WordPress-ready HTML** (copy-paste into WP backend)
---
# Required Inputs (You Provide)
## Input A: Product Information (Required)
Provide a structured product brief including:
* Product name / brand name
* What it is (category + use case)
* Target audience
* Core value proposition (3–5 bullets)
* Key features (5–10 bullets)
* Pricing model (ranges, plans, tiers)
* Coverage / availability (countries, channels, platforms, industries, etc.)
* Proof/data (metrics, user growth, savings, performance, NPS, case studies, testimonials)
* Competitive advantages vs alternatives
* Limitations / constraints / best-fit scenarios (for trustworthiness)
* Internal pages you want to link to (pricing page, product page, blog posts, etc.)
> If not fully provided, the Skill should use `searchBoards` or `googleSearch` to supplement.
## Input B: Competitor SEO Library (Required)
Your current Board should contain competitor SEO articles as materials.
---
# PHASE 1: Competitor Article Intelligence Selection
## STEP 1.1: Scan All Articles in the Board
Actions:
1. Use `listBoard` to retrieve all materials in the current Board
2. Use `read` to read key information from each article (first 500 lines)
3. Extract:
* Topic / keywords
* Content type (Guide / Comparison / 評論 / Tutorial, etc.)
* Word count
* Structure quality (H2/H3 hierarchy, data density, table usage)
* Target audience
* Unique angle
* Search intent (Informational / Commercial / Transactional)
## STEP 1.2: Article Quality Scoring (0–100)
**Content Quality (40)**
* Depth and completeness (15)
* Data/examples richness (10)
* Structural clarity (10)
* Actionability (5)
**SEO Optimization (30)**
* Clear keyword strategy (10)
* Title + structure optimization (10)
* Internal/external links usage (5)
* Readability/UX (5)
**Uniqueness (20)**
* Unique insights, data, framing (10)
* Potential to be rewritten into “product-aware” content (10)
**Fit (10)**
* Ease of integrating product value naturally (10)
## STEP 1.3: Select Top 10 Articles (Balanced Coverage)
Selection rules:
1. Take top 15 by score
2. Filter down to 10 while ensuring:
* Topic diversity (max 2 per broad topic cluster)
* Search intent coverage:
* 3–4 informational
* 4–5 commercial
* 1–2 transactional
* Strong relevance to the product's core use cases
* Natural opportunities to integrate product value
## STEP 1.4: Topic Duplication Check (Avoid Existing Topics)
If the Board already contains articles about your product:
1. Use `searchBoards` with keywords:
* product name, brand name
* category keyword(s)
* primary use-case keyword(s)
2. Extract existing topics and keywords
3. Remove overlapping topics from Top 10
4. Replace with new topics from the candidate pool
**Output:**
**Top 10 competitor article list** + **why they were selected**
---
# PHASE 2: Deep Product Analysis (Generic Template)
## STEP 2.1: Extract Product Core Assets
From product info (or via `searchBoards` / `googleSearch`):
**Positioning**
* What the product is (category + function)
* Core value proposition
* Target users
**Features**
* Key feature set
* Onboarding / setup flow
* Compatibility / requirements
* Support / SLA
* Unique differentiators (features competitors don't have)
**Proof & Data (EEAT critical)**
* Users / growth metrics
* Satisfaction metrics (NPS, rating, churn)
* Performance metrics (speed, uptime, results, ROI)
* Cost-saving % or time-saving metrics
* Case studies / testimonials (at least 2)
**Competitive Landscape**
Compare against:
* The default alternative (do nothing/manual)
* Traditional solutions in the category
* Direct competitors
* DIY substitute tools / free methods
## STEP 2.2: Build a Use-Case Library (10+ Scenarios)
Create 10+ “user scenarios” relevant to any product.
Example universal scenario patterns:
1. Beginners onboarding (first-time user)
2. Budget-conscious user
3. Power users / advanced workflows
4. Teams and collaboration
5. Enterprise compliance / security needs
6. High-frequency usage / scalability
7. Multi-region / multi-platform usage
8. Time-sensitive / emergency need
9. Switching from an incumbent competitor
10. Seasonal or campaign-based usage
11. Integration with other tools
12. Performance optimization / cost reduction
Each scenario must include:
* Pain point
* Product solution
* Supporting data (pricing, ROI, benchmark, time saved, etc.)
---
# PHASE 3: 10-Article Strategy Matrix Generation
Use the selected competitor articles to create a rewrite plan:
```plaintext
| # | Source Topic | New Topic (Product-Aware Angle) | Primary Keyword | Secondary Keywords | Search Intent | Unique Angle | Product Integration Points | EEAT Plan | Word Count |
|---|-------------|----------------------------------|----------------|-------------------|------------|-------------|------------------------|------------|---------|
| 1 | [topic] | [rewritten topic] | [keyword] | [5 keywords] | INFO | [angle] | [2-3 scenarios] | [strategy] | 2000 |
```
Each article must explicitly define:
1. **Topic transformation logic**
Example: “Best Travel Apps” → “Best Travel Apps for [specific product users]”
或 “How to do X” → “How to do X with [product] (with alternatives comparison)”
2. **Unique angle to prevent plagiarism**
* Add product-exclusive data + examples
* Reframe content from the user's perspective
* Add missing scenarios/pain points
* Provide actionable steps/checklists
* Introduce a proprietary framework (eg, “3-layer decision model”)
3. **Product integration points** (2–3 natural placements)
* In the solution section
* In the comparison table
* In user story / case study
* Do NOT hard-sell in intro and conclusion
4. **EEAT plan**
* Experience: real cases, hands-on results
* Expertise: technical explanation, best practices
* Authority: cite credible sources
* Trust: transparent comparisons + limitations
---
# PHASE 4: Batch Writing (10 Articles)
## Anti-Plagiarism Rules
### 🚫 Forbidden
* Direct translation of sentences
* Keeping unique metaphors/phrases from competitor content
* Copying paragraph order and section flow
* Reusing competitor headline phrasing
* Copying competitor private data
### ✅ Mandatory
* Re-think from the product user perspective
* Rebuild structure and order from scratch
* Add product-exclusive proof/data (min 3)
* Add 3+ new scenarios/examples not in source
* Use different headline logic and phrasing
* Provide step-by-step guides/checklists
## Universal WordPress HTML Article Template
（保留你原模板，替換RedEX 為[PRODUCT_NAME]，並把eSIM-specific 語意改成product-aware 語意學）
* `esim-content` → `product-content`
* “eSIM users” → “[product] users” / “users in this category”
* 表格列：RedEX eSIM → `[PRODUCT_NAME]`
> 你原HTML 模板可以直接沿用，僅做變數替換+ 文案語意泛化。
---
# PHASE 5: Built-in QA System (Universal)
After each article, run:
## ✅ Originality (Anti-Plagiarism)
* H2/H3 fully rewritten
* Structure order redesigned
* Adds 3+ new scenarios
* No 5 consecutive words match competitor (except public data)
* Adds ≥3 product-exclusive data points
* Adds ≥2 missing subtopics (H3) not present in competitor
## ✅ EEAT Score (≥85/100)
Same scoring logic as your original（Experience/Expertise/Authority/Trust）
## ✅ Technical SEO Checklist
Same as your original（Title/meta/url/h1/h2/kw density/links/FAQ/table/readability）
## ✅ Product Integration Check
* Product mentions ≤3 times (excluding FAQ)
* Every mention solves a concrete problem
* Includes specific proof/data
* No pushy promotion in intro/conclusion
* Mentions limitations honestly
---
# PHASE 6: Output Format
## Output Strategy Matrix First (For Approval)
```markdown
# Universal SEO Batch Production Strategy
## Selected 10 Competitor Articles
| # | Source Title | Quality Score | Reason |
|---|-------------|--------------|--------|
| 1 | [Title] | 92/100 | [Reason] |
…
## 10-Article Strategy Matrix
[Full table]
## EEAT Implementation Strategy
- Experience: ...
- Expertise: ...
- Authoritativeness: ...
- Trustworthiness: ...
## Originality Safeguards
1. ...
2. ...
---
**Proceed to writing?** (Type "Start writing" or suggest edits)
```
## After Approval: Output 10 Full WordPress HTML Articles + QA Report
(Keep your existing “Article + QA report” packaging exactly.)
描述
推薦自
nene@YouMind
為什麼我們推薦這個技能
這款技能透過分析競爭對手文章庫，智慧生成高品質、符合E-E-A-T原則的SEO文章，並深度整合您的產品特點。它能自動篩選最佳競品內容，避免主題重複，並輸出WordPress友好型HTML，是批量生產專業SEO內容的理想選擇。
這也許可能是最好的SEO文章寫作Skill，透過這個Skill，可以確保您產出的文章符合EEAT框架，不會胡亂編造，需要您提供產品資訊與競品文章。（以下是AI撰寫的詳細介紹） 這項通用SEO批量寫作技能能幫助您將競爭對手的文章庫轉化為10篇針對任何產品或服務的原創、高品質SEO文章：它會自動掃描並評分您目前板塊中的所有文章，篩選出頂級參考資料，避免重複您已發布的主題，構建清晰的10篇文章策略矩陣（包括關鍵字、意圖、獨特視角以及自然提及產品的地方），然後生成可直接用於WordPress的HTML文章，這些文章遵循Google E-E-A-T原則和頁面SEO最佳實務——每篇文章末尾都附帶一份內建的品質評估報告。
相關技能
查看全部
寫作Evergreen Refresh Radar
這個市集中的所有工具都幫你發布新內容，卻沒有任何工具能防止你過去兩年的心血悄悄出錯。 已發布的內容會腐敗。你引用的統計數字已經變了；連結仍然有效，但指向的頁面不再包含原來的說法；你推薦的工具取消了免費方案；「最近」這個詞每存在一天，都在造成傷害。讀者不會就這些問題寫信給你，只會對你的信任悄悄減少。 Evergreen Refresh Radar 會稽核你已經發布的內容，逐一檢查七種衰敗：失效的證據、過時的數字、被取代的事實、錨定時間的語言、失準的預測、脈絡偏移，以及表面腐蝕。它會開啟每個連結，確認引用的說法仍然在頁面上——這是幾乎沒有人檢查的失敗模式，也是讓一篇好文章悄悄變成錯誤文章的原因。 接著它會排序。Refresh ROI 的計算方式是「承受風險的價值」乘以嚴重度，再除以所需心力，並以持久性作為平手時的決定條件，分為「立即修補」「排程處理」「重寫」「退役或重新導向」四類。它也會告訴你哪些內容完全不需要動，因為到處都找出問題的稽核，不算是稽核。 它還會寫好修補內容。原始句子、替換句子、新的來源、新的日期，全部準備好讓你直接貼上，而且會配合周遭段落的句子長度和用詞，讓修正看起來不像疤痕。它會以兩種語氣起草你應該讓讀者看到的更新說明，而且絕不會建議你默默更改實質主張。 它可以作為排程任務每月執行，只回報新出現的衰敗，並持續維護一份衰敗日誌（Decay Log），讓你能隨著時間看到目錄的健康狀況，而不是在某則回覆中才發現問題。 適合部落客、電子報作者、文件負責人、課程創作者、維護客戶網站的代理商，以及任何搜尋流量和信譽都仰賴自己很久以前寫的內容的人。
寫作發布前完整性稽核
市場上的每個生成器都會產出初稿。但幾乎沒有什麼會在你署名發布前檢查它們。 這是介於你的草稿與公眾之間的辦公桌。它不會改善你的文筆。它尋找真正會讓你付出代價的六件事：錯誤的數字、誤引的來源、證據無法支撐的主張、律師會圈起來的句子、使用螢幕閱讀器的人無法看到的圖片，以及去年三月就已失效的連結。 六道檢查。它將每個可核實的陳述提取成編號表格，並逐一對照主要來源驗證，而非次要報導。它檢查數字中的單位和基準錯誤，因為大多錯誤藏在那裡，而不是位數錯誤。它找出每段引文的原始措辭，並報告差異。它搜尋誇大詞彙，因為「第一」、「唯一」和「最大」是任何草稿中風險最高的詞。它標示將相關性寫成因果關係的情況，以及以單一研究支撐普遍主張的論述。它嗅出誹謗風險、未經認證的健康、法律和財務建議、結果承諾，以及未揭露的利益。 接著是無障礙檢查，這是市場上幾乎沒有技能會執行的：缺少替代文字時，它會寫出替代文字；跳過的標題層級；單獨存在時毫無意義的連結文字，並提供替代方案；僅以顏色作為意義的唯一載體；破壞線性閱讀的表格；缺少字幕和逐字稿；以及對照你的發布平台檢查的閱讀難度評估。 所有結果會以 BLOCK、FIX 或 NOTE 標示，並完整寫出替代措辭，附上修正後的草稿。它不會叫你考慮改寫。它直接給你句子。 它也會告訴你哪些部分無法驗證，以及原因。 適用於以自己的名義或公司名義發布的人：記者、電子報作者、分析師、顧問、行銷人員，以及任何沒有專職事實查核員或無障礙審查員的團隊。
寫作亞馬遜文案生成大師
生成、改寫並質檢 Amazon Listing：先完成買家意圖與關鍵字映射，再按標題新規撰寫，最後通過 CDQ、A9、COSMO、Alexa 可見性、合規和標題短語六門質檢循環修訂。
最強通用型SEO文章寫作
指令
# Universal SEO Batch Writing Skill (English Version)
## Skill Overview
This Skill is designed to generate **high-quality, original, EEAT-compliant SEO articles** for **any product or service**, using a competitor article library in the current Board.
It can:
* Automatically select **10 best competitor SEO articles** from the current Board as references
* Intelligently avoid **topic overlap** with your existing articles
* Deeply integrate **your product's unique features, data, and positioning**
* Follow **Google EEAT** principles and pass originality checks
* Run a built-in **Quality Assurance system** to ensure each article meets standards
* Output **WordPress-ready HTML** (copy-paste into WP backend)
---
# Required Inputs (You Provide)
## Input A: Product Information (Required)
Provide a structured product brief including:
* Product name / brand name
* What it is (category + use case)
* Target audience
* Core value proposition (3–5 bullets)
* Key features (5–10 bullets)
* Pricing model (ranges, plans, tiers)
* Coverage / availability (countries, channels, platforms, industries, etc.)
* Proof/data (metrics, user growth, savings, performance, NPS, case studies, testimonials)
* Competitive advantages vs alternatives
* Limitations / constraints / best-fit scenarios (for trustworthiness)
* Internal pages you want to link to (pricing page, product page, blog posts, etc.)
> If not fully provided, the Skill should use `searchBoards` or `googleSearch` to supplement.
## Input B: Competitor SEO Library (Required)
Your current Board should contain competitor SEO articles as materials.
---
# PHASE 1: Competitor Article Intelligence Selection
## STEP 1.1: Scan All Articles in the Board
Actions:
1. Use `listBoard` to retrieve all materials in the current Board
2. Use `read` to read key information from each article (first 500 lines)
3. Extract:
* Topic / keywords
* Content type (Guide / Comparison / 評論 / Tutorial, etc.)
* Word count
* Structure quality (H2/H3 hierarchy, data density, table usage)
* Target audience
* Unique angle
* Search intent (Informational / Commercial / Transactional)
## STEP 1.2: Article Quality Scoring (0–100)
**Content Quality (40)**
* Depth and completeness (15)
* Data/examples richness (10)
* Structural clarity (10)
* Actionability (5)
**SEO Optimization (30)**
* Clear keyword strategy (10)
* Title + structure optimization (10)
* Internal/external links usage (5)
* Readability/UX (5)
**Uniqueness (20)**
* Unique insights, data, framing (10)
* Potential to be rewritten into “product-aware” content (10)
**Fit (10)**
* Ease of integrating product value naturally (10)
## STEP 1.3: Select Top 10 Articles (Balanced Coverage)
Selection rules:
1. Take top 15 by score
2. Filter down to 10 while ensuring:
* Topic diversity (max 2 per broad topic cluster)
* Search intent coverage:
* 3–4 informational
* 4–5 commercial
* 1–2 transactional
* Strong relevance to the product's core use cases
* Natural opportunities to integrate product value
## STEP 1.4: Topic Duplication Check (Avoid Existing Topics)
If the Board already contains articles about your product:
1. Use `searchBoards` with keywords:
* product name, brand name
* category keyword(s)
* primary use-case keyword(s)
2. Extract existing topics and keywords
3. Remove overlapping topics from Top 10
4. Replace with new topics from the candidate pool
**Output:**
**Top 10 competitor article list** + **why they were selected**
---
# PHASE 2: Deep Product Analysis (Generic Template)
## STEP 2.1: Extract Product Core Assets
From product info (or via `searchBoards` / `googleSearch`):
**Positioning**
* What the product is (category + function)
* Core value proposition
* Target users
**Features**
* Key feature set
* Onboarding / setup flow
* Compatibility / requirements
* Support / SLA
* Unique differentiators (features competitors don't have)
**Proof & Data (EEAT critical)**
* Users / growth metrics
* Satisfaction metrics (NPS, rating, churn)
* Performance metrics (speed, uptime, results, ROI)
* Cost-saving % or time-saving metrics
* Case studies / testimonials (at least 2)
**Competitive Landscape**
Compare against:
* The default alternative (do nothing/manual)
* Traditional solutions in the category
* Direct competitors
* DIY substitute tools / free methods
## STEP 2.2: Build a Use-Case Library (10+ Scenarios)
Create 10+ “user scenarios” relevant to any product.
Example universal scenario patterns:
1. Beginners onboarding (first-time user)
2. Budget-conscious user
3. Power users / advanced workflows
4. Teams and collaboration
5. Enterprise compliance / security needs
6. High-frequency usage / scalability
7. Multi-region / multi-platform usage
8. Time-sensitive / emergency need
9. Switching from an incumbent competitor
10. Seasonal or campaign-based usage
11. Integration with other tools
12. Performance optimization / cost reduction
Each scenario must include:
* Pain point
* Product solution
* Supporting data (pricing, ROI, benchmark, time saved, etc.)
---
# PHASE 3: 10-Article Strategy Matrix Generation
Use the selected competitor articles to create a rewrite plan:
```plaintext
| # | Source Topic | New Topic (Product-Aware Angle) | Primary Keyword | Secondary Keywords | Search Intent | Unique Angle | Product Integration Points | EEAT Plan | Word Count |
|---|-------------|----------------------------------|----------------|-------------------|------------|-------------|------------------------|------------|---------|
| 1 | [topic] | [rewritten topic] | [keyword] | [5 keywords] | INFO | [angle] | [2-3 scenarios] | [strategy] | 2000 |
```
Each article must explicitly define:
1. **Topic transformation logic**
Example: “Best Travel Apps” → “Best Travel Apps for [specific product users]”
或 “How to do X” → “How to do X with [product] (with alternatives comparison)”
2. **Unique angle to prevent plagiarism**
* Add product-exclusive data + examples
* Reframe content from the user's perspective
* Add missing scenarios/pain points
* Provide actionable steps/checklists
* Introduce a proprietary framework (eg, “3-layer decision model”)
3. **Product integration points** (2–3 natural placements)
* In the solution section
* In the comparison table
* In user story / case study
* Do NOT hard-sell in intro and conclusion
4. **EEAT plan**
* Experience: real cases, hands-on results
* Expertise: technical explanation, best practices
* Authority: cite credible sources
* Trust: transparent comparisons + limitations
---
# PHASE 4: Batch Writing (10 Articles)
## Anti-Plagiarism Rules
### 🚫 Forbidden
* Direct translation of sentences
* Keeping unique metaphors/phrases from competitor content
* Copying paragraph order and section flow
* Reusing competitor headline phrasing
* Copying competitor private data
### ✅ Mandatory
* Re-think from the product user perspective
* Rebuild structure and order from scratch
* Add product-exclusive proof/data (min 3)
* Add 3+ new scenarios/examples not in source
* Use different headline logic and phrasing
* Provide step-by-step guides/checklists
## Universal WordPress HTML Article Template
（保留你原模板，替換RedEX 為[PRODUCT_NAME]，並把eSIM-specific 語意改成product-aware 語意學）
* `esim-content` → `product-content`
* “eSIM users” → “[product] users” / “users in this category”
* 表格列：RedEX eSIM → `[PRODUCT_NAME]`
> 你原HTML 模板可以直接沿用，僅做變數替換+ 文案語意泛化。
---
# PHASE 5: Built-in QA System (Universal)
After each article, run:
## ✅ Originality (Anti-Plagiarism)
* H2/H3 fully rewritten
* Structure order redesigned
* Adds 3+ new scenarios
* No 5 consecutive words match competitor (except public data)
* Adds ≥3 product-exclusive data points
* Adds ≥2 missing subtopics (H3) not present in competitor
## ✅ EEAT Score (≥85/100)
Same scoring logic as your original（Experience/Expertise/Authority/Trust）
## ✅ Technical SEO Checklist
Same as your original（Title/meta/url/h1/h2/kw density/links/FAQ/table/readability）
## ✅ Product Integration Check
* Product mentions ≤3 times (excluding FAQ)
* Every mention solves a concrete problem
* Includes specific proof/data
* No pushy promotion in intro/conclusion
* Mentions limitations honestly
---
# PHASE 6: Output Format
## Output Strategy Matrix First (For Approval)
```markdown
# Universal SEO Batch Production Strategy
## Selected 10 Competitor Articles
| # | Source Title | Quality Score | Reason |
|---|-------------|--------------|--------|
| 1 | [Title] | 92/100 | [Reason] |
…
## 10-Article Strategy Matrix
[Full table]
## EEAT Implementation Strategy
- Experience: ...
- Expertise: ...
- Authoritativeness: ...
- Trustworthiness: ...
## Originality Safeguards
1. ...
2. ...
---
**Proceed to writing?** (Type "Start writing" or suggest edits)
```
## After Approval: Output 10 Full WordPress HTML Articles + QA Report
(Keep your existing “Article + QA report” packaging exactly.)
描述
推薦自
nene@YouMind
為什麼我們推薦這個技能
這款技能透過分析競爭對手文章庫，智慧生成高品質、符合E-E-A-T原則的SEO文章，並深度整合您的產品特點。它能自動篩選最佳競品內容，避免主題重複，並輸出WordPress友好型HTML，是批量生產專業SEO內容的理想選擇。
這也許可能是最好的SEO文章寫作Skill，透過這個Skill，可以確保您產出的文章符合EEAT框架，不會胡亂編造，需要您提供產品資訊與競品文章。（以下是AI撰寫的詳細介紹） 這項通用SEO批量寫作技能能幫助您將競爭對手的文章庫轉化為10篇針對任何產品或服務的原創、高品質SEO文章：它會自動掃描並評分您目前板塊中的所有文章，篩選出頂級參考資料，避免重複您已發布的主題，構建清晰的10篇文章策略矩陣（包括關鍵字、意圖、獨特視角以及自然提及產品的地方），然後生成可直接用於WordPress的HTML文章，這些文章遵循Google E-E-A-T原則和頁面SEO最佳實務——每篇文章末尾都附帶一份內建的品質評估報告。
相關技能
查看全部寫作Evergreen Refresh Radar
這個市集中的所有工具都幫你發布新內容，卻沒有任何工具能防止你過去兩年的心血悄悄出錯。 已發布的內容會腐敗。你引用的統計數字已經變了；連結仍然有效，但指向的頁面不再包含原來的說法；你推薦的工具取消了免費方案；「最近」這個詞每存在一天，都在造成傷害。讀者不會就這些問題寫信給你，只會對你的信任悄悄減少。 Evergreen Refresh Radar 會稽核你已經發布的內容，逐一檢查七種衰敗：失效的證據、過時的數字、被取代的事實、錨定時間的語言、失準的預測、脈絡偏移，以及表面腐蝕。它會開啟每個連結，確認引用的說法仍然在頁面上——這是幾乎沒有人檢查的失敗模式，也是讓一篇好文章悄悄變成錯誤文章的原因。 接著它會排序。Refresh ROI 的計算方式是「承受風險的價值」乘以嚴重度，再除以所需心力，並以持久性作為平手時的決定條件，分為「立即修補」「排程處理」「重寫」「退役或重新導向」四類。它也會告訴你哪些內容完全不需要動，因為到處都找出問題的稽核，不算是稽核。 它還會寫好修補內容。原始句子、替換句子、新的來源、新的日期，全部準備好讓你直接貼上，而且會配合周遭段落的句子長度和用詞，讓修正看起來不像疤痕。它會以兩種語氣起草你應該讓讀者看到的更新說明，而且絕不會建議你默默更改實質主張。 它可以作為排程任務每月執行，只回報新出現的衰敗，並持續維護一份衰敗日誌（Decay Log），讓你能隨著時間看到目錄的健康狀況，而不是在某則回覆中才發現問題。 適合部落客、電子報作者、文件負責人、課程創作者、維護客戶網站的代理商，以及任何搜尋流量和信譽都仰賴自己很久以前寫的內容的人。
寫作發布前完整性稽核
市場上的每個生成器都會產出初稿。但幾乎沒有什麼會在你署名發布前檢查它們。 這是介於你的草稿與公眾之間的辦公桌。它不會改善你的文筆。它尋找真正會讓你付出代價的六件事：錯誤的數字、誤引的來源、證據無法支撐的主張、律師會圈起來的句子、使用螢幕閱讀器的人無法看到的圖片，以及去年三月就已失效的連結。 六道檢查。它將每個可核實的陳述提取成編號表格，並逐一對照主要來源驗證，而非次要報導。它檢查數字中的單位和基準錯誤，因為大多錯誤藏在那裡，而不是位數錯誤。它找出每段引文的原始措辭，並報告差異。它搜尋誇大詞彙，因為「第一」、「唯一」和「最大」是任何草稿中風險最高的詞。它標示將相關性寫成因果關係的情況，以及以單一研究支撐普遍主張的論述。它嗅出誹謗風險、未經認證的健康、法律和財務建議、結果承諾，以及未揭露的利益。 接著是無障礙檢查，這是市場上幾乎沒有技能會執行的：缺少替代文字時，它會寫出替代文字；跳過的標題層級；單獨存在時毫無意義的連結文字，並提供替代方案；僅以顏色作為意義的唯一載體；破壞線性閱讀的表格；缺少字幕和逐字稿；以及對照你的發布平台檢查的閱讀難度評估。 所有結果會以 BLOCK、FIX 或 NOTE 標示，並完整寫出替代措辭，附上修正後的草稿。它不會叫你考慮改寫。它直接給你句子。 它也會告訴你哪些部分無法驗證，以及原因。 適用於以自己的名義或公司名義發布的人：記者、電子報作者、分析師、顧問、行銷人員，以及任何沒有專職事實查核員或無障礙審查員的團隊。
寫作亞馬遜文案生成大師
生成、改寫並質檢 Amazon Listing：先完成買家意圖與關鍵字映射，再按標題新規撰寫，最後通過 CDQ、A9、COSMO、Alexa 可見性、合規和標題短語六門質檢循環修訂。
發現下一個適合你的技能
繼續探索更多精選 AI 技能，用於研究、創作和日常工作。