本文へ移動
cccskills
無料GitHub で公開

kortix-social

Recipe: write platform-native social content for Kortix (LinkedIn posts, X threads, carousels, Instagram, TikTok, Reels and Shorts video scripts, content calendars) and repurpose one long-form piece into many. Load kortix-brand first for voice, positioning and claims. This skill covers platform mechanics: limits, hooks, cadence, repurposing. Use when the user asks for a LinkedIn post, Twitter or X thread, carousel, social calendar, "what should I post", "repurpose this", a video hook, a reel or short-form video.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md7.0 KB
  • evals/evals.json3.6 KB
  • references/platform-limits.md1.2 KB
  • references/post-templates.md2.3 KB
  • references/short-form-video.md2.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Social Content

Turn product context into platform-native content, and turn one piece of content into many. This skill writes the posts and the scripts. It hands visual production to kortix-image.

Load kortix-brand first. It owns voice, positioning, claims and the words not to say. This file owns platform mechanics only.

Before writing

Read the kit, then write. Do not interrogate.

  1. Voice and vocabulary. voice-and-tone.md, section 5.9 (Social), and the don't-say list.
  2. Positioning and audience. positioning.md: the approved lines and the pitch for the audience.
  3. Claims. claims.md. A post makes only a sanctioned claim. Never name a customer.
  4. Visuals. For carousels, quote graphics, thumbnails or video covers, hand the brief to kortix-image. Do not describe pixels here.

Ask only for what the kit does not cover: the goal (awareness, leads, traffic, community), the platform, the action you want from readers, and whether the voice is personal or company. Default from the kit.

Routing

User intentMode
"write me a post / thread / carousel"Create
"turn this blog/podcast/webinar into social"Repurpose
"script a reel / TikTok / Short / video hook"Video
"plan my week / build a calendar"Plan
"what should I post? / I'm out of ideas"Ideate

Platform quick reference

PlatformBest forCadenceNative format
LinkedInB2B, thought leadership3–5×/weekText story, carousel, poll
Twitter/XTech, real-time, community3–10×/dayThread, hot take, reply
InstagramVisual, lifestyle1–2 + Stories dailyReel, carousel
TikTokReach, younger audience1–4×/dayShort-form video

Two distribution rules that apply almost everywhere: first-hour engagement decides reach, and external links in the post body suppress reach — put links in the first comment or a reply. Character/hashtag limits live in references/platform-limits.md.

Create

Every post is one hook + one idea + one action. The first line earns the second.

  • Hook first. Pick a hook type to the goal: curiosity, story, value or contrarian. A hook states a mechanism or a fact. It does not use a banned hype word, and "contrarian" never means an attack on a named product. Library in references/post-templates.md. If reach is flat, the hook is almost always the cause; test new hooks before anything else.
  • One idea per post. Don't pack a thread's worth of value into a single post — split it.
  • Standalone. The reader has no prior context. A repurposed clip's caption must work even if they never saw the source.
  • One clear action. A question, a save, a "link in comments" — never two.
  • Match length and tone to the platform (limits file). LinkedIn rewards line breaks and 1,200–1,500 chars; X rewards brevity; carousels need a hook slide that promises a payoff.

Repurpose

The strongest social content isn't written from scratch — it's extracted from long-form and adapted per platform. This is the highest-leverage mode.

  1. Mine content atoms — pull 5–10 self-contained moments from the source: a quotable claim, a complete mini-story, a tactical tip, a contrarian take, a data callout, a behind-the-scenes moment.

  2. Adapt each atom to a format — same idea, native shape:

    AtomGoes to
    Quotable claim / hot takeX post, LinkedIn, quote graphic
    Complete mini-story (setup→resolution)Reel, TikTok, Short
    Tactical tip / frameworkLinkedIn carousel, Short
    Data / statLinkedIn carousel, X
    List of takeawaysX thread
  3. Write standalone captions for each.

  4. Spread across 1–2 weeks — never dump them all at once.

  5. Reshare evergreen atoms every 3–6 months.

Rough yield from one podcast/webinar/video: 3–5 short clips, 1–2 LinkedIn posts, 1 X thread, 1 carousel.

Video

Short-form video is the highest-reach format on every platform. Frameworks and the full hook library are in references/short-form-video.md. The essentials:

  • 3-second rule — visual hook + verbal hook + text overlay, all landing in the first second. Show the payoff or the problem immediately; never build up to it.
  • Pick a structure — Problem→Agitate→Solution→CTA, List (one item every 5–8s), or Tutorial (show the result first). Keep it 9:16, 15–60s.
  • Caption everything — most short-form is watched on mute; subtitles lift watch time 25–40%. Max 2 lines, 3–5 words each, key word highlighted.
  • Output a script with timestamped beats (hook / body / CTA) plus production notes (sound, b-roll, overlays). Hand any cover frame or thumbnail to kortix-image.

Plan

Build around 3–5 content pillars the audience cares about and you can sustain — e.g. for a SaaS/dev-tool brand: industry insight (~30%), behind-the-scenes/build-in-public (~25%), educational how-tos (~25%), personal/opinion (~15%), promotional (~5%). Keep promo light.

Then produce a weekly grid (day × platform × pillar × format) and a batching plan: write the week's posts in one 2–3 hour block, schedule the evergreen ones, and leave gaps for real-time replies and trend-jacking. Maintain a 1–2 week queue, never more.

Ideate

When stuck, generate from the pillars, not from a blank page: repurpose a past high-performer, react to industry news, answer a real audience question, share a lesson or failure, or document what you're building this week. For each idea, name the pillar, the platform, and the hook before drafting.

References

Related

  • kortix-brand owns voice, positioning, claims and terminology for all copy.
  • kortix-image produces the carousels, graphics, thumbnails and video covers.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Policy runbook for turning a Slack access request into a least-privilege, policy-checked GitHub or AWS IAM grant. Covers the role-to-grant mapping, extra-scrutiny cases, the approval handshake, and how an applied grant gets logged.

日本語の概要は準備中です。原文の説明を表示しています。

kortix-ai/suna2万2026年10月12日 更新

Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.

日本語の概要は準備中です。原文の説明を表示しています。

kortix-ai/suna2万2026年10月12日 更新

Daily read-only ad-performance runbook — budget pacing, CPA/ROAS drift, underperforming ads and keywords, and anomaly detection across Google Ads and Meta Ads, plus how to rank and word optimization recommendations for {{alert_channel}}.

日本語の概要は準備中です。原文の説明を表示しています。

kortix-ai/suna2万2026年10月12日 更新

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

日本語の概要は準備中です。原文の説明を表示しています。

kortix-ai/suna2万2026年10月12日 更新

Extraction, PO matching, duplicate detection, and overcharge tolerance for processing incoming vendor invoices from {{invoice_label}} against the POs and ledger in {{ap_ledger}}. Load this before extracting a single invoice so every one is checked to the same standard and only genuine exceptions reach a human, with no invoice ever scheduled for payment by the agent.

日本語の概要は準備中です。原文の説明を表示しています。

kortix-ai/suna2万2026年10月12日 更新

Daily brand-mention monitoring loop for {{brand_terms}}. Searches news, social platforms, and forums for new mentions, dedupes against the ledger of mentions already reported, classifies sentiment and notability, and posts a digest with suggested response drafts to {{slack_channel}} — never posts, replies, or comments anywhere.

日本語の概要は準備中です。原文の説明を表示しています。

kortix-ai/suna2万2026年10月12日 更新

kortix-ai のスキルをすべて見る

このスキルの問題を報告する