avifenesh/content-pipeline
skills/content-pipeline/SKILL.md
Generate content drafts when a PR is merged or significant code ships. Produces a Twitter/X thread, blog post outline, and changelog entry from PR title, changed files, and commit messages. Keywords: content, tweet, blog, changelog, announce, write about, PR merged, shipped, released, draft post, social, thread
$ install --global
skillsauthnpx skillsauth add avifenesh/cairn content-pipelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 12, 2026, 3:10 AM28.3s1 file scanned
SKILL.md
- name:
- content-pipeline
- description:
- Generate content drafts when a PR is merged or significant code ships. Produces a Twitter/X thread, blog post outline, and changelog entry from PR title, changed files, and commit messages. Keywords: content, tweet, blog, changelog, announce, write about, PR merged, shipped, released, draft post, social, thread
- inclusion:
- on-demand
- allowed-tools:
- cairn.shell,cairn.gitRun,cairn.readFile,cairn.searchMemory,cairn.publishToFeed
Content Pipeline
Generates three draft content formats from a merged PR or shipped feature. Run after a significant PR merges or when Avi says "write content for X".
Step 1: Gather Context
Determine the PR or commit to write about. Accept one of:
- A PR number (e.g. "write content for PR #812")
- "latest" — find the most recently merged PR
- A feature description — use it directly as context
If PR number or "latest":
cairn.shell: gh pr view <number> --repo avifenesh/cairn --json title,body,mergedAt,files,commits
or for latest merged:
cairn.shell: gh pr list --repo avifenesh/cairn --state merged --limit 3 --json number,title,mergedAt,files
Collect commit messages for the PR:
cairn.gitRun: log --oneline <base>..<head>
Summarise changed files — group by domain (backend/frontend/config/skill/docs). Skip test files for public copy.
Step 2: Check Tone and Style Preferences
cairn.searchMemory: "writing style tone voice communication"
Look for: writing style hard rules (no emojis, plain tone, direct), preferred framing (technical vs accessible), any past content preferences.
Step 3: Generate the Three Drafts
Output all three in a single response, separated by clear headers.
DRAFT A — Twitter/X Thread (3-5 tweets)
Rules:
- Tweet 1: hook — one sentence that tells what shipped and why it matters
- Tweets 2-4: one concrete detail per tweet (what problem it solved, how it works, what changed for users)
- Tweet 5 (optional): link or call to action
- Each tweet ≤ 280 characters
- No emojis unless Avi's style preferences say otherwise
- Technical specifics welcome (e.g. "SQLite busy_timeout was resetting to 0 on every restart")
Format:
🧵 [1/N] <hook>
[2/N] <detail>
[3/N] <detail>
[4/N] <optional detail>
[5/N] <link/cta if applicable>
DRAFT B — Blog Post Outline
A short outline (not the full post) for a 400-600 word technical post.
Format:
Title: <title>
Subtitle: <one sentence>
Sections:
1. The Problem — <2-3 sentence summary of what was broken/missing>
2. The Approach — <key technical decision and why>
3. Implementation — <2-4 bullet points of what was done>
4. Result — <concrete outcome: what works now that didn't before>
5. What's Next — <optional: follow-on work>
Target audience: <technical / general / builders>
Tone: <matter-of-fact / story-driven / tutorial>
Estimated read time: <N min>
DRAFT C — Changelog Entry
One concise paragraph for CHANGELOG.md or release notes. Style: past tense, factual, no marketing language.
Format:
## [date] — <feature name>
<One paragraph: what changed, what it fixes or enables, any breaking changes or migration notes.>
Wiring Note
How to trigger automatically on PR merge:
There is no pr_merged TaskMilestone in the event bus. The closest hooks are:
TaskMilestone.Milestone == "pr_created"(fires when a coder agent opens a PR)isExtraordinary(result)ininternal/channel/task_summary.go(fires for any task result containing a PR URL or "files changed")
Recommended wiring options (in order of effort):
-
Cron (zero code): Add a daily cron that calls
cairn.loadSkill("content-pipeline")and passes"latest"as context. Generates content for yesterday's most significant merge. Avi reviews in the next morning's digest. -
Orchestrator heuristic (no code): The orchestrator's GATHER phase already reads PR status. Add a DECIDE heuristic: if a PR was merged since the last tick and
isExtraordinary(PR title + body), spawn a content-pipeline worker with the PR number. -
Notification bridge hook (minimal Go): In
notification_bridge.go, whenTaskMilestone.Milestone == "pr_created"fires andisExtraordinary(e.Summary)returns true, also spawncontent-pipelineas a background worker subagent. This is ~10 lines of Go innotification_bridge.go.
Related Skills
avifenesh/pr-stall-detector
data-ai
VerifiedTrustedCommunity
Detect agent-cairn PRs that have stalled (no activity >=90 min) and classify the failure mode to route to appropriate recovery agent.
4SKILL.mdUpdated Apr 12, 2026
avifenesh/installer
tools
VerifiedTrustedCommunity
Post-install skill adaptation: read a newly installed SKILL.md, fix environment-specific references (paths, accounts, tool names), assign the skill to relevant agent types, and propose an AGENTS.md update. Triggered automatically after cairn.installSkill completes.
4SKILL.mdUpdated Apr 12, 2026
avifenesh/growth-brief
data-ai
VerifiedTrustedCommunity
Monthly self-improvement brief for Cairn. Queries error_patterns, action_exemplars, experiment_windows, and session_journal to synthesize what Cairn learned, where it failed, and 3 concrete proposals for Avi to approve. Run on the 1st of each month. Keywords: growth brief, monthly review, self-improvement, what did cairn learn, how is cairn doing, monthly report
4SKILL.mdUpdated Apr 12, 2026
avifenesh/decision-support
testing
VerifiedTrustedCommunity
Decision support with memory-backed context. Retrieves past decisions, journal history, and relevant facts before answering questions that involve a choice or tradeoff. Keywords: should I, which is better, tradeoff, compare, decide, choose, option, alternative, pros and cons, recommend
4SKILL.mdUpdated Apr 12, 2026