Social
Social media content
content-converter
by ma2ong
将长文浓缩并改写成适合社交媒体推广的内容。 使用场景：文章完成后生成X/小红书/Instagram/微信公众号推广内容、把长文转成短内容。 触发关键词：转X、转小红书、转Instagram、微信公众号、短内容、推广内容、社媒分发。
pre-post
by juangadm
Captures before/after screenshots of web pages for visual comparison in PRs. Use when user says "take before and after", "screenshot comparison", "visual diff", "PR screenshots", or after making visual UI changes.
publisher-api
by z1w2r3
视频发布 API/CDP 版：B站用 API（0 tokens），其他平台用 CDP 固定脚本。稳定、模型无关。当 orchestrator 指定 publisher-api-skill 时触发。
ghe-thread-manager
by Emasoft
Use this skill when the user expresses ANY intent related to issue/thread management: - Switching issues: "let's work on X", "switch to #Y", "go to the auth issue" - Checking status: "what are we working on?", "current issue?", "status?" - Background work: "what's in background?", "any features ready?", "check progress" - Starting development: "implement X", "add feature", "fix bug Y", "build a..." - Joining reviews: "let me see the review", "check that feature", "join #X" - Pausing/resuming: "pause this", "come back later", "resume #X" - Stopping transcription: "stop tracking", "don't record this", "private mode" - Resuming last session: "what were we working on?", "resume last issue", "continue where we left off" - Any natural expression of wanting to change focus or check work status This skill interprets natural language - users should NOT memorize commands. For the full GHE workflow protocol, see skill: github-elements-tracking
Создание Facebook кампаний
by dengineproblem
СообÑи ÑезÑлÑÑаÑ
ghe-claim
by Emasoft
CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree. USE THIS SKILL WHEN: - User says "claim issue #N" or "claim #N" - User says "start working on issue #N" or "take issue #N" - User says "I'll work on #N" or "pick up #N" - User wants to BEGIN work on a specific issue number - User selected an issue from available work and wants to claim it REQUIRED: An issue number must be specified or identifiable from context. DO NOT USE THIS SKILL WHEN: - User just wants to SEE status (use ghe-status) - User is ALREADY working and wants to post update (use ghe-checkpoint) - User wants to CHANGE phases (use ghe-transition) - User wants reports (use ghe-report) - No specific issue number is mentioned EXAMPLES: <example> Context: User wants to start work on a specific issue user: "Claim issue #201" assistant: "I'll use ghe-claim to claim issue #201 with the full protocol" </example> <example> Context: User picks from available work user: "I'll take issue #205" assistant: "I'll use ghe-claim to claim issue #205" </example> <example> Context: User wants to start on specific feature user: "Start working on #312" assistant: "I'll use ghe-claim to claim and set up issue #312" </example>
ghe-checkpoint
by Emasoft
POST a progress checkpoint to the CURRENTLY ACTIVE thread. Saves work state without changing phases. Requires an already-claimed in-progress thread. USE THIS SKILL WHEN: - User says "post a checkpoint" or "save my progress" - User says "update the issue" or "record current state" - User says "checkpoint" or "save checkpoint" - User completed a milestone and wants to record it - User encountered a blocker and wants to document it - User is about to take a break and wants to save state - Meaningful state change occurred during work PRECONDITION: User must already have an active (claimed, in-progress) thread. DO NOT USE THIS SKILL WHEN: - User wants to SEE status (use ghe-status) - User wants to START work on new issue (use ghe-claim) - User wants to FINISH current phase and MOVE to next (use ghe-transition) - User wants reports (use ghe-report) - No active thread exists (must claim first) EXAMPLES: <example> Context: User working on DEV wants to save progress user: "Post a checkpoint" assistant: "I'll use ghe-checkpoint to post your current progress to the active thread" </example> <example> Context: User completed a milestone user: "Save my progress, I finished the authentication module" assistant: "I'll use ghe-checkpoint to record this milestone" </example> <example> Context: User taking a break user: "I need to stop for now, save my work" assistant: "I'll use ghe-checkpoint to save your current state before you go" </example>
Оптимизация Facebook рекламы
by dengineproblem
â ï¸ Ð¡Ð¿ÑоÑи подÑвеÑждение пеÑед WRITE опеÑаÑиÑми.
ghe-transition
by Emasoft
CHANGE phases in the GitHub Elements workflow. Closes current thread and opens next phase thread. This is a PHASE CHANGE operation, not just saving progress. USE THIS SKILL WHEN: - User says "transition to TEST" or "move to REVIEW" - User says "I'm done with DEV, start TEST" or "DEV complete" - User says "advance to next phase" or "close this phase" - User says "demote to DEV" (from TEST or REVIEW) - User says "tests pass, ready for review" - User says "merge this" (after REVIEW PASS) - User explicitly wants to END current phase and BEGIN next DO NOT USE THIS SKILL WHEN: - User just wants to SEE status (use ghe-status) - User wants to START work on new issue (use ghe-claim) - User wants to SAVE progress but CONTINUE working (use ghe-checkpoint) - User wants reports (use ghe-report) - User is not ready to END current phase IMPORTANT: This CLOSES current thread and OPENS next thread. Use ghe-checkpoint if you just want to save progress without changing phases. EXAMPLES: <example> Context: DEV work complete, ready for testing user: "I'm done with DEV, transition to TEST" assistant: "I'll use ghe-transition to close DEV and open TEST thread" </example> <example> Context: All tests pass, ready for review user: "Tests pass, move to REVIEW" assistant: "I'll use ghe-transition to close TEST and open REVIEW thread" </example> <example> Context: Structural issues found in TEST user: "This needs structural changes, demote to DEV" assistant: "I'll use ghe-transition to demote from TEST back to DEV" </example> <example> Context: REVIEW passed, ready to merge user: "REVIEW passed, merge it" assistant: "I'll use ghe-transition to complete the workflow and merge" </example>
enforce-contract
by knowlet
單元測試與代碼提交前觸發。掃描並驗證方法的 pre-conditions、post-conditions 與 invariants，透過契約式設計減少 AI 幻覺。
bash-install
by cuozg
Install software with auto-retry, fallback strategies, and post-install verification — use for 'install', 'set up', 'install software', 'install tool', 'install dependency'
moltbook
by wweggplant
The social network for AI agents. Post, comment, upvote, and search on Moltbook. Use when Agent needs to Post updates or thoughts to Moltbook, Check feed/notifications, Comment on or vote for posts, Search for content/users/communities, Register a new agent.
last30days
by Hairy-jumper134
"Analyzes the last 30 days of trends across X/Twitter, Weibo, Xiaohongshu, and Douyin, then returns concise Chinese reports with cross-platform overlaps, regional differences, and emerging signals. Use when the user asks about recent trends, social buzz, internet-native topics, China-vs-global narratives, or fast-moving platform analysis."
signet
by h1-hunt
Interact with Signet onchain advertising on Hunt Town. Use when the user wants to check spotlight ad prices, list current ads/signatures, or post a URL to the Signet spotlight. Supports both direct on-chain signing (with ETH, USDC, HUNT, or MT tokens) and x402 payment protocol for programmatic ad placement by AI agents.
claw-apply
by MattJackson
External ATS jobs are queued and classified â stubs will be promoted to full implementations based on usage data.
page-cro
by silvainfm
When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
social-content
by silvainfm
"When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies."
addressing-reviews
by tenzir
Address GitHub PR review feedback. Use when responding to reviewers, resolving threads, or handling review comments.
burke-conservative
by Oncorporation
"Teaches and deploys Edmund Burke's conservative philosophy: preserve organic social order, tradition, institutions, and gradual reform against revolutionary chaos."
social-media-generator
by mamba-mental
This skill should be used when the user requests social media content creation for Twitter, Instagram, LinkedIn, or Facebook. It generates platform-optimized posts and saves them in an organized folder structure with meaningful filenames based on event details.
rust-async
by peixotorms
Use when writing async or concurrent Rust code with tokio, async-std, futures, channels, mutexes, threads, spawn, or runtime. Covers async patterns, Pin, poll, Stream, timeout, graceful shutdown, task management, blocking in async, mutex across await, select, JoinSet, CancellationToken, sync primitives, broadcast, mpsc, oneshot, watch channels, deadlock prevention, and thread safety.
sniper-dynamics-and-mitigation
by SanctifiedOps
Understand sniper bots in Solana launches and implement defensive measures without harming fair access. Use before token or LP go-live.
reputation-recovery-playbook
by SanctifiedOps
Recover credibility after mistakes: incident comms, restitution, roadmap resets, and monitoring sentiment. Use after exploits, missteps, or comms errors.
bmad-autopilot-skill
by martin-janci
Autonomous BMAD development orchestration