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/series-planner/cadence-guidelines.md

View on GitHub
# Publishing Cadence Guidelines

Recommendations for series publication frequency based on content type and goals.

---

## Cadence Options

### Weekly (Recommended Default)

**Schedule:** Same day each week (e.g., every Tuesday)

**Best for:**
- Standard series (3-5 parts)
- Evergreen technical content
- Building sustained audience interest
- Content that benefits from reader feedback between parts

**Advantages:**
- Maintains momentum without overwhelming
- Time to incorporate feedback
- Sustainable writing pace
- Allows promotion between posts

**Example schedule:**
```
Week 1 (Dec 3):  Part 1 - Foundation
Week 2 (Dec 10): Part 2 - Core Implementation
Week 3 (Dec 17): Part 3 - Advanced Topics
Week 4 (Dec 24): Part 4 - Production
```

---

### Bi-Weekly

**Schedule:** Every other week

**Best for:**
- Deep technical content (1500+ words per part)
- Complex topics requiring research
- Part-time content creation
- Audiences that need digestion time

**Advantages:**
- More time for thorough writing
- Complex topics get proper treatment
- Sustainable for side projects
- Reader has time to implement/experiment

**Example schedule:**
```
Dec 3:   Part 1 - Problem Space
Dec 17:  Part 2 - First Approach
Dec 31:  Part 3 - What Went Wrong
Jan 14:  Part 4 - Final Solution
```

---

### Daily (Launch/Event Mode)

**Schedule:** Consecutive days (typically Mon-Fri)

**Best for:**
- Time-sensitive content
- Product/feature launches
- Conference tie-ins
- Short series (3-4 parts max)

**Advantages:**
- Maximum momentum
- Captures full attention
- Good for event-driven content
- Creates urgency

**Disadvantages:**
- No time for feedback incorporation
- Demanding production schedule
- Reader may fall behind

**Example schedule:**
```
Monday:    Part 1 - Announcement
Tuesday:   Part 2 - Getting Started
Wednesday: Part 3 - Deep Dive
Thursday:  Part 4 - Advanced Usage
Friday:    Part 5 - What's Next
```

---

### Staggered

**Schedule:** Part 1, gap, then remaining parts weekly

**Best for:**
- SEO optimization (Part 1 establishes search presence)
- Content calendar balancing
- Testing audience interest before committing

**Pattern:**
```
Week 1:  Part 1
Week 2:  [gap - promote Part 1, gather feedback]
Week 3:  Part 2
Week 4:  Part 3
Week 5:  Part 4
```

**Advantages:**
- Part 1 builds search ranking before series continues
- Gap builds anticipation
- Time to adjust based on Part 1 reception
- Remaining parts maintain momentum

---

## Cadence Selection Criteria

### Choose Weekly When:

- [x] Content is evergreen
- [x] Parts are 800-1200 words each
- [x] You have buffer of completed parts
- [x] Audience expects regular content
- [x] No urgent time constraints

### Choose Bi-Weekly When:

- [x] Parts are 1500+ words each
- [x] Content requires significant research
- [x] Writing is not your primary job
- [x] Topics are complex and dense
- [x] Reader needs implementation time

### Choose Daily When:

- [x] Content is time-sensitive
- [x] Series is short (3-4 parts max)
- [x] All parts are complete before publishing
- [x] You can dedicate full attention to promotion
- [x] Audience will engage daily

### Choose Staggered When:

- [x] SEO is a primary goal
- [x] Testing topic interest
- [x] Balancing with other content
- [x] Part 1 is particularly strong/shareable

---

## Day and Time Considerations

### Best Days for Technical Content

| Day | Effectiveness | Notes |
|-----|---------------|-------|
| Tuesday | Excellent | Early week, past Monday chaos |
| Wednesday | Excellent | Mid-week, high engagement |
| Thursday | Good | Before weekend reading time |
| Monday | Fair | Competing with work catch-up |
| Friday | Fair | Weekend may help or hurt |
| Weekend | Variable | Good for hobbyist audiences |

### Time of Day

- **Morning (8-10am)**: Catches morning reading habits
- **Lunch (12-1pm)**: Lunch break reading
- **Evening (4-6pm)**: End of workday reading

**Recommendation:** Pick a consistent day/time. Consistency matters more than perfect timing.

---

## Managing Series Production

### Buffer Strategy

**Recommendation:** Complete at least Part 1 + 50% of remaining parts before publishing Part 1.

```
Series of 4 parts:
  Before Part 1 publishes:
    Part 1: Complete
    Part 2: Complete
    Part 3: Draft
    Part 4: Outlined
```

**Why:** Reduces pressure, allows revision, handles unexpected delays.

### Feedback Integration

Build in feedback windows:

```
Day 0: Part 1 publishes
Day 1-6: Collect feedback (comments, questions, issues)
Day 7: Part 2 publishes (can address Part 1 feedback)
```

### Publishing Checklist Per Part

Before each part goes live:

- [ ] All links verified (prev/next, external)
- [ ] Cross-references accurate
- [ ] Code examples tested
- [ ] Previous part updated with "Next" link
- [ ] Landing page updated (if manual)
- [ ] Social posts scheduled
- [ ] Email newsletter queued (if applicable)

---

## Handling Delays

### Missing a Scheduled Publication

**Best practice:** Publish late rather than skip.

**Communication:**
```markdown
*[Series note: This part was delayed from our usual Tuesday schedule.
Part 4 returns next Tuesday as scheduled.]*
```

### Extended Delay (1+ weeks)

**Communication on landing page:**
```markdown
**Series Status:** Parts 1-3 complete. Part 4 expected [date].
```

### Abandoning a Series

If you must stop mid-series:

1. Add note to landing page explaining status
2. Update last published part with status
3. Consider: Can you publish what you have as incomplete but still valuable?

```markdown
**Series Status:** This series is on indefinite hold after Part 3.
Parts 1-3 are complete and standalone. Part 4 (Production) may be
added in the future.
```

---

## Series Length vs Cadence

| Parts | Recommended Cadence | Total Duration |
|-------|---------------------|----------------|
| 3 | Weekly or Bi-weekly | 3-6 weeks |
| 4 | Weekly | 4 weeks |
| 5 | Weekly or Staggered | 5-7 weeks |
| 6 | Weekly or Bi-weekly | 6-12 weeks |
| 7 | Bi-weekly | 14 weeks |

**Guideline:** Series duration should not exceed 3 months for reader engagement.

---

## Promotion Between Parts

### Inter-Part Promotion

Between publications:
- Share individual insights from upcoming parts
- Ask questions the next part will answer
- Highlight comments/feedback from previous parts

### Series Completion Promotion

When final part publishes:
- Announce series completion
- Share landing page as comprehensive resource
- Consider: Summary post linking all parts

---

## Audience Considerations

### Technical Professionals

- Weekly works well (aligned with work week)
- Bi-weekly for very complex topics
- Prefer schedules that include weekdays so the cadence reaches readers when they are most active

### Hobbyists/Learners

- Weekly or bi-weekly both work
- Weekend publishing can be effective
- Consider: Time needed to work through exercises

### Mixed Audience

- Default to weekly
- Provide clear "level" indicators per part
- Allow readers to skip to relevant depth
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