Archive Newsletter Guidelines
Human-readable reference for the /archive-newsletter skill. The skill file at .claude/skills/archive-newsletter/SKILL.md contains the full execution steps.
Purpose
Section titled “Purpose”Backfill past Baseworks newsletters into the vault so we can:
- Reference past content when writing new campaigns
- Repurpose sections into future newsletters/blogs/social posts
- Preserve historical editorial record (voice evolution, topic coverage)
- Cross-reference press features, events, and campaigns that were promoted via newsletter
What Gets Archived
Section titled “What Gets Archived”Only textual content. The old template HTML, CSS, and design layouts from FluentCRM or Ontraport are discarded — they reflect design patterns we’ve since moved past and aren’t useful source material.
Images are migrated to the Backblaze B2 CDN at media.baseworks.com/newsletters/<slug>/ so they remain accessible after any source archive URL expires.
When to Use
Section titled “When to Use”- Periodically working through the Drive Inventory: Newsletters to backfill past issues
- When a current campaign references an older newsletter that should be preserved for context
- When Patrick or Asia recall a past newsletter worth pulling in for continuity
When NOT to Use
Section titled “When NOT to Use”- For active newsletter drafting — use
/create-newsletterinstead - For blog post archival — use
/archive-blog-post(pulls from live baseworks.com, not FluentCRM) - For social post archival — currently handled via campaign note updates; a dedicated social archive skill may come later
Cross-Linking Requirements
Section titled “Cross-Linking Requirements”The skill is required to:
- Find related content in the vault before writing (via
vault-index.dbquery + targeted folder checks) - Propose correlations to the user for approval — not silently apply
- Add bidirectional wikilinks — update every correlated file’s
## Relatedsection to point back - Update indexes —
_newsletter-index.md+drive-inventory-newsletters.md
Archives that aren’t cross-linked are dead content. The skill enforces this step.
Output Location
Section titled “Output Location”02-areas/communications/newsletters/YYYY-MM-DD-slug/YYYY-MM-DD-slug.md
Filename prefix is the send date. Slug comes from the subject line (~6 words, kebab-case).
Frontmatter Markers
Section titled “Frontmatter Markers”Every archived newsletter carries:
status: archivedsource: fluentcrm-archivesource-url:(the original FluentCRM URL)image-migration:(list of original → CDN URL mappings)
These markers distinguish archives from active-workflow newsletters and preserve provenance.