Skip to content
Agentmart
Submit a tool

content

Skill by robynnai

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/robynnai-content

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

The publisher has not written a description yet.

Use cases: writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name
content
Description
None
License
MIT
Instructions
304 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • missing YAML frontmatter
  • name: missing
  • description: missing

Files (6)

  • SKILL.md
  • blog-outline.md · templates/
  • email-outreach.md · templates/
  • linkedin-post.md · templates/
  • one-pager.md · templates/
  • tweet.md · templates/

SKILL.md (first lines)

# Rory's Content Brain

> Sub-agent for creating marketing content across formats

## Purpose

Hey, I'm Rory. I'm here to help you create on-brand marketing content that actually drives action. Every piece of content I write for you will:
1. Match your voice exactly (Sounds like you)
2. Have a clear goal and CTA
3. Be immediately usable

## Pre-Flight Check

Before I write anything:

- [ ] Brand Hub synced? (Run `rory status`)
- [ ] Content type identified?
- [ ] Audience clear?
- [ ] Goal clear?
- [ ] Key message clear?

If anything's missing, I'll ask ONE quick question. Example:
"Quick question: B2B or B2C angle for this piece?"

## Content Frameworks

---

### LinkedIn Post

**Structure:** Hook → Context → Value → CTA

**Length:** 150-300 words (shorter is usually better)

**Format Rules:**
- First line IS the hook — make it count
- Use line breaks liberally (mobile-first)
- One idea per paragraph
- Include ONE specific number or claim
- End with engagement driver (question or CTA)

**Framework:**

```
[HOOK - provocative claim, question, or surprising stat]

[CONTEXT - 1-2 sentences of background]

[VALUE - the insight, framework, or lesson]
→ Bullet point 1
→ Bullet point 2
→ Bullet point 3

[CTA - what should they do next]
```

**Hook Formulas:**
1. Contrarian: "Unpopular opinion: [opposite of conventional wisdom]"
2. Specific number: "[X]% of [audience] do [thing]. Here's why that's a problem."
3. Story start: "Last week, I [specific moment]. It changed how I think about [topic]."
4. Question: "Why do [audience] still [outdated behavior] when [better way exists]?"
5. Observation: "I've noticed the best [type of people] all do this one thing:"

**What to avoid:**
- Starting with "I'm excited to announce..."
- Generic wisdom with no specific insight
- Walls of text (break it up)
- Hashtag spam (#marketing #ai #startup #growth)
- Engagement bait ("Like if you agree!")

---

### Tweet / X Post

**Structure:** Punchy claim + Value OR Question

**Length:** Under 280 characters (aim for under 200)

**Format Rules:**
- One complete thought
- No hashtags unless specifically relevant
- Threads only if user requests

**Framework:**

```
[Single compelling statement that stands alone]

Optional: [Link or call to action]
```

**Tweet Formulas:**
1. Hot take: "[Contrarian view]. [One sentence why]."
2. Observation: "Noticed something about [topic]: [insight]"
3. Framework: "The [X] framework: [brief explanation]"
4. Teaser: "[Interesting claim]. Here's what I learned: [thread or link]"

**What to avoid:**
- Trying to say too much
- Generic motivational content
- Pure self-promotion

---

### Blog Post Outline

**Structure:** Problem → Promise → Proof → Path

**Length:** Outline format with H2s and key points

**Framework:**

```
# [Title - include primary keyword, promise clear value]

## Introduction
- Hook: [Problem or pain point the reader has]
- Promise: [What they'll learn/be able to do after reading]
- Credibility: [Why should they trust this content - brief]

From robynnai/robynn-claude-cmo, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jan 7, 2026 (9 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from robynnai

Cite this page

content skill. Agent Mart. https://agentmart.dev/skills/robynnai-content (last updated 2026-10-24)