ink

Draft or prepare channel-native marketing outputs for Ink channels that do not yet have a dedicated writer skill, including Instagram, TikTok, YouTube, X/Twitter, Facebook, newsletters, email sequences, Discord, forums, communities, podcasts, webinars, ads, SMS, push, in-app messages, app-store listings, marketplace listings, events, sales collateral, and program-run handoffs. Route to specialized Ink skills when available.

Create or update Ink Content Program packs for recurring marketing series, campaigns, repeatable formats, asset workflows, calendars, and performance trackers across any marketing channel or production surface, including social, video, audio, email, communities, owned web, paid/partner, direct/product, events, and sales assets.

Create a reusable Content Idea Brief for One Horizon approval across dedicated Ink channels or broader generic marketing channels by combining current company context, trend signals, archive gaps, and channel fit. Use when Codex needs to map a goal to one concrete content idea, choose a channel, manage trend-source URLs, or turn a current signal into an approved-later brief that a writer workflow can pick up. Blog ideas follow the Blog Lifecycle Contract. Do not draft content in this skill.

Execute or prepare runs from an existing Ink Content Program pack for any marketing channel or production surface. Use when the user wants to batch recurring content, create program run artifacts, route a format into dedicated Ink skills, use the generic channel-content-writer fallback, or produce handoff prompts for semi-manual marketing steps.

Orchestrate blog writing from brief to final draft using the repo blog corpus, lightweight web research, One Horizon context docs, image planning, two writing passes, and the required review sequence. Use when Codex needs to draft or revise an original long-form blog article for this repo. Do not use this skill for LinkedIn posts, social-first writing, or storage-only tasks.

Turn approved One Horizon Ink content ideas into reviewable drafts. Use when Codex is asked to process planned `[Ink Idea]` records, run the matching writer workflow or generic channel writer, update Blog initiatives in place from `[Ink Idea] [Blog]` to `[Ink Draft] [Blog]`, and leave draft content in One Horizon for human review. Do not use this skill for ideation, direct publishing, corpus storage, or automation setup.

Process reviewed One Horizon Ink draft records into revised drafts or publish-ready output. Use when Codex is asked to handle `[Ink Draft]` initiatives under `Ink - Blog`, `Ink - LinkedIn`, `Ink - Reddit`, or optional `Ink - Channel Content` that are `Planned` or `In Progress`, apply human comments, prepare manual publishing handoffs, or rebuild blog drafts through the blog writer before creating publishing branches and pull requests. Blog draft work stays on the same initiative that began as `[Ink Idea] [Blog]`. Do not use this skill for ideation, first-draft creation from ideas, corpus storage, or automation setup.

Orchestrate LinkedIn social writing from brief to final draft using a published-post corpus, One Horizon context docs, staged review passes, and optional local MCP research tools. Use when Codex needs to draft or revise original LinkedIn posts, comment replies, DMs, DM replies, or reposts while matching the saved voice, loading only the relevant One Horizon context, asking only necessary questions, and iterating through humanizer, tone, style, and fact-check passes. Do not use this skill for storage-only requests such as logging, saving, importing, or batch-storing already-written posts in the corpus.

Set up Ink's author-scoped context docs in One Horizon. Use when the user asks to set up Ink, configure context, onboard a new author, populate missing One Horizon author context docs, or fix missing context before using the writing workflows. Requires a connected One Horizon MCP server. Does not overwrite or refresh existing author context docs.

Draft Reddit posts and follow-up comment replies using One Horizon context docs, subreddit research, the Reddit corpus, and Ink's staged review passes. Use when Codex needs to write or revise Reddit content that should fit subreddit norms instead of sounding like generic social copy.

Search and download candidate blog images through a local Unsplash-backed MCP server while filtering out previously used assets and preserving attribution metadata. Use when Codex needs to source a fresh image for a blog post, compare candidate photos for an article concept, download a selected image into the configured local staging folder, or check the local image-provider setup before image work.

Upload local blog image files to the selected Ink profile's configured S3 bucket through a local MCP server and return the object metadata plus public URL. Use when Codex needs to publish a downloaded blog image, move a local JPG, PNG, or WebP asset into the profile's blog-images bucket, verify the target object key before upload, or keep blog image credentials isolated in a local .secrets config.

Remove AI tells from drafts early in the review loop while keeping the intended meaning, stance, and voice. Use when Codex has a raw content draft such as a LinkedIn post, blog article, reply, or other editorial copy and needs a first cleanup pass before tone, style, and fact review.

Review structure, readability, and persuasion in a draft without changing the author's core voice. Use when Codex needs to tighten a short-form or long-form editorial draft such as a LinkedIn post, blog article, reply, or other narrative copy after a usable draft exists and in the position defined by the active writer workflow.

Review a draft against the saved corpus and One Horizon context docs to catch tone drift, stance drift, and the wrong level of personal detail. Use when Codex needs to compare a content draft such as a LinkedIn post or blog article to the author's actual voice near the end of the editing loop or wherever the active writer workflow places tone review before finalization.

Finalize a LinkedIn post with the repo review workflow and store it in the selected Ink profile's published corpus only when approval is explicit. Use when the user asks to finalize a post, approve the final version, or save the approved post, and the result should go through the humanizer, tone, style, and optional fact-check passes before optionally being written into the selected profile's LinkedIn root with the repo storage template. Do not use this skill for simple corpus logging of already-written posts that do not need final editing.

Store one or more already written, shared, or published LinkedIn items in the selected Ink profile corpus with deterministic filenames and the repo storage templates. Use when the user says things like "I shared this", "store this post", "store these posts", "store the following posts", "save this to the corpus", "add these to the corpus", "log this LinkedIn post", "import these posts", or provides multiple posts separated by `|`, especially when the content already exists and should be written into the selected profile's LinkedIn root with the correct format, date, follow-up number, and optional format-template metadata. Do not use this skill for drafting new copy or for final review before approval.

Create or update strategic implementation briefs for website pages by coordinating intake, site-pattern analysis, competitor research, brief-direction ideation, SEO intent planning, positioning, conversion planning, copy guidance, claim validation, and final brief assembly. Use when Codex needs a website page brief, web page brief, landing page brief, product page brief, comparison page brief, help page update brief, "alternative to X" page brief, or requests such as "create a brief for a new product page", "write a landing page brief", "update our alternative to Linear page", "update the brief for this help page", or "plan a web page brief for this site". Do not use it to write the full page, implementation tickets, HTML, CSS, JS, React, or components.

Finalize a Reddit post or comment reply with the repo review workflow and store it in the selected Ink profile's local Reddit corpus only when approval is explicit. Use when the draft is close and needs the last review loop before optional storage.

Research Reddit communities and winning discussion patterns using public Reddit data, One Horizon context docs, and Ink's MCP tools. Use when Codex needs to find audience-relevant subreddits, inspect the best recent posts, understand subreddit rules and anti-promo norms, or hand a Reddit writing brief to another skill.

Store one or more already written, shared, or published Reddit posts or comment replies in the local Reddit corpus with deterministic filenames and repo templates. Use when the primary user intent is storage, logging, saving, or importing existing Reddit content rather than drafting new copy.

Capture and normalize the required inputs for a website page brief, identify missing context, and separate confirmed facts from assumptions before strategy work starts. Use when Codex needs to gather the minimum inputs for a new or updated product page, landing page, help page, feature page, solution page, comparison page, or evergreen page brief. Do not use it for site analysis, competitor research, SEO planning, or final brief assembly.

Research competitor or comparable pages for a website brief by inspecting messaging patterns, structure, CTA behavior, proof mechanisms, differentiation opportunities, and overused tropes. Use when Codex needs external page research for a new or updated landing page, product page, help page, comparison page, solution page, or similar web page brief. Do not use it for same-site pattern analysis or final brief assembly.

Plan the conversion path for a website page brief by mapping funnel stage, desired user action, friction points, exact CTA labels, exact CTA placements, support for the primary CTA, the role of the secondary CTA, and trust or reassurance elements needed near conversion moments. Use when Codex needs CTA and conversion strategy for a new or updated web page. Do not use it to write full page copy or to replace the broader messaging strategy.

Write, rewrite, or improve final marketing copy for website pages such as homepages, landing pages, pricing pages, feature pages, about pages, product pages, and solution pages. Use when Codex needs finished page copy, section copy, headline options, subheadline options, or CTA copy for a website page, including requests like "write copy for this landing page", "rewrite this feature page", "improve this page copy", "headline help", or "CTA copy". Do not use it for strategic page briefs or page-strategy work; use page-brief-builder for that.

Assemble a concise locked website page brief from collected planning inputs, turning intake, research, SEO, positioning, conversion, copy guidance, and claims validation into exact instructions another LLM agent or human can execute without interpreting options. Use when Codex has the research inputs and needs to produce the final implementation brief for a new or updated web page. Do not use it to fill research gaps by guesswork, write the full page itself, or produce code.

Apply repo-local copy, hero, proof, objection-handling, and CTA rules to website page briefs. Use when Codex needs message hierarchy, exact H1, exact hero subheading, exact section headings, supporting-content modules, proof handling, or conversion-focused copy rules for a new or updated website page brief. Do not use it to write the finished page or to replace the broader positioning workflow.

Apply repo-local page-type, site-role, and structural rules to website page briefs. Use when Codex needs page-specific guidance for product pages, feature pages, landing pages, solution pages, comparison pages, help or FAQ pages, integration pages, or evergreen resource pages while preparing a new or updated website page brief. Do not use it as a substitute for live same-site analysis when relevant site pages are available.

Apply repo-local SEO, search-intent, internal-linking, structured-data, supporting-content, and on-page structure rules to website page briefs. Use when Codex needs search-aware guidance for a new or updated landing page, product page, feature page, help page, comparison page, solution page, integration page, or evergreen resource page brief. Do not use it as a full sitewide SEO strategy or standalone keyword-research workflow.

Define the messaging and positioning layer for a website page brief by brainstorming up to 3 viable page directions, choosing one direction or asking the user to choose, and then clarifying audience pains and motivations, value proposition, differentiators, proof points, objections, trust signals, tone guidance, and claims that require substantiation. Use when Codex needs strategic messaging guidance for a new or updated web page. Do not use it to draft the finished page or to replace claim validation.

Plan the search-intent and SEO contract for a website page brief by defining primary intent, secondary intents, keyword or topic cluster, exact title tag, exact meta description, internal links, structured-data decisions, supporting-content modules, and overlap risk. Use when Codex needs search-aware guidance for a new or updated product page, landing page, help page, comparison page, solution page, or evergreen page. Do not use it for sitewide SEO strategy, standalone keyword research, or final page copy.

Inspect the target website and comparable same-site pages to extract recurring structure, voice, CTA patterns, proof patterns, and keep-versus-improve guidance for a new or updated page brief. Use when Codex needs to align a new page with an existing site system or audit an existing page before rewriting its brief. Do not use it for competitor research or final brief assembly.

Give blog drafts a blunt, Gordon Ramsay-style editorial review from the target reader's perspective. Use when the user asks for a brutal review, blunt publish-no-publish feedback, or says things like "rip this apart", "be harsh", "judge this like Gordon Ramsay", or "tell me if this is AI slop", and Codex must pressure-test a full blog draft for repetition, dull structure, weak hooks, empty claims, bloated sections, or overall reading quality before publishing. Do not use this skill for LinkedIn posts, outlines, or factual verification.

Verify unstable or external claims in drafts using local research tools or equivalent web access. Use when a draft contains dates, names, numbers, public-company facts, product claims, sourced statements, or references to recent events that should be checked before the draft is finalized.

Verify cited, embedded, or recommended URLs in blog drafts using local research tools or equivalent web access. Use when a blog article contains source links, outbound links, citations, or recommended URLs that must be checked to confirm the page exists, is not a 404 or soft-404, and matches the expected content before publication.