journal-to-post
Convert personal journal entries into shareable social media posts
Best use case
journal-to-post is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Convert personal journal entries into shareable social media posts
Teams using journal-to-post should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/journal-to-post/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How journal-to-post Compares
| Feature / Agent | journal-to-post | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Convert personal journal entries into shareable social media posts
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Journal to Post Convert personal reflections, journal entries, or voice notes into shareable social media posts. ## Usage ``` /journal-to-post [journal text or file path] ``` ## How It Works 1. **Input:** Provide journal text directly or a file path 2. **Process:** Extract universal insights from personal experience 3. **Output:** 1-3 polished posts ready to share ## Voice Guidelines ### Do - Direct, confident, no hedging - First person when sharing experience - Punchy hooks that challenge assumptions - Specific details that add credibility (numbers, timeframes) ### Don't - Include too personal/private details - Write vague platitudes - Use "I learned that..." framing (show, don't tell) - Sound like typical self-help content ## What Gets Extracted - Universal insights from personal experience - Counterintuitive observations - Patterns you've noticed - Specific data points that anchor the insight ## Transformation Examples ### Example 1 **Journal:** > "Noticed my energy dropped after that difficult meeting. Took 3 hours of walking before I felt normal again." **Post:** > "Your body keeps score of difficult conversations. My energy tanked after one meeting yesterday. Took 3 hours of walking to recover. Most people ignore this and wonder why they're exhausted by Friday." --- ### Example 2 **Journal:** > "Had a breakthrough in meditation today - realized I've been trying to 'achieve' stillness instead of just noticing what's already there." **Post:** > "The meditation trap: trying to achieve stillness. The shift: noticing stillness is already there, underneath the noise. Took me 2 years to stop efforting." --- ### Example 3 **Journal:** > "Spent 4 hours debugging something that turned out to be a typo. Frustrated but also funny in hindsight." **Post:** > "4 hours debugging. The fix? A typo. One character. This is the job. The gap between 'stuck' and 'solved' is often embarrassingly small." ## Output For each generated post: 1. **Show the post** - Ready to copy/paste 2. **Explain the transformation** - What was extracted, what was removed 3. **Offer variations** - Different angles or platforms (X vs LinkedIn) ## Tips for Better Results - Include specific numbers and timeframes in your journal - Note your emotional state, not just events - Capture the "aha moment" or shift in thinking - Don't self-censor in the journal - the skill will filter for you
Related Skills
pinch-to-post
WordPress automation for Clawdbot. Manage posts, pages, WooCommerce products, orders, inventory, comments, SEO (Yoast/RankMath), media via REST API or WP-CLI. Multi-site support, bulk operations, content health checks, markdown to Gutenberg, social cross-posting. 50+ features—just ask.
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".
polymarket-2
Query Polymarket prediction markets - check odds, trending markets, search events, track prices.