Blogger Distiller
otter1101/blogger-distiller
A skill your agent uses when the user wants to analyze or distill a blogger/account on Xiaohongshu or Douyin, benchmark a target creator, or diagnose their own content strategy.
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow.
Install Ink Calendar
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-calendar --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-calendar .claude/skills/ink-calendar && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ink-calendar" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-calendar into .claude/skills/ink-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-calendar", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-calendarType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-calendar --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-calendar .agents/skills/ink-calendar && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ink-calendar" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-calendar into .agents/skills/ink-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-calendar", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-calendar --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-calendar .cursor/skills/ink-calendar && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ink-calendar" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-calendar into .cursor/skills/ink-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-calendar", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/ink-calendar--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-calendar --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-calendar .gemini/skills/ink-calendar && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ink-calendar" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-calendar into .gemini/skills/ink-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-calendar", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-calendarInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-calendar .github/skills/ink-calendar && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ink-calendar" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-calendar into .github/skills/ink-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-calendar", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-calendar --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-calendar .opencode/skills/ink-calendar && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ink-calendar" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-calendar into .opencode/skills/ink-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-calendar", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ink-calendar- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 305 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow.
- Works in 7 steps: Gather Calendar Context → Set Publishing Cadence → Build Content Mix → …
- Asked to build a content calendar
- SKILL.md covers Steps and Delivery
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ink Calendar is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Content strategy. 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. The licence is MIT.
When your agent uses it
- Asked to build a content calendar
- Plan our content for the quarter
- How often should we publish
- Create an editorial schedule
Example prompts
- “build a content calendar”
- “plan our content for the quarter”
- “how often should we publish”
- “/ink-calendar”
Requirements
- Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, AskUserQuestion
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashGlobGrepAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ink Calendar loads about 1.2k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 305 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 305 words, ~1,228 tokens.
Download SKILL.mdSave it as
.claude/skills/ink-calendar/SKILL.md (or your agent's skills folder).- name
- ink-calendar
- description
- Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
- allowed-tools
- Read, Bash, Glob, Grep, AskUserQuestion
- version
- 0.1.0
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
Content Calendar
You are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar.
Steps
Step 0: Gather Calendar Context
Before building:
- Who is creating content? (founder only / founder + contractor / content team)
- How much time per week for content? (1h / 4h / dedicated person)
- What ARR stage? (Stage 1: 1 post/2 weeks, Stage 2: 2-4 posts/week, Stage 3: daily)
- What content types are in scope? (blog, tutorials, case studies, newsletter)
- What distribution channels exist? (email list, Twitter, LinkedIn, HN, Product Hunt, etc.)
Step 1: Set Publishing Cadence
Match cadence to capacity — not ambition. Inconsistency destroys SEO signals and audience trust.
| Capacity | Cadence | Format priority |
|---|---|---|
| Founder only, <4h/week | 2 posts/month | Long-form (evergreen) |
| Founder + 1 contractor | 4 posts/month | Mix of evergreen + timely |
| Part-time content hire | 2 posts/week | Cluster-building |
| Full-time content | 3-5 posts/week | Full editorial calendar |
Step 2: Build Content Mix
For each publishing period, balance:
| Content type | % of mix | Why |
|---|---|---|
| Evergreen tutorials | 40% | Compounds over time, best SEO ROI |
| Thought leadership | 20% | Brand authority, often goes viral |
| Product use cases | 20% | MOFU conversion, shows product value |
| Comparison / alternatives | 10% | High commercial intent |
| Community roundups / curated | 10% | Low effort, builds goodwill |
Step 3: Build the Calendar
Produce a 12-week rolling calendar:
## Week 1
- Post 1: [Title] | Keyword: [X] | Type: [tutorial] | Author: [name] | Status: [draft/review/scheduled]
- Post 2: [Title] | Keyword: [Y] | Type: [thought leadership] | ...
## Week 2
...For each post include:
- Working title (keyword-forward)
- Target keyword
- Content type
- Estimated word count
- Author
- Distribution plan (where does it go after publish)
- Deadline
Step 4: Design Distribution Workflow
Content without distribution is lost. For each published piece:
DISTRIBUTION CHECKLIST (after every publish):
[ ] Share on Twitter/X with [specific hook — not just the title]
[ ] Share on LinkedIn with [professional angle]
[ ] Submit to HN if technical: "Ask HN: [question the post answers]" or "Show HN: [if a tool/resource]"
[ ] Send to email list (if applicable)
[ ] Add to internal links of 2 existing related posts
[ ] Submit to [relevant newsletter/aggregator if applicable]
[ ] Reply to mentions/comments within 24hStep 5: Content Repurposing Map
One piece of content, multiple formats:
Long-form blog post (2,000w)
→ Twitter thread (10-15 tweets) — most popular insights
→ LinkedIn article — professional framing
→ Newsletter feature — abbreviated version
→ Developer conference talk abstract — if topic is technical
→ Follow-up shorter post — one section expandedStep 6: Produce Calendar Document
# Content Calendar — [Product Name]
**Period:** [Q1/Q2/etc. YYYY]
**Publishing cadence:** [N posts per week/month]
**Primary goal:** [organic traffic / brand / signups attribution]
## Editorial Themes by Month
**Month 1 theme:** [e.g., "developer onboarding automation"]
- Focus on: [ICP segment] dealing with [pain]
- Target cluster: [pillar page + supporting posts]
**Month 2 theme:** [e.g., "replacing meetings with async AI updates"]
...
## 12-Week Content Plan
[table with title, keyword, type, word count, author, deadline, distribution]
## Distribution Workflow
[checklist from Step 4]
## Repurposing Plan
[map from Step 5]
## Metrics to Track
- Posts published on schedule (target: 90%+)
- Posts with internal links (target: 100%)
- Traffic per post at 30/60/90 days
- Signup attribution from contentDelivery
Produce the complete calendar as a table plus the distribution checklist and repurposing plan. Be specific about titles and keywords — not placeholder topics.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. If output exceeds 40 lines, delegate to /atlas-report.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/ai-agency/tonone/skills/ink-calendar of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Ink Calendar next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ink Calendar this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Blogger Distillerotter1101/blogger-distiller | 701 | — | ~3.8k | Automated safety check: Notes | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| WeChat Hot Article AnalysisSpaceZephyr/creator-buddy | 1.6k | — | ~847 | Automated safety check: Pass | None | |
| Brand Voice Content Creatordavila7/claude-code-templates | 33k | 3 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
WeChat Hot Article Analysis
SpaceZephyr/creator-buddy
Fetches hot WeChat Official Account articles by sector or keywords and produces a data file and an HTML report with rankings, style patterns and writing references.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
Ralph Copywriter
muratcankoylan/ralph-wiggum-marketer
A skill your agent uses when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand…
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Ink Calendar
What does Ink Calendar do?
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Ink Calendar is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow.
When should I use Ink Calendar?
Ink Calendar fits situations like: asked to build a content calendar; plan our content for the quarter; how often should we publish; create an editorial schedule.
How do I install Ink Calendar in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/ink-calendar in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/ink-calendar in your project. Claude Code loads it when a task matches its description.
How do I install Ink Calendar in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/ink-calendar in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/ink-calendar in your project. Codex loads it when a task matches its description.
Can I use Ink Calendar in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-calendar -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ink-calendar, .gemini/skills/ink-calendar, .github/skills/ink-calendar and .opencode/skills/ink-calendar in your project.
What does Ink Calendar need to run?
SKILL.md names no scripts, command-line tools or credentials: Ink Calendar is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, AskUserQuestion.
Does Ink Calendar access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ink Calendar safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Ink Calendar use?
Ink Calendar is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ink Calendar use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ink Calendar?
Skills that share tags, products or a category with Ink Calendar: Blogger Distiller (otter1101/blogger-distiller, 701 stars), Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars), Blog Post Drafting (luongnv89/claude-howto, 42k stars) and WeChat Hot Article Analysis (SpaceZephyr/creator-buddy, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ink Calendar?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.