onehorizonai

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.

Draft release notes for external customers, internal teams, or stakeholders. Use when asked to "write release notes", "draft changelog", "prepare what's new", "summarize this release", or "announce this version". Defaults to external customer-facing copy that excludes internal jargon. Optionally pulls shipped work from One Horizon. Requires One Horizon MCP when sourcing content from workspace data.

Draft a structured initiative brief for roadmap-first planned work in One Horizon. Use for "write an initiative", "draft an initiative brief", "plan this initiative", or "scope this roadmap work". Requires One Horizon MCP.

Create a One Horizon bug or feature request when work type is clear. Use for "log a bug", "file a feature request", or "report this issue". Prefer one-task-management for ambiguous requests. Requires One Horizon MCP.

Turn open bugs into prioritized triage notes. Use when asked "prepare bug triage", "summarize open bugs", or "prioritize defects for review". Requires One Horizon MCP.

Create a One Horizon Todo or roadmap initiative when the user asks for that exact work type and the scope is clear. Prefer one-task-management for ambiguous or multi-step operational requests. For bugs or feature requests, use one-report-issue instead. Requires One Horizon MCP.

Resolve One Horizon team, member, workspace, and identity context. Use when asked "who is on my team", "find Jane's user ID", "which workspace am I in", "list my workspaces", or "who am I". Prefer one-task-management when team or workspace lookup is only one step in a larger operational request. Requires One Horizon MCP.

Fetch the full details for one known One Horizon task when the task ID is already available and the user needs exact task context. Prefer one-task-management when details are only one step in a larger operational request. Requires One Horizon MCP.

Turn current work into handoff notes a teammate can continue from. Use when asked to "write handoff notes", "prepare transition docs", or "document my current ownership". Requires One Horizon MCP.

Compare a code change against the existing codebase to check pattern alignment. Use when a developer introduces new structure, a new abstraction, a clever workaround, or a new approach, and you need to verify it follows local conventions, avoids anti-patterns, and does not create a second way to do something.

Review a coding or implementation plan against the existing architecture before code is written. Use when a developer shares a plan, asks "does this plan make sense?", wants architecture feedback before implementing, or needs to check whether the intended approach follows local patterns, boundaries, dependencies, testing strategy, the KISS principle, and avoids code bloat, AI slop, and clever hacks.

Start here when you don't know where to start. Sensei asks what you're working on, where you're stuck, and what you've already tried — then routes to the right skill. Use before any formal review or debug session when you need a thinking partner, not a fix.

Evaluate what the tests actually prove and what they miss. Use when reviewing a PR's test coverage, when a developer says "I wrote tests", or when you want to challenge the developer to reason about test quality — not just test quantity.

Run a post-merge or post-session reflection to capture what was learned and identify what to practice next. Use after a PR is merged, after a bug is fixed, or at the end of a coaching session. Keep it short enough to review in two minutes.

Analyze code for responsibility, boundary, abstraction, code-bloat, and duplicated-knowledge problems. Use when a function or module seems to be doing too many things, when the same business rule appears in multiple places, when the developer asks about SRP, DRY, KISS, code smells, or whether code is too complex, or when reviewing whether a split or abstraction is justified.

Review a code diff or file for correctness, security risks, AI slop, code smells, pattern mismatches, and missing verification — in teaching mode. Use when a developer asks for a code review, "look at this diff", "review my PR", or wants to know whether code is simple, maintainable, or too hacky.

Help a developer reason through a design decision by naming options, costs, constraints, reversibility, and what would change the decision. Use when a developer says "should I use X or Y", "help me decide", "what's the tradeoff", or "is this the right architecture". If the decision claims architecture fit, read the closest local precedent before judging. Do not decide for the developer.

Paladin's security context dispatcher. Use when no specific Paladin skill is requested, when the user asks for a security review but the mode is unclear, or when Codex should inspect git state and route to code review, PR review, broad security review, repository audit, setup, or vulnerability mitigation.

Review changed code for high-confidence security vulnerabilities. Use for uncommitted local changes, staged changes, branch diffs, pasted diffs, or code security review before a PR when the task is focused on the diff rather than a broad repository audit.

Orchestrate security review for pull requests and PR diffs. Use for GitHub PR security review, inline PR comments, previous review-thread follow-up, and final PR security decisions; delegate core changed-code analysis to paladin-code-review.

Produce backlog-style repository security audits and weekly security metrics. Use for security backlog creation, recently merged PR sweeps, weekly reporting, management metrics, recurring pattern review, and prioritized audit items; use paladin-security-review for broader one-off repo sweeps or current advisory checks.

Run a broad defensive security review of a local repository, including changed-code review, repo sweep, misuse-case analysis, dependency and advisory checks, public zero-day claim evaluation, and known-exploited vulnerability review. Use for security sweeps, broad audits, current vulnerability checks, or requests to check whether a repo is exposed.

Turn a known vulnerability, CVE, CWE, dependency alert, scanner result, audit finding, or PR security finding into concrete mitigation steps and regression tests. Use when the user asks how to fix, remediate, patch, reduce risk, or validate a security issue.

Configure Paladin for a repository by creating or updating PALADIN.md. Use when the user asks to set up Paladin, initialize Paladin config, configure review actions, choose One Horizon/Linear/Jira/email/custom destinations, or prepare a repo for Paladin security review.