Skip to content

notque/vexjoy-agent / skills/content/content

content

Unverified

Content operations: editorial calendar, marketing, publishing, social media management.

FileKindSize
SKILL.mdskill md11.5 KB
references/at-protocol-api.mdmarkdown7.6 KB
references/at-protocol-preferred-patterns.mdmarkdown8.5 KB
references/batch-edit-examples.mdmarkdown6.9 KB
references/batch-edit-operation-types.mdmarkdown7.0 KB
references/batch-edit-regex-patterns.mdmarkdown5.4 KB
references/batch-edit-safety-checklist.mdmarkdown6.0 KB
references/batch-edit.mdmarkdown9.9 KB
references/calendar-format.mdmarkdown3.5 KB
references/campaign-planning.mdmarkdown17.5 KB
references/classification-prompt.mdmarkdown5.9 KB
references/content-engine.mdmarkdown8.7 KB
references/content-engine/error-handling.mdmarkdown7.8 KB
references/content-engine/phase-playbook.mdmarkdown8.3 KB
references/content-engine/platform-specs.mdmarkdown10.9 KB
references/content-strategy.mdmarkdown14.5 KB
references/email-sequences.mdmarkdown15.8 KB
references/error-handling.mdmarkdown8.2 KB
references/headlines.mdmarkdown5.9 KB
references/image-audit-alt-text-examples.mdmarkdown6.8 KB
references/image-audit-format-selection.mdmarkdown5.8 KB
references/image-audit-report-templates.mdmarkdown3.8 KB
references/image-audit-size-guidelines.mdmarkdown4.2 KB
references/image-audit.mdmarkdown10.4 KB
references/link-audit-false-positives.mdmarkdown4.1 KB
references/link-audit-fix-strategies.mdmarkdown7.1 KB
references/link-audit-graph-metrics.mdmarkdown5.0 KB
references/link-audit.mdmarkdown7.8 KB
references/llm-marketing-failure-modes.mdmarkdown18.7 KB
references/marketing.mdmarkdown20.4 KB
references/metrics.mdmarkdown7.4 KB
references/news-collection.mdmarkdown5.2 KB
references/operations.mdmarkdown5.8 KB
references/outline-examples.mdmarkdown11.2 KB
references/outline-structure-templates.mdmarkdown6.4 KB
references/outline.mdmarkdown8.9 KB
references/pagespeed-insights.mdmarkdown10.4 KB
references/pipeline-stages.mdmarkdown3.3 KB
references/pre-publish-checklist.mdmarkdown7.4 KB
references/pre-publish-hugo-frontmatter.mdmarkdown5.3 KB
references/pre-publish-seo-guidelines.mdmarkdown4.1 KB
references/pre-publish.mdmarkdown10.8 KB
references/reddit-moderate.mdmarkdown7.9 KB
references/script-commands.mdmarkdown3.7 KB
references/seo-audit.mdmarkdown16.4 KB
references/seo-guidelines.mdmarkdown5.5 KB
references/seo-keyword-placement.mdmarkdown6.0 KB
references/seo-title-patterns.mdmarkdown5.6 KB
references/seo.mdmarkdown8.9 KB
references/series-planner.mdmarkdown11.7 KB
references/series-planner/cadence-guidelines.mdmarkdown6.8 KB
references/series-planner/cross-linking.mdmarkdown7.2 KB
references/series-planner/output-format.mdmarkdown3.8 KB
references/series-planner/series-types.mdmarkdown7.6 KB
references/taxonomy-audit-report-format.mdmarkdown3.2 KB
references/taxonomy-consolidation-rules.mdmarkdown6.7 KB
references/taxonomy-examples.mdmarkdown9.7 KB
references/taxonomy-guidelines.mdmarkdown5.5 KB
references/taxonomy.mdmarkdown9.0 KB
references/topic-brainstormer.mdmarkdown10.1 KB
references/topic-brainstormer/content-filter.mdmarkdown7.1 KB
references/topic-brainstormer/priority-scoring.mdmarkdown8.1 KB
references/topic-brainstormer/topic-sources.mdmarkdown7.6 KB
references/wordpress-upload.mdmarkdown11.2 KB
references/x-api.mdmarkdown7.8 KB
scripts/publish/link_scanner.pyscript21.4 KB
scripts/publish/pagespeed.pyscript15.3 KB
scripts/publish/tests/test_load_env_file.pyscript3.8 KB
scripts/publish/tests/test_wordpress_inline_urls.pyscript4.4 KB
scripts/publish/tests/test_wordpress_media_upload.pyscript1.5 KB
scripts/publish/tests/test_wordpress_scraper.pyscript4.1 KB
scripts/publish/wordpress-edit-post.pyscript21.2 KB
scripts/publish/wordpress-media-upload.pyscript8.7 KB
scripts/publish/wordpress-scraper.pyscript23.4 KB
scripts/publish/wordpress-upload.pyscript44.2 KB
scripts/reddit-moderate/reddit-automod-cron.shscript3.9 KB
scripts/reddit-moderate/reddit-mod.pyscript83.0 KB
scripts/reddit-moderate/tests/test_reddit_mod.pyscript31.3 KB

references/seo-keyword-placement.md

View on GitHub
# Keyword Placement Reference

## Priority Locations

### 1. Title Tag (Critical)
**Weight**: Highest
**Recommendation**: Include primary keyword, preferably front-loaded

**Good Examples**:
```
"Hugo Debugging: How to Fix Common Template Errors"
 ^^^^^^^^^^^^^^^  <- Primary keyword at start

"Fix Hugo Build Errors: A Practical Debugging Guide"
     ^^^^^ <- Keyword variation near start
```

**Bad Examples**:
```
"A Comprehensive Guide to Various Techniques for Hugo Debugging"
                                                 ^^^^^^^^^^^^^^^
                                                 <- Keyword buried at end

"My Journey Through Template Problems"
  <- No keyword at all
```

### 2. First Paragraph (High)
**Weight**: High
**Recommendation**: Primary keyword within first 100 words, ideally first 2 sentences

**Good Example**:
```markdown
Hugo debugging can be frustrating when error messages don't clearly
point to the problem. This guide covers practical techniques for
tracking down template errors, build failures, and content issues.
```

**Bad Example**:
```markdown
When I started building static sites, I encountered many challenges.
The learning curve was steep. Eventually, after much trial and error,
I found some useful approaches that helped me understand what was
happening when things went wrong with my templates.
[... 150 words later ...]
Hugo debugging is what this post covers.
```

### 3. H2 Headers (Medium)
**Weight**: Medium
**Recommendation**: 2-3 H2s should contain keyword or variations

**Good Structure**:
```markdown
## Common Hugo Debugging Scenarios        <- Contains keyword
## Template Error Messages Explained       <- Related topic
## Debugging Hugo Partial Templates        <- Keyword variation
## Build-Time vs Runtime Errors            <- Topic without keyword (fine)
## Debugging Tools and Techniques          <- Partial keyword
```

**Bad Structure**:
```markdown
## Introduction                            <- Generic
## The Problem                             <- Generic
## My Approach                             <- Generic
## What I Learned                          <- Generic
## Conclusion                              <- Generic
```

### 4. URL Slug (Medium)
**Weight**: Medium
**Recommendation**: Include primary keyword in filename

**Good**:
```
content/posts/2024-12-hugo-debugging.md
                     ^^^^^^^^^^^^^^^ <- Keyword in slug
```

**Acceptable**:
```
content/posts/2024-12-debugging-hugo-templates.md
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <- Variation
```

**Bad**:
```
content/posts/2024-12-my-experience.md
                     ^^^^^^^^^^^^^^ <- No keyword
```

### 5. Body Content (Medium)
**Weight**: Medium
**Recommendation**: Natural usage throughout, 1-2% density

**Natural Placement Opportunities**:
- When introducing new sections
- When referencing the topic directly
- In code comments
- In image alt text
- In concluding summaries

**Prefer**:
- Forcing keywords into unrelated sentences
- Repeating exact phrase when variation is more natural
- Breaking sentence flow for keyword insertion

### 6. Image Alt Text (Low-Medium)
**Weight**: Low-Medium (helps with image search)
**Recommendation**: Describe image, include keyword if relevant

**Good**:
```markdown
![Hugo debugging output showing template error](image.png)
```

**Bad** (keyword stuffing):
```markdown
![Hugo debugging hugo debug hugo template debugging](image.png)
```

**Bad** (no description):
```markdown
![Screenshot](image.png)
```

---

## Keyword Variations

### Why Variations Matter
Search engines understand semantic relationships. Using variations:
- Keeps keyword usage natural
- Sounds natural to readers
- Captures related search queries

### Example Variation Set
**Primary Keyword**: "hugo debugging"

**Variations**:
- "debug Hugo sites"
- "debugging Hugo templates"
- "Hugo troubleshooting"
- "fix Hugo errors"
- "Hugo build problems"
- "template debugging in Hugo"

### When to Use Variations
- When exact keyword sounds awkward
- When discussing specific aspects (templates, builds, etc.)
- When the context is clear
- In headers after primary keyword is established

---

## Keyword Cannibalization

### What It Is
Multiple posts targeting the same primary keyword compete with each other in search results.

### Keep Primary Keywords Distinct
- Each post should target unique primary keyword
- Related posts can share secondary keywords
- Use internal links to establish hierarchy

### Example Problem
```
Post 1: "Hugo Debugging Guide" (keyword: hugo debugging)
Post 2: "Hugo Debugging Tips" (keyword: hugo debugging)
Post 3: "Advanced Hugo Debugging" (keyword: hugo debugging)
         ^^^ All competing for same term
```

### Example Solution
```
Post 1: "Hugo Template Debugging" (keyword: hugo template debugging)
Post 2: "Hugo Build Error Fixes" (keyword: hugo build errors)
Post 3: "Hugo Performance Debugging" (keyword: hugo performance)
         ^^^ Each targets distinct long-tail keyword
```

---

## Placement Checklist

Before publishing, verify:

| Location | Check |
|----------|-------|
| Title | Contains primary keyword? |
| Title | Keyword front-loaded (first half)? |
| URL | Contains keyword or variation? |
| First paragraph | Keyword in first 100 words? |
| H2 headers | 2-3 contain keyword/variations? |
| Body | Natural usage (1-2% density)? |
| Meta description | Contains primary keyword? |
| Image alt | Relevant images described with keyword? |

---

## Technical Content Specifics

### Error Messages as Keywords
Technical readers often search for exact error messages:
```markdown
## "template not found" Error

When Hugo reports `template "layouts/..." not found`, the issue is...
```

This captures searches for the exact error.

### Version-Specific Keywords
Include versions when relevant:
```markdown
## Hugo 0.120+ Debugging Changes

In Hugo 0.120, the debugging output format changed...
```

### Command/Code Keywords
Include actual commands people might search:
```markdown
## Using `hugo --debug`

The `--debug` flag enables verbose output...
```

This captures searches for "hugo --debug" and "hugo debug flag".
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall