kami-community/kami/viral-formats

Claude Code and agent skill by kami-community/kami

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Research current platform-native viral/engagement formats before drafting distribution posts. Use on every Create distribution research run so drafts stay timely.

Install

npx vskill@latest install kami-community/kami/viral-formats

SKILL.md

Viral formats (live research)

Do not rely on a static tip list. Formats change weekly. Before drafting any distribution opportunity:

Procedure

  1. Identify the target platform from the Work Order.
  2. Research what is working now on that platform (web search / browser / recent examples). Prefer patterns from the last 7–30 days over evergreen advice.
  3. Pick one format that fits the company’s angle and the specific thread/source (if any).
  4. Draft to that format only. Ban generic “here’s what we built” pitches unless the chosen format is explicitly a product demo / Show HN / launch maker comment.
  5. Return with the opportunity:
  • format_used — short name of the pattern (e.g. hot-take-thread, value-first-reddit-comment, founder-lesson-li-post)
  • format_why — one line: why this format fits this week and this source

Platform hints (starting points — always verify live)

PlatformOften-working patterns (verify current)
XShort hot take + proof; reply with a concrete tip; mini thread (hook → story → lesson); demo GIF + one line
RedditValue-first answer that stands alone; “here’s what worked for me” without linkspam; AMA-style honesty
LinkedInSpecific founder lesson; before/after; question that invites peer stories (no engagement bait)
Hacker NewsTechnical tradeoff; Show HN clarity; no marketing voice
Product HuntMaker comment / FAQ; honest limitations
DiscordHelpful reply in an opt-in community thread; never cold DM

Hard rules

  • Refresh formats every research run — do not reuse last month’s template blindly.
  • If research tools are unavailable, pick a conservative format, set format_used to that name, and say so in format_why ([no live research]).
  • Never invent that a post went viral or that you published.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
64
Repository forks
9
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/kami-community/kami/viral-formats/badge)](https://verified-skill.com/skills/kami-community/kami/viral-formats)

Something wrong with this skill or its page? Tell us.