the2hourclo/ai-employee-builder

Writing employee · Explain an objection, belief, or unfamiliar idea through a fair parallel that helps the reader reach their own conclusion without trapping them. USE WHEN user says 'write an agreement analogy', 'write one fair analogy', 'fair analogy', 'price objection', 'find an analogy for this objection', 'explain this belief with an analogy', 'analogy for my FAQ', 'bridge this objection', or 'use a parallel example'. Runs in fresh context to test fairness. Do NOT use for full campaign or offer copy -> copywriter; offer diagnosis -> offer-clarity; general teaching metaphors unrelated to selling -> the relevant writing skill.

Builder employee · The free introductory AI Employee Map helps owners assess AI readiness across four levels (Manual → Basic Digital Assets → Integrated → AI-Powered, the Business Owner's AI Playbook ladder) and identify a first AI opportunity. USE WHEN user explicitly says "ai employee map", "find AI opportunities", "where can I use AI", "ai readiness", "what level is my business", "am I ready for AI", pastes their Business Owner's AI Playbook results ("Run my AI Employee Map…"), or asks for the free intro map. Operational business diagnosis routes to business-x-ray; post-map build guidance routes to roadmap.

Writing employee · Apply behavioral science principles from Chase Hughes' Behavior Ops Manual to any content. Diagnose missed persuasion triggers, enhance drafts with specific techniques, or look up principles by category. 290 principles across 10 categories. USE WHEN user says 'behavioral science', 'behavior ops', 'apply behavioral lens', 'check persuasion', 'enhance with psychology', 'what behavioral principle', 'why isn't this landing', or when any content needs a behavioral science audit.

Builder employee · Install and maintain the file system AI employees navigate. Builds one canonical BUSINESS-MAP.md world model; department folders with neutral DEPARTMENT.md sources and generated AGENTS.md adapters that both Claude and Codex can use; client records; shared system records for CRM, email, Drive, Notion, and other tools; a normalized client-system relationship ledger with backlinks instead of duplicated tool setup; live-data routing with verified IDs; safe migration, tidy, and routing verification. USE WHEN user says "set up my business OS", "organize my workspace", "map my clients", "connect my CRM", "connect my data sources", "make this work in Claude and Codex", "make this workspace work in both Claude and Codex without duplicating the business map", "AGENTS.md", "CLAUDE.md", "my AI can't find anything", or "where does my live data live". Do NOT use to diagnose business processes or draw opportunity maps; use business-x-ray for that.

Builder employee · Operational Business X-Ray: map, diagnose, and optimize how the business runs through progressive visual analysis. Creates Business Maps, Bow-Tie Funnels, Process Swimlanes, a System Connection Map, and a future-state Operating System Map of connected AI Employees and tools. ALWAYS USE for 'business x-ray', 'x-ray my business', 'map my business', 'diagnose my business', 'audit my business', 'find the bottlenecks', 'where am I the bottleneck', 'map my operations', 'where does my business break without me', 'score my business assets', 'leverage score', or a visual operational diagnosis. Folder/file scaffolding uses business-os when available and a lean mapped fallback when locked; an explicitly requested free intro AI-readiness map routes to ai-employee-map; post-diagnosis build guidance routes to roadmap.

Setup employee · Verify and repair this AI Employee Builder setup — connector, license plan, surface-appropriate workspace folders, onboarding state, and the managed workspace-instructions block — then offer consent-gated fixes. USE WHEN user says 'check my setup', 'verify my setup', 'is my setup ok', 'is everything connected', 'something seems broken', 'my skills stopped working', 'fix my setup', 'setup health check', 'am I connected', 'why isn't this working', or another skill or message told them to run a setup check. Safe to run any time — it changes nothing without an explicit yes.

Writing employee · Write CTAs that continue the conversation instead of interrupting it. Three-element structure (concept link, curiosity bridge, soft CTA) that makes the offer feel inevitable, plus the 7-Element Close checklist (Bridge, Value Stack, Price Reveal, Risk Reversal, Objection Handling, Urgency, Decisive Action) for full paid-offer closes. USE WHEN user says 'write CTA', 'improve this CTA', 'CTA feels generic', 'make the CTA better', 'contextual CTA', 'the offer feels plugged in', 'write the close', 'check the close', 'closing section', '7 elements of a close'.

Writing employee · Campaign and offer copywriting orchestrator. Builds campaign strategy, message foundations, offer documents, email-linked offer letters, VSL-topped mini landing pages, campaign email sequences, welcome emails, VSLs, paid live webinar/workshop pages, and Game Worth Playing documents. USE WHEN the user says 'sales campaign', 'offer document', 'send the offer by email', 'mini landing page', 'VSL at the top', 'promotion package', 'campaign email sequence', 'welcome email', 'write a welcome email', 'video sales letter', 'turn my offer into a video sales letter', 'webinar sales page', 'workshop page', or 'Game Worth Playing'. Do NOT use for product or sales bullets (product-bullet-points), offer diagnosis (offer-clarity), objection analogies (agreement-analogy), daily/editorial email (write), lifecycle sequences (email-os), generic website copy (copywriting), page diagnosis (cro), headline-only work (headline), or external deployment without separate approval.

Builder employee · Navigate a real branching taste or judgment decision instead of averaging options: which avatar, angle, positioning, hook, offer frame, or thumbnail concept. USE WHEN user says 'build a decision tree', 'map the options', 'map the decision', 'which option is best', 'help me decide' for a creative choice, or when a chain reaches a fork with two or more legitimate branches. Record each human pick and reason, then pass only the chosen branch downstream. Do NOT use when there is no genuine fork among alternatives.

Writing employee · Define or sharpen a personal/business brand through a guided interview, then produce two working references — a one-page positioning spine and a False Beliefs Document. Runs the brand questions one or two at a time, open-question-first then a proposed draft to react to, and holds every answer against the branding principles. USE WHEN the user says 'define my brand', 'brand worksheet', 'sharpen my positioning', 'who am I for', 'what's my pairing', 'what do I stand against', 'find my unique edge', 'work on my brand', or BEFORE creating content when no brand is defined yet. Do NOT use to write a finished piece (that's the content skills), to set up or calibrate voice files/voice samples (that's setup-content-employees), to map operations (that's business-x-ray), or to render finished visuals.

Writing employee · Render legible hand-drawn 'Excalidraw whiteboard' diagrams, graphs, and charts as PNGs from hand-authored HTML/SVG — white background, real Excalifont, an SVG wobble filter on SHAPES ONLY so text stays crisp, color-by-meaning accents. The go-to recipe for email graphs, newsletter diagrams, process maps, and video teaching slides. USE WHEN user says 'make a graph for my email', 'excalidraw diagram', 'whiteboard graphic', 'hand-drawn diagram', 'diagram this', 'make a chart', 'draw a process diagram', 'visualize this as a graph', 'teaching-slide graphic', 'sketch this concept on a board', or wants a clean hand-drawn diagram/graph for a video slide, email, newsletter, carousel slide, or canvas. Do NOT use for: photoreal/AI-generated imagery (outside this plugin's scope), or a full multi-slide social carousel (→ carousel — though its individual diagram slides can be drawn HERE).

Writing employee · Generate and review email subject lines, carousel covers, landing-page heroes, offer names, and landing-page section headers from validated direct-response shapes using demand matching. USE WHEN user says 'write a headline', 'subject line', 'email subject', 'carousel cover', 'LP hero', 'section header', 'sales-page headers', 'make this headline better', 'does this convert', 'name this offer', or 'fascination', and whenever another writing skill needs a headline. Landing-page section headers always route here. Do NOT use for body openings → write-hook; full argument structure → writing-logic; claim tightening → precision-principle; perspective discovery → perspective-shift; or the full email/carousel → write or carousel.

Setup employee · Import and install skills from external sources into your workspace. USE WHEN user says 'install this skill', 'import a skill', 'add this skill pack', 'install from github', 'set up this skill', 'load skill from', 'bring in this skill'.

Writing employee · The selling philosophy beneath every CTA, offer, and promotional line — invite, don't push; recognition, not manipulation — plus the premium framing shifts (reserve not "lock in", included resource not "bonus"). USE WHEN user says 'apply invitation lens', 'make this less salesy', 'this feels pushy', 'soften the sell', 'invitation framing', 'invite don't sell', 'less aggressive CTA', 'sounds too salesy', or when any selling/persuasion copy needs its relationship-to-the-reader checked. Do NOT use to WRITE a CTA from scratch (→ contextual-insights-cta) or a hook (→ write-hook) — this is the LENS those skills apply.

Builder employee · Create subagents for Claude Code. USE WHEN user says 'create an agent', 'make an agent', 'add an agent', 'new agent for', 'build an agent', 'meta create agent', 'I need a specialist for', 'delegate this to', 'autonomous worker for'.

Builder employee · Create slash commands for Claude Code. USE WHEN user says 'create a command', 'make a command', 'add a command', 'new slash command', 'build a command for', 'I need a shortcut for', 'make a quick action', 'automate this action'.

Builder employee · Create hooks for Claude Code automation. Covers ALL 14 hook events, ALL 6 hook locations (settings.json, frontmatter, plugins), ALL 3 hook types (prompt, command, agent), async hooks, input modification, and decision control. USE WHEN user says 'create a hook', 'add a hook', 'meta create hook', 'automate when', 'trigger when', 'run automatically', 'after writing', 'before commit', 'validate output', 'add automation to skill'.

Builder employee · Add, configure, build, secure, migrate, or distribute MCP servers across Claude Code, Cowork, desktop, web, and other MCP hosts. USE WHEN user says 'add an MCP', 'connect to', 'add integration', 'setup MCP', 'connect MCP server', 'configure MCP', 'build an MCP', 'create MCP server', 'remote connector', or 'MCP OAuth'.

Builder employee · Package skills into a Claude Code plugin for distribution. Creates plugin folder structure, plugin.json manifest, and prepares for publishing. USE WHEN user says 'create a plugin', 'package these skills', 'bundle skills into a plugin', 'make a plugin from', 'publish plugin', 'plugin from skills'.

Builder employee · Creates, validates, tests, updates, and hardens agent skills for Claude or Codex; chains them into Skill Systems (AI Employees); chooses the artifact an outcome needs; and applies domain-invariant contracts to stateful or side-effecting employees. Use when someone describes an OUTCOME ('review emails weekly', 'I do this manually'); asks to build ('create a skill', 'build an AI employee', 'automate this operation', 'make it decide like me'); asks to change an existing skill ('update skill X', 'add a rule'—always load this first); asks to protect business state ('add ontology', 'enforce invariants', 'stop duplicate actions'); reports symptoms ('it ignores its rule', 'said it did it but did not', 'make it production-grade'); or wants to schedule, validate, test, or audit skills. A skill that MISFIRED and needs a patch routes to retrospective. Do NOT use for workspace structure, BUSINESS-MAP.md, AGENTS.md, or shared Claude/Codex adapters; use business-os.

Writing employee · Apply the ABT (And, But, Therefore) narrative framework as a writing lens. Builds narrative backbone before writing or diagnoses why existing content isn't landing. USE WHEN user says 'apply abt', 'narrative lens', 'build my abt', 'find my hook', 'find my but', 'what's my tension', 'analyze my content', 'check my narrative', 'is this narrative', 'strengthen my hook', 'narrative gym', 'abt framework', or before starting any content piece that needs a clear hook and structure.

Writing employee · Decide, diagnose, and independently review offers. USE WHEN user says 'roast my offer', 'clarify my offer', 'why isn't this selling', 'reposition this offer', 'what should I sell', 'what offer to sell', 'I do not know what offer to sell', 'three pillar exercise', 'run the rulebook', 'check this low-ticket offer', or 'offer QA'. Runs in fresh context to avoid self-grading. Do NOT use to write campaign assets or offer documents → copywriter; generic website copy → copywriting if available, otherwise return an evidence-backed page-copy brief for the user's installed producer.

Setup employee · First-run setup for the ai-employee-builder plugin. Scaffolds the authoring folders (.claude/skills|agents|commands|hooks), writes a workspace CLAUDE.md with skill routing, and maps the business into department folders + BUSINESS-MAP.md using the full Business OS when available or a lean built-in fallback when locked. Then it hands off to the tracked journey, whose first checkpoint is the Business X-Ray. USE WHEN user says "onboard me", "set me up", "get me started", "start my workspace", "bootstrap my workspace", "first time setup", "build my workspace", OR when you detect a fresh workspace (no .claude-state/onboarding-progress.json) and the user has just installed the ai-employee-builder plugin.

Builder employee · Create an evidence-labelled Pareto chart and 10/90 resource-focus brief for a business owner. USE WHEN user says 'make a Pareto chart', 'run an 80/20 analysis', 'run a 90/10 analysis', 'find my highest-leverage activities', 'which activities produced most revenue or qualified leads', 'what should I focus on', 'where should I use AI', or 'I have no data but need clarity'. Do NOT use for a full business map or process diagnosis (use business-x-ray) or a recurring KPI dashboard (use metrics-tracking).

Writing employee · Find and charge the ONE perspective shift inside a transcript, article, newsletter, raw idea, or brand-positioning source. Produces scoped shift cards with old/new belief, content angle, and dream/nightmare stakes for any short-form format. USE WHEN user says 'find the perspective shift', 'what's the shift here', 'extract the shifts', 'what's the angle', 'turn this source into short-form ideas', or hands over a source to repurpose for cold traffic. Do NOT use for a finished rendered piece (route to an installed destination producer; if none is available, return a format-neutral production brief), a hook with no shift work (→ write-hook), or a full long-form argument (→ writing-logic).

Writing employee · Wording sharpener for ONE claim, promise, or headline at a time — the Meaning Test (would two people read it the same way?), Word Force (use the lowest-force word that does the job), and precision language rules (kill qualifiers, uncertainty markers, two-part negations). USE WHEN user says 'meaning test', 'word force', 'tighten this claim', 'make this specific', 'make this measurable', 'precision check', 'is this claim clear', 'this sounds hypey', 'lower the intensity', or when an offer/CTA/headline/promise needs its wording sharpened. Scope: ONE sentence at a time — hand anything draft-sized to the writing chain.

Writing employee · Turn verified product features, deliverables, curriculum, course modules, or bonuses into specific outcome-focused sales bullets. USE WHEN user says 'write product bullets', 'write bullet points', 'product benefits', 'create sales bullets', 'turn these features into benefits', 'verified course modules', 'outcome-focused sales bullets', 'what you get bullets', 'landing page bullets', 'lead magnet benefits', or 'workshop outcome bullets'. Do NOT use for a full campaign or offer document -> copywriter; full website pages -> copywriting if available, otherwise return a verified page-copy handoff brief; headline-only work -> headline if available, otherwise return evidence-bound headline directions; offer strategy or diagnosis -> offer-clarity.

Support employee · Send Rashid a problem report from inside Claude when AI Employee Builder isn't working: setup or sign-in fails, a skill errors or gives a clearly wrong result, or a step doesn't match what the member sees. Drafts the report in plain words, shows the exact text, and sends only after a yes. USE WHEN user says 'report a bug', 'report a problem', 'report this', 'tell Rashid', 'send this to support', 'this is broken and the setup check didn't fix it', 'how do I report this', or a check-setup repair didn't work. Do NOT use for a first setup check (use check-setup).

Builder employee · Capture learnings from skill usage and propose SKILL.md improvements - the door for patching an OBSERVED misfire. USE WHEN user says 'retrospective', 'this skill messed up', 'fix this skill', 'heal this skill', 'the skill got it wrong', 'that run was wrong', 'capture what went wrong', 'skill-level post-mortem', or when a skill just produced wrong output and the user wants its instructions patched. Do NOT use for a deliberate change with no observed failure - 'update skill X', 'add a rule to X', 'improve this skill' route to meta-create-skill. Making a skill reliable going forward (gates, enforcement, hardening) is also meta-create-skill's job, not a retrospective.

Builder employee · The EXCLUSIVE owner of the AIEB 7-Day Challenge—its scorecard, fresh test, completion report, and credit-first flow—and the build-roadmap/triage front door. ALWAYS USE for 'start my Challenge', 'continue my Challenge', 'Challenge progress', 'create my scorecard', 'run my fresh test', 'generate my completion report', 'apply my Challenge credit', 'what's next', 'what should I build next', 'where am I', 'roadmap', 'continue building', 'I keep doing X by hand', or 'I don't know what to build'. Challenge mode reuses saved intake and tracks seven checkpoints. Ladder mode tracks post-onboarding AIEB progress. Triage mode routes plain-language pain to the right skill, system, harness, MCP, hook, or command builder. Also use for repeated manual work when the artifact is not named. Do NOT use for first-run setup (onboard), an operational business diagnosis outside an active Challenge (business-x-ray), or when the exact artifact is already named (use its meta-create builder).

Writing employee · Universal teaching framework (Show → Extend → Expose → Direct) for explaining any concept in visuals, text, slides, video, or docs. Three modes — CREATE, DIAGNOSE, REWRITE. USE WHEN user says 'explain this concept', 'explain this so a beginner gets it', 'explain it simply', 'teach this', 'break this down', 'make this clear', 'SEED this', 'apply SEED', 'how do I explain X', 'this needs to be clearer', 'check if this makes sense', 'diagnose this content', 'find the gaps', 'would a reader understand this', 'SEED diagnose', 'SEED check', or when any concept needs to be taught to an audience who doesn't already understand it.

Securely connect, reconnect, update, or resume AI Employee Builder through its remote connector, and configure its private local improvement ledger. USE WHEN the user says "set up AI Employee Builder", "connect AI Employee Builder", "set up AIEB", "connect AIEB", "reconnect AIEB", "activate AI Employee Builder", "finish AIEB setup", "update AIEB", "enable my local improvement ledger", "disable my local improvement ledger", or has just installed the plugin.

Setup employee · First-run onboarding for the content employees. Sets up everything the writing fleet needs on this machine — voice samples, brand positioning doc, visual identity (brand colors + fonts for your diagrams and graphics), output folders, and a routing map in CLAUDE.md — through a short guided interview. USE WHEN user says 'set up my content employees', 'onboard my writing employees', 'set up my voice', 'calibrate my voice', 'my voice files', 'set my brand colors', 'customize how my diagrams look', 'my visual style', 'get started with the writing skills', 'the write skill says my voice files are missing', or right after the writing skills switch on with an AI Employee Builders membership. Safe to re-run any time — it updates only what you approve and never overwrites your work. Also USE WHEN user says 'calibrate my voice', 'calibrate my voice files', 'set up my voice samples'.

YouTube employee · Build or inspect an editable Excalidraw storyboard made from finished slide images. Arranges PNG slides as spine, narrative-act columns, and teaching-beat rows; preserves each slide's real aspect ratio; creates a bird's-eye preview; or reads an existing image-based canvas into an overview and structured summary. USE WHEN the user says 'build a storyboard canvas', 'arrange these slides on a board', 'put this deck in Excalidraw', 'read this canvas', 'show the canvas arrangement', or needs an editable whiteboard deck. Do NOT use to decide visual coverage, render slides, author diagram art, or create a flat presentation PDF.

YouTube employee · Assisted thumbnail judgment for choosing a high-impact visual story before rendering. Deconstructs relevant references, creates three materially different thumbnail visual stories, rejects objectively weak concepts, explains close calls, records the human's selection and reason, and produces a renderer-neutral concept brief. USE WHEN the user says 'analyze this thumbnail', 'why does this thumbnail work', 'thumbnail ideas', 'three thumbnail visual stories', 'choose a thumbnail concept', 'design a thumbnail concept', 'whiteboard thumbnail', 'visual metaphor', or needs a thumbnail that communicates in one second. Do NOT use for a complete YouTube production package (youtube-strategy), image rendering alone, or post-publish analytics.

YouTube employee · Plan visual explanations before rendering. Chooses each frame's shape from the relationship in the content, orders frames so each earns the next, maps proof and continuity, and produces a single Visual Brief or a sequence-level Visual Coverage Map. USE WHEN the user asks to plan visual coverage, says 'plan the visuals', 'how should I show this', 'lay out this slide', 'sequence this deck', 'the deck flows wrong', 'map visual coverage', or 'add proof'. If the user asks to turn an approved YouTube package into a narrated whiteboard deck, choose youtube-strategy; this Skill plans coverage but does not build that complete YouTube deliverable. Do NOT use to generate images or render finished artifacts; delegate those to the chosen renderer.

YouTube employee · Transform a source webinar or masterclass into a coherent, annotated, 90%-visual Excaligraph teaching deck and compile the finished slide collection. USE WHEN user says 'turn this into a webinar masterclass', 'review this masterclass top to bottom', 'make these slides visual', 'old way new way slides', 'make a 90% visual webinar', 'compile all these slides', 'build an annotated Excaligraph deck', or 'simplify this presentation'. Do NOT use for funnel copy or registration pages.

Writing employee · The Whale Bait lens — turn a content idea or a perspective shift into content that attracts the few RIGHT buyers (whales) instead of a broad crowd (fish), and generate fresh whale-bait ideas from the brand. Diagnoses fish-vs-whale and value-vs-insight, then charges the idea with the brand's Plan/Code/Ideas/Proof. USE WHEN user says 'make this whale bait', 'whale-bait this', 'is this fish bait', 'will this attract whales', 'better leads not more leads', 'give me whale bait ideas', 'content ideas for buyers', 'this attracts the wrong people', 'make this attract buyers not browsers', or hands over an idea / perspective-shift card to sharpen for the right audience. Runs AFTER perspective-shift (charges the shift it scoped) and BEFORE the format skill (write / carousel / reel-creator). Do NOT use to: render a finished piece (→ that format's skill), find the shift itself (→ perspective-shift), tighten a single claim (→ precision-principle), or write a full argument (→ writing-logic).

Writing employee · Write newsletters, long-form articles, daily emails, broadcast emails, and general one-off emails. USE when the requested deliverable is a newsletter, article, long-form post, daily email, broadcast email, or general email draft. Scope is editorial prose from idea to finished draft. Any long-form YouTube asset, including a YouTube opening or hook, belongs to youtube-strategy. Commercial product and offer copy is outside scope. Formatting-only work on an existing draft is outside scope. Planning-only and voice-setup jobs are outside scope.

Writing employee · Write non-YouTube hooks and short-form CTA openings. One gated procedure (the PSF Hook Scaffold) voiced through five accents — 5-Beat Claim, Empathy, Framework, Story, PADAI Offer — as either the opening of a longer piece OR a complete short-form CTA piece. USE WHEN user says 'write a hook', 'write the opening', 'hook for this', '5-beat hook', 'carousel hook', 'proof slide', 'evidence structure', 'opening for this piece', 'slide 2', 'grab attention', 'short-form CTA', 'PADAI', 'VSL opener', 'offer email opener', 'sales email opener', 'one-day open', 'launch email opener'. Do NOT use for a long-form YouTube opening, title, or thumbnail; a full announcement post; building a carousel; reel ideation or a full reel; a full sales email/sequence or sales page; or full argument structure. Route those jobs to their installed owners — youtube-strategy, write, carousel, reel-creator, copywriter, or writing-logic — when available; otherwise return a production-ready handoff brief.

Writing employee · Format an already-written draft for a publishing platform. ALWAYS USE when the user says 'format this for Substack', 'format for Substack', 'format this newsletter', 'apply formatting', 'make this publishable', 'format carousel', 'carousel formatting', 'Substack formatting', or asks only for platform-specific headers, bold, italics, blockquotes, spacing, or visual rhythm. This skill formats existing prose; it does not create the draft.

Writing employee · Make AI-generated text sound human. Scrub AI tells (em-dashes, staccato, filler-deficit, announcer scaffolding, And/So/Now/Because openers, billboard proclamations), enforce active voice, and check deliverable integrity. Works standalone on any text. USE WHEN user says 'humanize this', 'clean up AI-isms', 'make this sound human', 'voice cleanup', 'remove AI patterns', 'sound more natural', 'check for AI tells', 'fix the voice', or when any writing needs voice cleanup after drafting. Do NOT use to install the creator's personal voice - 'make it sound like me', 'install my voice' route to writing-voice (humanize scrubs AI tells; voice install is a separate pass).

Writing employee · Argument scaffolding system. Takes an idea (or a source) and sequences it into a Perspective-Shift scaffold — one protagonist's Old→New journey across labeled beats, one takeaway each, ordered to meet the reader where they are and break the idea down progressively. Build the scaffold, then QA it for logical integrity before any prose. USE WHEN user says 'plan argument', 'scaffold this', 'argument structure', 'plan the newsletter structure', 'sequence these ideas', 'logic check my writing', 'check my logic', 'expand this idea', 'map my ACTs', or when building the argument structure for any content piece before writing prose.

Writing employee · Install your teaching voice. PRIMARY TEST — every sentence must sound like someone speaking and pointing at things, not a billboard or press release. Then point at named things, run What → Why → Takeaway on every teaching moment, and replace every abstract noun with a specific named thing. The Spoken-and-Pointing test runs FIRST on every sentence — only after that does the Circle Test, Verb Test, and Teaching Triad apply. USE WHEN user says 'voice check', 'install voice', 'install teaching voice', 'make it sound like me', 'scan for vagueness', 'point at things', 'name the gap', 'pointing voice', 'less announcy', 'sounds like a billboard', 'too staccato', when writing prose from a writing-logic scaffold, or to install the teaching-on-a-board stance on existing prose. Also USE WHEN user says 'this reads vague', 'too vague - point at things'.

YouTube employee · The exclusive owner of every long-form YouTube job, from strategy through record-ready production. USE WHEN a request names YouTube, including 'audit my YouTube channel', 'write the opening hook for my long-form YouTube video', or 'turn this approved YouTube package into a narrated whiteboard deck'. Also handles channel audits, declining-view diagnosis, breakout research, next-video ideas, positioning, title-thumbnail promise pairs, scripts, video slides, draw-along decks, optional visual coverage, and production handoff. Choose this over general writing or visual-planning skills whenever the requested deliverable is a long-form YouTube asset. Do NOT use for non-YouTube hooks (write-hook), short-form reels (reel-creator), post-publish metrics reporting without a strategy diagnosis (metrics-tracking), or publishing without approval.