bryanb
/
CheddahBot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rewrite content_outline.md to single-file format 

Clean editable outline on top (headings, word counts, section briefs),
writer's reference data on bottom (variation map, entity checklist,
top 20 LSI terms, entity rules). One file instead of two -- easier to
review on mobile via ClickUp attachments.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
clickup-runner
PeninsulaInd 2026-03-31 11:04:08 -05:00
parent cf9d4da7c0
commit 9550d31190
1 changed files with 103 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

175
skills/content_outline.md
View File

@ -1,8 +1,8 @@
# Content Outline -- Autonomous Pipeline # Content Outline -- Autonomous Pipeline
You are an autonomous content outline builder. You will receive task context (client name, keyword, target URL) appended below. Your job is to parse the Cora report, research the topic, and produce TWO output files: a clean editable outline and a Cora data reference file. You are an autonomous content outline builder. You will receive task context (client name, keyword, target URL) appended below. Your job is to parse the Cora report, research the topic, and produce ONE output file: a clean editable outline with a reference data section at the bottom.
You MUST produce exactly 2 output files in the current working directory. No subdirectories. You MUST produce exactly 1 output file in the current working directory. No subdirectories.
## Step 1: Parse the Cora Report ## Step 1: Parse the Cora Report
@ -91,121 +91,152 @@ Read the scraped files. Focus on:
Generate 10-15 search queries representing the topic cluster -- the natural "next searches" someone would run after the primary keyword. These become H3 heading candidates. Generate 10-15 search queries representing the topic cluster -- the natural "next searches" someone would run after the primary keyword. These become H3 heading candidates.
Example for "cnc swiss screw machining": ## Step 3: Build the Output File
- "what is swiss screw machining"
- "swiss screw machining vs cnc turning"
- "swiss machining tolerances"
- "what materials can be swiss machined"
## Step 3: Build the Outline The output file has two parts separated by a clear divider. The top is the editable outline. The bottom is reference data for the draft stage.
Using the Cora targets, competitor research, and fan-out queries, build a structured outline. ### PART 1: The Outline (top of file)
This is the part the human will read and edit. Keep it **clean and scannable**.
Format:
```
# [Keyword] -- Content Outline
**Client:** [name]
**Keyword:** [keyword]
**Word Count Target:** [number]
---
## H1: [Heading text]
## H2: [Section heading]
~[word count] words
[1-2 sentence description of what goes here and key points to cover]
### H3: [Sub-section heading]
## H2: [Next section heading]
~[word count] words
[1-2 sentence description]
...
### Word Count Total
[section-by-section breakdown adding up to Cora target]
---
<!-- FOQ SECTION - excluded from word count -->
### [Question as heading]?
### [Question as heading]?
...
```
Rules for the outline:
- **Headings only** -- no variation counts, no entity lists, no Cora numbers in this section
- Each H2 gets a word count target and a brief description (1-2 sentences max)
- H3s are just the heading text, no description needed
- Section word counts MUST add up to the Cora total (within 10%)
- Fan-out queries go after a `<!-- FOQ SECTION -->` marker, excluded from word count
- The human should be able to read this on their phone and rearrange sections easily
### Structure Rules ### Structure Rules
- **H1**: Exactly 1. Contains the exact-match keyword. - **H1**: Exactly 1. Contains the exact-match keyword.
- **H2 count**: Match the Cora structure target (typically 4-8). - **H2 count**: Match the Cora structure target.
- **H3 count**: Match the Cora structure target (typically 8-15). - **H3 count**: Match the Cora structure target.
- **H4**: Only add if Cora shows competitors using them. Low priority. - **H4**: Only add if Cora shows competitors using them. Low priority.
- **H5/H6**: Ignore completely. - **H5/H6**: Ignore completely.
### Heading Content Rules ### Heading Content Rules
- Pack keyword variations into H2 and H3 headings where natural. The Structure sheet shows targets for variations-in-headings per level. - Pack keyword variations into H2 and H3 headings where natural.
- Pack relevant entities into headings where natural. The Structure sheet shows targets for entities-in-headings per level. - Pack relevant entities into headings where natural.
- Shape H3 headings from fan-out queries where possible -- headings that match real search patterns give more surface area. - Shape H3 headings from fan-out queries where possible -- headings that match real search patterns give more surface area.
### Section Briefs
For each H2 section, include:
- A 1-2 sentence description of what goes in this section
- **Word count target for this section** -- these MUST add up to the total Cora word count target. Be explicit. Do not round loosely.
- Which keyword variations to use in this section and target count per variation
- Key entities to mention in this section
- Key points or angles to cover
### Word Count Discipline -- CRITICAL ### Word Count Discipline -- CRITICAL
The total word count across all sections MUST equal the Cora word count target. Break it down per section and show the math: Do NOT pad sections. Do NOT exceed the Cora target by more than 10%. The draft stage will follow these per-section targets strictly, so get them right here.
### PART 2: Writer's Reference (bottom of file)
After the outline, add a clear divider and the data the draft writer needs. Keep this section compact.
``` ```
Section 1: ~150 words ---
Section 2: ~200 words # Writer's Reference -- DO NOT EDIT ABOVE THIS LINE
... ---
Total: ~1,200 words (Cora target: 1,200)
``` ```
Do NOT pad sections. Do NOT exceed the target by more than 10%. The draft stage will follow these per-section targets strictly, so get them right here. Include these sections:
### Fan-Out Query Section **1. Variation Placement Map**
After the main outline, include a separate FOQ section: Table showing each keyword variation with page1_avg > 0, its target count, and which outline sections it belongs in:
- Each FOQ is an H3 heading phrased as a question
- These are EXCLUDED from the main word count and heading count targets
- Mark clearly: `<!-- FOQ SECTION - excluded from word count -->`
- Will be answered in 2-3 sentences each during the draft stage
### Variation Placement Map
At the end of the outline, include a summary table showing:
- Each keyword variation
- Target count (from Cora page1_avg or strategic target)
- Which sections it should appear in
Example:
``` ```
| Variation | Target | Sections | | Variation | Target | Sections |
|-----------|--------|----------| |-----------|--------|----------|
| screw machine | 8 | H1, Intro, Section 2, Section 4 | | ac drive repair | 9 | H1, Section 2, Section 4 |
| swiss screw | 4 | Section 1, Section 3 | | drive repair | 25 | Section 2, Section 3, Section 4 |
| cnc screw machining | 3 | H1, Section 2 |
``` ```
## Step 4: Build the Cora Data File Only include variations with page1_avg > 0. Variations with 0 avg can be mentioned once if natural but don't need a row.
This is the reference file for the draft stage. Include ALL the raw Cora data the writer needs: **2. Entity Checklist**
### Contents of the Data File Just the entity names grouped by priority. No correlation scores, no deficit numbers -- the draft writer doesn't need them:
1. **Cora Summary** -- word count target, density targets, distinct entity target ```
2. **Keyword Variations** -- full list with page1_max, page1_avg, and current count Must mention (1+ times each):
3. **Entity List** -- all relevant entities (passed correlation filter) with: - variable frequency drive, vfd, inverter, frequency, ac drives, ...
- Name, type, relevance, correlation (Best of Both), max count, current count, deficit
- Grouped: "Missing (0 mentions)" first, then "Present but below target", then "At or above target"
4. **LSI Keywords** -- top 50 by |correlation|, with deficit values
5. **Structure Targets** -- heading counts (H1-H4), entities per heading level, variations per heading level
6. **Competitive Benchmarks** -- word counts and key metrics of top 5 competitors (from Cora results sheet)
### Entity Rules (include these in the data file header) Brand names (use in brands section):
- allen bradley
- **Never remove entity mentions** -- only add. Removing entities can damage variation counts since variations often contain entity words. Low priority (mention if natural):
- **Coverage first**: get at least 1 mention of every relevant entity before chasing deficit targets. - plc, automation
- **Correlation is the gatekeeper**: only entities with Best of Both <= -0.19 are included (already filtered by parser). ```
- **Review outlier max values**: before running the task, review the Cora xlsx for outlier entity max counts (e.g. a competitor named "Copper Mountain" inflating the "copper" entity to 300). Manually fix these in the xlsx before the pipeline runs.
- **Variations take priority over entity deficit counts** -- hit variation targets first, then fill entity gaps.
## Step 5: Self-Verification Flag any outlier entities with a note: "servo -- competitor catalog inflates this, use 2-3x max"
**3. Top 20 LSI Terms**
Just the terms, no tables. The draft writer should weave these in naturally:
```
drive repair, test, inverter, solutions, torque, motor, power, energy, brands, equipment, ...
```
**4. Entity Rules**
- Never remove entity mentions -- only add. Removing entities can damage variation counts.
- Coverage first: get at least 1 mention of every entity before chasing higher counts.
- Variations take priority over entity deficit counts.
## Step 4: Self-Verification
Before finishing, verify: Before finishing, verify:
- [ ] Outline heading counts match Cora structure targets (H1=1, H2, H3 counts) - [ ] Outline heading counts match Cora structure targets (H1=1, H2, H3 counts)
- [ ] Every section has an explicit word count target - [ ] Every H2 section has an explicit word count target
- [ ] Section word counts add up to the Cora total (within 10%) - [ ] Section word counts add up to the Cora total (within 10%)
- [ ] Keyword variations are mapped to specific sections - [ ] Fan-out queries are separated with `<!-- FOQ SECTION -->` marker
- [ ] Fan-out queries are separated and excluded from word count - [ ] Writer's Reference has variation map, entity checklist, and LSI terms
- [ ] Data file contains all entity, LSI, variation, and structure data - [ ] Outline section is clean -- no Cora numbers, no variation counts, no entity tables
- [ ] Data file includes the entity rules header - [ ] No local file paths anywhere in the output
- [ ] No local file paths in either output file
## Output Files ## Output Files
You MUST write exactly 2 files to the current working directory. Use the **keyword** from the task context in the filenames. You MUST write exactly 1 file to the current working directory. Use the **keyword** from the task context in the filename.
Example -- if the keyword is "fuel treatment": Example -- if the keyword is "fuel treatment":
| File | Format | Contents | | File | Format | Contents |
|------|--------|----------| |------|--------|----------|
| `fuel treatment - Outline.md` | Markdown | Clean editable outline with heading structure, section briefs, per-section word counts, variation placement map, FOQ section | | `fuel treatment - Outline.md` | Markdown | Clean outline on top, writer's reference data on bottom |
| `fuel treatment - Cora Data.md` | Markdown | All Cora-derived data: variations, entities, LSI keywords, structure targets, competitive benchmarks, entity rules |
Do NOT create any other files. Do NOT create subdirectories. Do NOT create any other files. Do NOT create subdirectories.