lhm-project-hub

Create, classify, clean up, update, assign, discuss, complete, move, or otherwise mutate LHM BasicOps tasks. Use whenever a user or another LHM Project Hub workflow asks to write anything in BasicOps, including "create a task", "classify my tasks", "clean up Kristalyn's board", "give me the next five tasks to review", "add this to BasicOps", "assign this", "update the task", "mark it complete", or "add a discussion note". This is the mandatory shared BasicOps mutation boundary for all Project Hub skills; other skills may prepare project context but must route the final task payload and write through this skill.

Kick off a new blog/article content pipeline — intake, state file, BasicOps scaffold with backwards-scheduled milestones, client kickoff email, and handoff to the content engine. Use this when the user says 'blog kickoff', 'article marketing kickoff', 'start the blog engine', or 'content pipeline for [client]'. Follows references/kickoff-pattern.md. Delivery work itself belongs to lhm-content-engine:content-orchestrator, never this skill.

Prepare a review-only client meeting bundle from Fathom evidence. Use after a client meeting to draft the follow-up email, structured meeting record, and proposed client, goal, and project updates. This skill never writes the vault, creates Gmail drafts, sends email, or changes BasicOps; approved mutations run as separate operations.

Run LHM's resumable new-client onboarding workflow. Use when the user says 'client onboarding', 'onboard [client]', 'continue onboarding', 'where is onboarding up to', 'billing setup', 'strategy call', 'client access', 'tracking setup', or 'service kickoff'. Reads and updates the detailed, scope-aware Obsidian onboarding checklist first, then mirrors only five top-level phases and seven top-level checks to the BasicOps *Client Onboarding board: Payment & Billing, Client Contact & Strategy, Access Assets & Config, Service Kickoff, and Onboarding Complete.

Propagate a client data change across all client files. Use when a client's name, service offering, contact details, branding, or other core details have changed. Finds every reference in the client folder and updates them. Flags downstream strategic work needed. Triggers on: 'client changed their name', 'they rebranded', 'new contact', 'updated their services', 'client update', 'name change', 'Raise the Bar Psychology is now Raise the Bar Clinic'.

Generate a plain-language client update email after completing a task. Use this when the user mentions 'client update', 'update the client', 'email the client', 'client email', 'explain what we did', 'send a summary', 'client report email', or 'let the client know'. This skill takes the work just completed and turns it into a friendly, jargon-free email the client will actually understand.

Deliver completed LHM production artefacts from an approved worker staging location into the client’s registered Google Drive folder with exact metadata and content readback. Use whenever a Hermes, Claude or Codex workflow produces a report, brief, copy deck, audit, plan, export or other file that must be retained for a client; when Head of Production reaches durable delivery; or when a result exists only on a VPS, local path, Hermes workspace or Kanban attachment. This is a shared delivery capability, not a specialist content or publishing bot.

Capture and transfer a new website project for an existing LHM client from Michael to Kristalyn. Use when Michael says an existing client needs a website, website rebuild, website handover, project handover to KP, or asks to start the website flow without repeating client onboarding. Interviews Michael one question at a time, prepares a canonical Obsidian handover for confirmation, routes it to Kristalyn for acceptance, then hands the accepted project to website-kickoff.

Kick off a new GMB/local SEO optimisation cycle — intake, state file, BasicOps scaffold with backwards-scheduled milestones, client kickoff email, and handoff to the GMB hub. Use this when the user says 'GMB kickoff', 'kick off GMB', 'start GMB optimisation', 'Google Business Profile kickoff', or 'local SEO kickoff'. Follows references/kickoff-pattern.md. Delivery work itself belongs to lhm-gmb-hub:gmb-orchestrator, never this skill.

Read, create, or update the project-management/gmb.md file for a client's GMB optimisation cycle. Use this when the user mentions 'GMB status', 'where are we at with GMB', 'update GMB project', 'update rankings', 'GMB progress', 'what's left to do', 'mark as done', or wants to check or modify the project tracking document. Also used internally by all agents after completing tasks.

Adopt an established Google Ads client into LHM's governed monthly review system without treating it as a new campaign build. Use when Michael asks to onboard, adopt, migrate, prepare, or make an existing Ads client monthly-flow-ready, including a one-client pilot before portfolio rollout.

Kick off a new Google Ads campaign build — gates on conversion tracking, intake, state file, BasicOps scaffold with backwards-scheduled milestones, client kickoff email, and handoff to the Ads specialist. Use this when the user says 'Google Ads kickoff', 'kick off Google Ads', 'start the ads campaign', or 'Ads audit and setup'. Follows references/kickoff-pattern.md. Delivery work itself belongs to the lhm-marketing-hub google-ads agent, never this skill. This is the skill client-onboarding Phase 4 delegates Ads campaign build work to.

Create, verify, or repair the machine-readable client preflight Hermes needs before autonomous SEO, Google Ads, GA4, website, Drive, BasicOps, or knowledge work. Use for new-client onboarding, missing client access or identifiers, connector readiness checks, and workflows blocked with client_onboarding_required.

Identify the matching Obsidian AI Operations SOP and prepare, monitor, and verify a concise Hermes execution plan for an existing LHM BasicOps task. Use when someone gives Monica a natural-language production task such as creating website page copy, asks her to "plan this for Waylon", asks "where are we at with this task?" or "where are you at?", needs a CTO capability incident explained, or wants Waylon's completed work reconciled. This skill plans, reports, and checks specialist work; it does not execute the production work itself.

Kick off a new PPC landing page campaign — intake, state file, BasicOps scaffold with backwards-scheduled milestones, client kickoff email, and handoff to the WordPress hub. Use this when the user says 'landing page kickoff', 'kick off the LP campaign', 'start landing pages', or 'new PPC landing pages'. Follows references/kickoff-pattern.md. Delivery work itself belongs to lhm-wordpress-hub:landing-page-orchestrator, never this skill.

Read, create, or update the project-management/landing-pages.md file for a landing page campaign. Use this when the user mentions 'LP project status', 'landing page status', 'where are we at with the landing page', 'update LP project', 'create LP project', 'LP progress', 'what's left on the landing page', or 'landing page project management'. Also run this at the start of any LP workflow to ensure the project file exists.

Monthly per-client review engine with three modes. Use this when the user says 'monthly review', 'monthly wrap', 'monthly update for [client]', 'end of month review', 'prep for the [client] meeting', 'meeting prep', or 'account review'. Wrap mode (KP): walk through every open task/project/milestone, confirm done/carried/blocked, update all project files and BasicOps, draft the monthly achievement email, and generate the client report with Google Ads and SEO wins. Internal mode (Michael): 30-minute account review with anomaly flags. Pre-meeting mode: brief + timed agenda.

Process a client meeting's follow-up after client-meeting-email: update client state files, detect stale artefacts, create a compact Client Flow action register, route linked BasicOps tasks to owners' Inbox sections, and draft the team update. Reads saved meeting notes and wrap email, with Fathom/manual fallback. Explicit meeting owners win; otherwise current Obsidian staff profiles resolve a clear role match, with questions only for genuine ambiguity. Client-owed items route to Kristalyn. Use when the user says meeting wrap, process the meeting follow-up, work through the actions, post-meeting review, meeting follow-ups, or client call debrief. All BasicOps writes route through basicops-task-manager.

Quarterly per-client strategy review: pulls three months of GA4/Ads/GSC data plus the quarter's monthly reports, analyses goal progress and channel performance, and drafts the next 3/6-month campaign plan for Michael's approval. Use this when the user says 'quarterly review', 'quarterly strategy', '90 day review', 'next quarter plan', or 'campaign plan for [client]'.

Run substantive LHM client or internal work through the governed Hermes workforce from source intake to durable delivery, independent QA and human review. Use when Michael or an LHM team member asks Claude, Codex or another desktop agent to "run this through Hermes", execute a BasicOps task through Hermes, test the Hermes employee chain, supervise delegated AI work, or recover a Hermes-run task that stalls. Routes capability failures to the Hermes CTO with a persisted return point and resumes automatically after verified repair.

Hand a newly closed client from Michael or Marlon into LHM delivery. Use after a sale closes or when the user says 'sales handover', 'handover to KP', 'we signed a client', 'closed a deal', 'new client handover', or 'hand this client over'. Captures sales context in canonical Obsidian records, drafts Michael's client introduction, creates one client-level card on the BasicOps *Client Onboarding board assigned first to Josephine, adds seven top-level checks, and hands the detailed workflow to client-onboarding.

Kick off a new SEO engagement — intake, state file, BasicOps scaffold with backwards-scheduled milestones, client kickoff email, and handoff to the SEO specialist. Use this when the user says 'SEO kickoff', 'kick off SEO', 'start SEO for [client]', or 'SEO engagement start'. Follows references/kickoff-pattern.md. Delivery work itself belongs to the lhm-marketing-hub seo agent, never this skill.

Plan and run a personalised LHM weekly-to-daily work flow for Michael, Kristalyn, Aiya, Jaimee or Josephine. Use when an authorised person asks “what should I focus on this week?”, “what should I work on today?”, asks to review, clean up or triage all their BasicOps tasks or inbox, asks for a mini stand-up or WhatsApp-ready team update, asks specifically for business-growth or client-work priorities, wants to review or save their weekly priorities, or wants to configure their weekly/daily reminder time, timezone, channel, delivery mode, focus mode or priority limit. Read the person’s canonical Obsidian profile, verified BasicOps personal-board mapping, authorised project context and current weekly file; prepare a small realistic plan; save only after confirmation; and apply approved BasicOps mutations through basicops-task-manager with read-back verification.

Turn a rough request, client email, message, meeting action or idea into a complete internal team brief and approved BasicOps handoff. Use for any LHM user—including Michael, Josephine, Kristalyn, Jaimee or Aiya—when they say "brief Aiya", "brief AR", "brief Jaimee", "brief Kristalyn", "brief Michael", "brief Josephine", "brief Chris", "hand this to the team", "create a brief", "delegate this", "turn this email into a task", or give feedback that a prior brief was missing context, access, a URL or another requirement. Reads requester, client, assignee and project context; asks one material question at a time; checks access, dependencies, evidence, authority, completion and review; then routes the approved task through lhm-project-hub:basicops-task-manager. Captures controlled person-, client- and process-level handoff learning in the Obsidian Brain.

Keep the visible BasicOps assignee aligned with Ted's active ownership and verified human handoffs. Use on every Ted task event that begins work, pauses for another owner, or completes.

Kick off a new website build (WordPress or Astro) — intake, state file, BasicOps scaffold with backwards-scheduled milestones, client kickoff email, and handoff to the WordPress hub. Use this when the user says 'website kickoff', 'kick off the website', 'start the website project', 'new website for [client]', or 'begin the site build process'. Follows references/kickoff-pattern.md. Delivery work itself belongs to lhm-wordpress-hub:website-build-orchestrator, never this skill.

Coordinate website project status and stage handoffs across Obsidian and BasicOps. Use when a user asks where a website project is at, what happens next, or asks to brief, assign or hand off Astro, WordPress, Decap, design, copy, development, SEO, QA or go-live work.

Read, create, or update the project-management/website.md file for a full WordPress or Astro website build. Use this when the user mentions 'WP project status', 'Astro project status', 'where are we at with the website', 'update website project', 'create the website PM doc', 'website progress', 'what's left on the build', or 'website project management'. Also called by phase agents after task completion to mark off checkboxes, and by wp-start at session start to detect current state.