القائمة
Generate ready-to-paste social media content for any blog post across multiple platforms (Twitter/X, LinkedIn, Hacker News, dev.to, Reddit, Facebook). Use proactively when promoting blog posts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | promote-post |
| description | Generate ready-to-paste social media content for any blog post across multiple platforms (Twitter/X, LinkedIn, Hacker News, dev.to, Reddit, Facebook). Use proactively when promoting blog posts. |
| disable-model-invocation | false |
| allowed-tools | Read, Glob, Grep |
| model | sonnet |
| argument-hint | <slug> [--platforms x,linkedin,hn,devto,reddit,facebook] [--lang en|es] |
| tier | 2 |
| intent | create |
| max-files | 0 |
| max-loc | 0 |
Generate ready-to-paste social media content for a specific blog post, tailored to each platform's tone, format, and audience. The output is text that the user can copy and paste directly into each platform — no files are created or modified.
Tier: 2 - Standard
Reasoning: Requires reading and understanding blog post content, then generating high-quality creative text adapted to multiple platform formats. No code changes, no risk, but needs good reasoning for platform-specific adaptation.
$SLUG: Blog post slug or URL. Accepts any of these formats:
how-we-got-into-y-combinatorhttp://localhost:4444/blog/how-we-got-into-y-combinator/ or http://localhost:4444/es/blog/how-we-got-into-y-combinator/https://xergioalex.com/blog/how-we-got-into-y-combinator/ or https://xergioalex.com/es/blog/how-we-got-into-y-combinator/$PLATFORMS: Comma-separated list of platforms (default: x,linkedin — Tier 1 platforms)
x, linkedin, hn, devto, reddit, facebook, allall = all 6 platformsx,linkedin), Tier 2 (hn,devto,reddit), Tier 3 (facebook)$LANG: Language for the generated content (default: en). Use en or es.Before running this skill, ensure:
src/content/blog/{lang}/ (matching the slug)_demo/ folder)Parse input — detect if $SLUG is a URL or a plain slug:
http(s)://.*/blog/{slug}/ → extract the slug from the URL path/es/blog/ → auto-set $LANG to es (unless explicitly overridden)/blog/ without /es/ → auto-set $LANG to enSearch for the post file using the extracted slug:
Glob: src/content/blog/{lang}/*_{slug}.{md,mdx}
$LANG is en, search in en/. If es, search in es/.Read the full post content — frontmatter (title, description, tags, pubDate, heroImage) and body.
Identify post characteristics:
tags array (cross-reference with src/content/tags/ for tier)$PLATFORMS not specified, default to Tier 1: x,linkedinall, generate for all 6 platformsPlatform selection guidance based on post tags:
tech, web-development, javascript, ai, devops, python → suggest devto, redditportfolio, dailybot, talks → suggest linkedinhnx, linkedinGenerate content for each requested platform following these formats:
Format: 3-5 tweet thread (each tweet ≤ 280 characters)
Structure:
Tone: Conversational, first-person, direct. Like talking to a friend who's also a developer.
Rules:
Format: Single post, 150-300 words
Structure:
Tone: Professional but personal. Storytelling format. "Here's what I learned..." or "We did X and here's what happened..."
Rules:
Format: Title only (+ optional first comment)
Structure:
Tone: Understated, technical, matter-of-fact. HN audience is skeptical of hype.
Rules:
Format: Frontmatter + adapted intro (first 3-4 paragraphs)
Structure:
---
title: "{post title}"
published: true
description: "{post description}"
tags: {up to 4 dev.to tags, comma-separated}
canonical_url: https://xergioalex.com/blog/{slug}/
cover_image: https://xergioalex.com{heroImage path}
---
{Adapted intro — first 3-4 paragraphs of the post, slightly rewritten to work standalone on dev.to}
---
*This post was originally published on [my blog](https://xergioalex.com/blog/{slug}/). Read the full version there for the complete experience.*
Tone: Same as the blog post — first person, technical, conversational.
Rules:
canonical_url is MANDATORY — prevents SEO competition with the originaljavascript, webdev, ai, productivity, startup)Format: Title + body text for a relevant subreddit
Structure:
Tone: Casual, community-oriented. "Hey, I wrote about X and wanted to share..." Not promotional.
Rules:
Format: Short post for tech/developer groups
Structure:
Tone: Casual, friendly, community-oriented. Like sharing with colleagues.
Rules:
Present all generated content in a clear, structured format:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📣 Social Media Content: {Post Title}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Post: {title}
URL: https://xergioalex.com/blog/{slug}/
Tags: {tags}
Language: {lang}
Platforms: {list}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🐦 TWITTER/X THREAD
━━━━━━━━━━━━━━━━━━━
[Tweet 1]
{content}
[Tweet 2]
{content}
...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
💼 LINKEDIN
━━━━━━━━━━
{full post content}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{... more platforms ...}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ Content generated for {N} platforms
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
❌ Post not found: {slug}
Available posts matching "{partial}":
- {suggestion 1}
- {suggestion 2}
Usage: /promote-post <slug> [--platforms x,linkedin,hn,devto,reddit,facebook]
src/content/blog/, src/content/tags/ (read-only)Before generating content:
canonical_url is included in dev.to outputStop immediately and report if:
_demo/ folder)This skill is complete when ALL of the following are true:
canonical_urlEscalate to user if:
Escalation Path:
Context: User wants to promote their YC story post.
Input:
/promote-post how-we-got-into-y-combinator
Execution: Reads the post, generates content for Twitter/X and LinkedIn (default Tier 1 platforms).
Output:
📣 Social Media Content: How We Got Into Y Combinator
Platforms: x, linkedin
🐦 TWITTER/X THREAD
[Tweet 1]
🧵 Getting into Y Combinator changed everything for DailyBot.
But the application process? Way more intense than I expected.
Here's what actually happened:
[Tweet 2]
We applied 3 times before getting in.
The first two rejections taught us more than the acceptance did — we learned to focus on metrics that matter, not features that impress.
[Tweet 3]
The YC interview is 10 minutes.
10 minutes to convince some of the smartest people in tech that your startup is worth betting on.
Here's what they actually asked us...
[Tweet 4]
Full story on my blog — every detail from application to Demo Day:
https://xergioalex.com/blog/how-we-got-into-y-combinator/
#YCombinator #startups #SaaS
💼 LINKEDIN
Getting into Y Combinator changed the trajectory of DailyBot.
But here's what nobody tells you...
{...}
Context: User wants full coverage in Spanish.
Input:
/promote-post how-we-got-into-y-combinator --platforms all --lang es
Execution: Reads the ES version of the post, generates content for all 6 platforms in Spanish.
Context: User promotes a technical web development post.
Input:
/promote-post lighthouse-perfect-scores --platforms x,hn,devto,reddit
Execution: Reads the post, notes it's deeply technical (Astro, Lighthouse, performance). Generates:
Context: User provides a wrong slug.
Input:
/promote-post my-awesome-post
Result:
❌ Post not found: my-awesome-post
Available posts with similar names:
- my-awesome-project (2024-05-15)
- awesome-tools-roundup (2024-03-10)
Usage: /promote-post <slug> [--platforms x,linkedin,hn,devto,reddit,facebook]
add-blog-post - Creates the blog posts that this skill promotescontent-writer - Can help refine or expand generated social content| Version | Date | Changes |
|---|---|---|
| 1.0.0 | 2026-03-03 | Initial version |
Create blog posts — from a topic (writes content) or with provided content (scaffolding). Use proactively when creating new blog posts or articles.
Pre-publication audit for blog posts — comprehensive final review of SEO, AEO, accessibility, images, content quality, i18n parity, and project conventions before publishing. Use proactively before publishing any blog post.
Pre-publication audit for blog series — validates series definition, post ordering, cross-post consistency, navigation, and runs individual post audits for all posts in the series. Use proactively before publishing any blog series.
Audit the blog tag taxonomy — frequency analysis, orphan detection, hierarchy validation, and proposals for new subtopic tags. Read-only — proposes, never modifies tags or posts. Use proactively before each release cycle or after a content drop of 5+ posts.
Optional DeepWorkPlan addon that connects an AI-first repo to the developer's Dailybot team — installing (with consent) the Dailybot agent skill (DailybotHQ/agent-skill) and/or the Dailybot CLI (DailybotHQ/cli), wiring the plan lifecycle into best-effort agent updates - kickoff when a plan starts, significant task completions, a blocked report when an unattended run halts, and a milestone on plan completion - with payloads derived from the plan's state layer, and optionally committing the Dailybot skill's deterministic hook enforcement (dailybot hook lifecycle hooks, CLI >= 1.12.0) so the agent harness itself reminds agents about unreported work. Opt-in, never required, never blocks the work, reconciles existing setups instead of clobbering them, and defers all auth to the Dailybot skill's own consent flow. Use when the developer or team already uses Dailybot and wants DWP progress visible to humans.
Optional DeepWorkPlan addon that safely upgrades a repo's dependencies — reasoning about the repo's ACTUAL package manager (npm/pnpm/yarn + ncu, pip/poetry/uv, cargo, go mod, bundler, composer, and more) rather than assuming npm — with a batched, validated, revertible workflow that detects the manager and manifests/lockfiles, classifies upgrades (patch/minor/major), upgrades in safe batches, runs the repo's real validation gate after each batch, reverts a failing batch, and summarizes. Opt-in, never required, reconciles with the repo's existing tooling. Use when the developer wants to bring dependencies up to date without breaking the build.