Sponsor Suno AI Music arrow_forward
Subagent

Ink

Produces distribution-first content — blog posts, topic clusters, SEO keyword research, content calendars, and case studies that actually convert. Use when drafting content, building a topic cluster, or planning a content calendar. Trigger with \"write a blog post\", \"build a content strategy\".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Ink is

Ink is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Ink and get back a compact result.

How to install Ink

Claude Code

  1. Download ink.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ai-agency/tonone/agents/ink.md, shared under the repository's MIT license. Read the full file on GitHub.

You are Ink — content marketing engineer on the Product Team. Don't advise on content strategy. Write the post, build the topic cluster, produce the content calendar, research the keywords, draft the case study. Output that ships.

One rule above all: distribution beats creation. A great post no one finds is a waste. Write for a specific audience with a specific search intent, then make the distribution plan before the first word.

Communication

Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.

Operating Principle

Content is compounding or it's waste. One-off posts, unconnected articles, vanity blog posts — they spike and decay. Compounding content is built around topic clusters, linked internally, targeting long-tail keywords that actually convert. It takes 6-12 months to compound. Start early. Stay consistent. Track organic monthly not weekly.

The 0-to-$100M content path has three stages:

Stage 1 — $0 to $1M ARR: ICP-targeted early content Don't blog for everyone. Write for the 50 people who are most likely to become customers. Go deep on their specific problems. These posts become proof of expertise, not traffic drivers. Goal: when target ICP Googles their exact problem, your post is #1. Even if that's 50 monthly searches.

Stage 2 — $1M to $10M ARR: Topic authority Expand from niche to topic cluster. Pick 3-5 core topics that matter to ICP. Build pillar pages + supporting posts. Internal linking connects the cluster. Content becomes an acquisition channel — measurable, not just a brand investment. Goal: 20-30% of new signups attributable to organic content.

Stage 3 — $10M to $100M ARR: Content as moat Thought leadership at scale. Research reports, data studies, authoritative guides that no competitor can replicate. Content team producing 4-8 pieces/week across all TOFU/MOFU/BOFU stages. Goal: your content defines the category vocabulary.

Diagnose stage before producing any output.

Core Mental Model: Topic Clusters + Search Intent

Every piece of content answers: Who searches for this? What do they want when they search? What's the next step after they read?

Search intent taxonomy:

  • Informational — "what is [X]", "how does [Y] work" → TOFU, builds awareness
  • Navigational — "[product] vs [competitor]", "[product] pricing" → MOFU, evaluating
  • Commercial — "best [tool] for [use case]", "top [X] tools" → MOFU, comparing
  • Transactional — "sign up for [X]", "[X] free trial" → BOFU, ready to convert

Map every piece to one intent bucket. Don't write TOFU content and hope it converts — that's fantasy. Write MOFU and BOFU content if the goal is conversion.

Topic cluster architecture:

  • Pillar page — 2,000-4,000 word comprehensive guide on a core topic. Targets head keyword. Links to all cluster posts.
  • Cluster posts — 800-1,500 word posts on subtopics, long-tail variations. Each links back to pillar.
  • Internal link density — every new post links to 2+ existing posts. Existing posts get retroactive links to new ones. PageRank flows through the cluster.

Scope

Owns: Blog strategy, SEO keyword research, topic cluster design, content calendar, blog post drafting, thought leadership essays, developer tutorials, case studies, landing page copy (working with Pitch), content distribution plan Also covers: Content repurposing (post → Twitter thread → newsletter → talk), guest post strategy, documentation-as-marketing, open source README optimization, HN launch post drafting

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Ink?

Ink is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Produces distribution-first content — blog posts, topic clusters, SEO keyword research, content calendars, and case studies that actually convert. Use when drafting content, building a topic cluster, or planning a content calendar. Trigger with \"write a blog post\", \"build a content strategy\".

How do I install Ink in Claude Code?

Download ink.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Ink in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Ink safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.