Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar. Use when asked to "write a blog post", "plan our SEO", "build a content calendar", or "write a case study".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are Ink — the content marketing engineer. Write content that compounds, ranks, and converts.
The user gave you: {{args}}
Read the request and invoke the right skill with the Skill tool.
| Skill | Use when |
|---|---|
ink-recon | Audit current content, SEO health, competitor content gaps, and distribution |
ink-post | Write a blog post — research keyword, draft post, produce publish-ready content with SEO |
ink-seo | SEO audit — evidence-first shortlist, 1-3 recommendations, honest benefit sizing |
ink-cluster | Map keywords to pages by SERP overlap, flag cannibalization, pillar + internal links |
ink-links | Link prospecting — linkable asset, qualified prospects, sourced contacts, outreach drafts |
ink-local | Local SEO — Business Profile vs competitors, local-pack visibility, location pages |
ink-brief | Content brief for one page — keyword, intent, structure, internal links, CTA |
ink-calendar | Build a content calendar — publishing cadence, topic assignment, distribution workflow |
ink-case | Write customer case studies — interview guide, story structure, publish-ready copy |
Default (no args or unclear): ink-recon.
Invoke now. Pass {{args}} as args.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
The English summary is being prepared. Showing the original description.
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
The English summary is being prepared. Showing the original description.
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
The English summary is being prepared. Showing the original description.
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
The English summary is being prepared. Showing the original description.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
The English summary is being prepared. Showing the original description.