MoxyWolfLLC/moxywolf-plugins

Operationalizes the 4D AI Fluency Framework (Delegation, Description, Discernment, Diligence) for content production. The single front door for every MoxyWolf blog property: a targets/ registry (FrontierFounder wired; STIGViewer, moxywolf-website, prfaq register-only) drives canonical URL, JSON-LD, frontmatter, and hero per destination, and every post picks a publishing target + a pillar (new or existing) before drafting — the hub-and-spoke methodology, with /blog-pillar to manage pillars and their linking maps. /blog-init is writer-friendly: two folder picks, author name, hero vibe, optional live URL. /blog-voice runs a self-contained 8-question voice interview and writes a per-writer voice profile; multi-voice supported. /blog-start mounts the two directories and surfaces in-progress and unpublished pieces. /blog-pipeline runs the 4-phase pipeline: 30-day discourse sweep across reddit/X/HN/Substack/Facebook/Quora/podcasts/academic with a /council:deliberate synthesis pass, verified bibliography via bibtex-builder, draft in the writer's voice via research-pipeline/content-writer, two-tier anti-AI-slop pass, then a nonce-bound Release Owner Gate (100-point rubric). On sign-off, the pipeline ends — social derivatives are opt-in. /blog-social derives any subset of: LinkedIn Post + first-comment (feed Post 1,300-2,500 chars sweet spot, 2,900 hard cap under LinkedIn's 3,000-char ceiling, zero body links; companion first-comment file with the fixed "If you want to do your own research…" opener, the blog URL, and the 2-3 sources the Post quotes inline), LinkedIn Article (optional long-form, separate selection), Twitter/X (5-10 post thread with ≤280-char per-post hard cap, script-enforced), Facebook (single 300-500 char post with body-inline link). One voice profile, per-platform register shifts (Twitter compressed; Facebook warmer; LinkedIn professional; first-comment voice-off and utilitarian). /blog-publish ships a signed post — the writer never types a git command. Implements the Release Owner Gate from MoxyWolf's Beyond the Prompt whitepaper.

End-to-end academic content pipeline: BibTeX theme mapping, perspective and voice capture, Academia.edu formatting, structure planning, iterative drafting, bibliography generation, and a 10-phase professor critique. Voice-first — voice and formatting are fixed before drafting, not retrofitted.

MoxyWolf analytics plugin — read-only reporting across data sources, one command per source. Ships the google-analytics command (GA4 Data API via a service account) with generic traffic reports plus Lens-Test campaign reports: acquisition by channel, first-touch signup source, custom-dimension segment (e.g. RPO vs non-RPO), and a one-shot markdown scoreboard with week-over-week for the Friday read. Built to grow — Microsoft Clarity, Ahrefs, PostHog, and others can be added as their own commands. Credentials come from the environment, never hardcoded; GA4 covers the acquisition end while the conversion verdict stays in PostHog. v0.1.0.

Build and enrich BibTeX bibliographies with AI-generated abstracts from URLs or uploaded .bib files.

Generate MoxyWolf monthly board deck from LivePlan, GA4, Taskade, and GitHub data.

Composio integration for Cowork. Teaches Claude to use Composio's Tool Router — 1000+ app toolkits through a session-based MCP connector — for apps with no native connector. Native MCPs stay first; Composio is the reach layer.

Multi-model AI deliberation with vault-aware institutional memory — structured consensus from multiple LLMs with self-learning routing, self-improving prompts, and bidirectional Obsidian vault integration.

Energy-aware personal operations system with Inbox Intelligence and Fitness Coach. Combines Apple HealthKit/Oura (via Health Auto Export), Google Calendar, Gmail, Google Drive tasks, and an Apple-Health-aware daily workout coach.

Framework-specific development best practices for React, Next.js, Supabase/Postgres, TDD, and Playwright E2E testing.

Document-to-Markdown ingestion front-end for the document-analysis pipeline. Wraps Microsoft MarkItDown (PDF, Word, PowerPoint, Excel, HTML, CSV/JSON/XML, EPub) with batch folder conversion that mirrors the input tree, YAML provenance frontmatter, a SHA-256 + settings manifest for idempotent re-runs (re-OCRs when --use-llm is added), a per-file timeout, per-file error isolation, and optional LLM image descriptions + embedded-image OCR via the team OpenRouter key. Runs in the Cowork sandbox; outputs default to the document-analysis repo's sources-md/ tree. Includes a documented (not-yet-wired) adoption reference for layout-faithful Azure Document Intelligence.

Transform AI-generated content into author-owned work through structured editorial judgment, voice extraction, and Sorkin DOB narrative framing — with a complete authorship record.

Stage-sharded /email-* commands for the product email lifecycle: /email-activation, /email-nurture, /email-convert, /email-retain, and /email-lifecycle (the whole arc). Each runs a shared engine skill scoped to its stage and returns five things: best practices (installed authoring skills + live external research), tooling (installed skills to use + catalog adoption candidates queried from the Workforce Automation Supabase catalog, de-duped vs our installed set), a benchmark of a named product's current setup graded against best practice, prioritized recommendations aligned to the MoxyWolf reference runtime (PostHog Workflows + Resend + first-party event capture, no n8n, single body store per class), and an auto-drafted email sequence for the stage (triggers, delays, exit conditions, subjects, copy in MoxyWolf voice). Email-specific, stage-sharded sibling of marcom-audit.

Generate Excalidraw diagrams directly into the MoxyWolf Vault in the zsviczian Obsidian-Excalidraw plugin's native .excalidraw.md format. /excalidraw <description> writes to _Shared Knowledge/Diagrams/ or Projects/<project>/06-Engineering/diagrams/; /excalidraw-here generates a diagram of the current document and embeds it next to that note. Carries the excalidraw-vault-core runner protocol (Obsidian wrapping format, element schema, depth assessment, routing) as the single source of truth so future plugins can delegate. Parallels vault-code-learn (code axis) and graphify-vault (knowledge axis) on the diagram axis.

Tooling for The Frontier Founder site. /blog-post converts any draft markdown file into a publication-ready, SEO/AEO-structured blog post — frontmatter with a meta-description excerpt, AEO structure (At a Glance, Key Takeaways, FAQ), a single @graph JSON-LD block (BlogPosting + Person + Organization + FAQPage) on the thefrontierfounder.com canonical, MoxyWolf typographic rules, a brand-aligned hero image, and slug-tied file naming, saved into the FrontierFounder repo. AEO thresholds defer to the canonical aeo-checklist in 4d-blog-engine.

Frontier Founder SMB (FFSMB) — pre-built small-business workflows on a modern indie-founder stack: Clarify AI CRM, Stripe payments, QuickBooks accounting, DocuSign, Gmail/Google, and claude.ai/design. Cash flow, month-end close, invoice chasing, weekly briefs, CRM upkeep, customer pulse, contract review, hiring, growth campaigns — with an approval gate on anything touching money or customers. A MoxyWolf public fork of Anthropic's Small Business plugin, re-homed off PayPal/HubSpot/Square/Canva. Companion to the Apollo plugin for B2B prospecting. v0.3.1: installable — all 31 skills migrated, design lane rewritten for claude.ai/design, connector manifest in place. Team-beta; a dogfood pass over the transformed money/CRM skills is recommended before public release.

Analyze GitHub repositories for health, tech-stack conformance, security-classified issue reviews (CWE/OWASP/NIST), HITL code-fix suggestions, closure verification, and reverse-engineered PRDs. Runs a graphify knowledge graph as the mandatory first step of deep analysis — corpus from the clone, runner protocol delegated to the graphify plugin's graphify-core skill — with keyless and plain-tree-walk fallbacks. Uses native GitHub MCP + gh CLI / REST.

Standalone graphify knowledge-graph runner with Obsidian integration. Graph any corpus — a code directory via /graphify, a Supabase database via /graphify-supabase (native --postgres introspection preferred, MCP corpus emit fallback), or the Obsidian vault itself via /graphify-vault (docs-first keyed flow). Obsidian-format exports land back in the MoxyWolf Vault (Projects/<project>/06-Engineering/graphs/ per project, _Shared Knowledge/Vault Graph/ vault-wide) so they cross-link with real notes. Hosts the canonical graphify-core runner protocol (team OpenRouter key per DR-010, two-pass AST-then-label sandbox-safe split, keyless fallback); github-repo-analyzer delegates its Step 0 here.

Software development execution engine adapted from Garry Tan's gstack (MIT). Code review, adversarial just-committed review via /gstack-codex-review (real Codex when the codex CLI is present, Claude fallback otherwise), security audit, debugging, QA testing, and shipping — /gstack-ship validates in a disposable worktree with a safe-fix/escalate contract (concept-ported from no-mistakes, MIT). Pairs with product-orchestrator. Browser ops via Claude in Chrome.

/marcom-best-practices [target] finds and applies best practices for any MARCOM project, idea, channel, or campaign, on the premise that we're probably doing it wrong and should consult the full toolbox before changing direction. Classifies the target into 13 MARCOM domains (lifecycle email/outreach expanded into onboarding -> nurturing -> upgrade -> retention, not one bucket), then sweeps three tiers: our installed plugins/skills via a curated domain->skill capability map; the Workforce Automation Supabase catalog of ~580K catalogued Claude skills/plugins/MCPs (with an 'installed' source for a real have/don't-have diff) to surface adoption candidates we don't have; and heavy external web research. Benchmarks current MoxyWolf practice against all three using live analytics (GA4/PostHog/Ahrefs/CRM), writes a prioritized best-practices brief to the target's MARCOM folder, lists adoption candidates, and auto-runs the top applicable installed skills to produce starter deliverables.

Bundle of 25 standalone skills used across MoxyWolf work — voice, brand, content ecosystems, plus the Anthropic-shipped reference skills, packaged as one installable plugin. (daily-ops moved out of the bundle in v1.1.0 — install the standalone plugin instead.)

Steph Ango / Obsidian's five official agent skills vendored into the MoxyWolf marketplace so every team Mac gets consistent Obsidian fluency. Ships obsidian-markdown (proper wiki-link / callout / embed rendering), obsidian-bases (Obsidian's new Bases query syntax that replaced Dataview for most use cases), json-canvas (the JSON Canvas spec for visual boards), obsidian-cli (script-friendly Obsidian invocation), and defuddle (Defuddle HTML-to-Markdown cleanup for web clips). Upstream: kepano/obsidian-skills, Apache-2.0. v1.0.0.

Vault-native personal operating system with Council integration. Energy-aware daily ops, three-layer persistent memory, Kanban task management, and session knowledge extraction into the MoxyWolf Obsidian vault. v2.7.0 adds Decision Record auto-routing: every DR write is classified by topic (engineering / GTM / brand / compliance / operating-norm / product / agents-and-plugins / personnel) and filed to the canonical folder, every DR is appended to the new Company Decision Log master index at _Shared Knowledge/Operating Norms/_INDEX.md, and project-scoped DRs also append to the project hub's <P> Decisions.md. v2.9.0: personal-os aligned to the Jira single-board migration — Obsidian KANBAN_VIEW.md + Google-Drive-canonical store are Dorian's private working layer (writes only Obsidian checkboxes, never Jira issues) that syncs up to the team board on Jira via team-kanban; the daily note's 'Today's Board' is now a live embedded Jira query (jira-search against MOXY) instead of a KANBAN_VIEW.md snapshot.

Horizontal restraint layer for coding work. An always-on 'lazy senior dev' ruleset injected every turn that runs a YAGNI ladder before the agent writes code (question whether it needs to exist, stdlib before custom, native before dependency, one line before fifty), never cutting validation, error handling, security, or accessibility. Ships the referenceable `ponytail` skill plus /ponytail (lite|full|ultra|off), /ponytail-review, /ponytail-audit, /ponytail-debt, /ponytail-gain, /ponytail-help. Vendored from DietrichGebert/ponytail (MIT) v4.8.3; pairs with gstack-execution (trim then harden) and dev-infrastructure-skills.

Product decision engine that wraps Council deliberation with product-specific role prompts for scope, architecture, and GTM decisions. Maintains a project charter of durable governing principles the Council consults before scope and PRD decisions. Routes outputs to downstream execution skills and maintains decision records in the Obsidian vault.

Cowork project lifecycle for MoxyWolf projects. /init-project scaffolds tailored Project Instructions. /session-start auto-resolves the project — explicit argument, then launch directory, then the most recently active project, never a picker — mounts the three standard roots, reads the previous session's handoff (cross-checked against current team-shared memory so stale procedural reminders get flagged STALE rather than silently propagated), reads Taskade/_Shared Files/_shared-memory/INDEX.md and surfaces it as a 'Team-shared rules in effect' briefing section, and probes the team-shared OpenRouter key (DR-010). /session-end asks who authored the handoff and whether it's a baton-pass, writes the canonical handoff with `author` / `for` frontmatter, requires every general behavioral reminder in the procedural-reminders section to cite a currently-existing team-shared memory file (or be tagged session-specific), supports --author / --handoff-to / --solo, refreshes each writable repo's README.md, then runs /obsidian-update. /init-project saves the full instructions on disk as the single source of truth and pastes only a thin loader stub (mounts + file-write-path override + read-the-file-first imperative) into Cowork settings, so the embedded copy never drifts out of sync with the on-disk file (DR-010). The stub skeleton and on-disk reconciliation directives live in a vault spec that both /init-project and /refresh-project-instructions read at run time, so changing a project-instruction rule is a vault edit plus a per-project /refresh-project-instructions run, never a plugin update. v0.22.0: folder access is fully mode-agnostic across online (cloud) and offline (on-computer) — each capability is detected by tool presence with a filesystem-probe fallback (detect via get_device_info or by listing the path; mount via request_cowork_directory when present, else prompt Add folder; pick via native picker when present, else device_list_dir + AskUserQuestion chips), so nothing hard-depends on request_cowork_directory and the skills run identically online or offline. v0.23.0: task-board reads moved from the retired vault kanban (KANBAN_VIEW.md) to the team Jira board (project MOXY) — /session-start Step 4b queries MOXY via the Atlassian MCP, strictly filtered fail-closed to the project's Jira label (project-<slug>); the 'Kanban project tag(s)' field now denotes a Jira label.

End-to-end academic research pipeline: literature discovery, citation verification, thematic synthesis, and perspective-driven content generation. AutoResearchClaw-inspired.

Full-pipeline front-end design system for SaaS products and marketing sites. Generates, polishes, audits, and optimizes production-ready Next.js + React + Tailwind + shadcn/ui interfaces. Includes an anti-slop design-taste gate (Design Read, three dials, anti-default discipline, em-dash ban) adapted from taste-skill (MIT), plus design-fluency material (OKLCH color, typography craft, AI-slop test, craft reference library) consolidated from impeccable (Apache-2.0).

End-to-end SaaS and API gateway pricing research, modeling, and copywriting. Combines competitor intelligence, pricing frameworks (Van Westendorp, Gabor-Granger, value-based), and conversion-optimized pricing-page generation.

Topic-Synergy Outreach Engine — find the people writing about your topics (and the people you cited) and reach them without pitching. Builds a topic fingerprint from your own content, then runs THREE discovery centers. AUTHOR center (named profiles via Apify harvestapi/linkedin-profile-posts) and CONTENT center (keyword/hashtag search via Apify harvestapi/linkedin-post-search) are comment-first, starting from who's posting; discovered posts are scored against the fingerprint, deduped against an xlsx tracker, and queued, then /synergy-run executes the comment-first decision tree (like + a practitioner comment, the cite-then-tell lever, and a connection note) with a hard human gate and a guard against the LinkedIn 'Post as' identity selector. The new CITATION center starts from who you cited: /synergy-cite-harvest parses your paper's bibliography, triages by reachability, resolves authors via OpenAlex/ORCID, dedups against Clarify, enriches person + org via Apollo (LinkedIn-first match + a verify gate against wrong-person matches), verifies LinkedIn identity via Apify, and drafts a 'we cited you' email + a hook-free connect note into a citation registry; /synergy-cite-run sends email first (Mailtrap as you, BCC you) then the LinkedIn connect, with the hard-won send discipline (type the note in separate click+type calls to beat the focus-race truncation bug, zoom-verify the note's start and end before Send, 2nd/3rd/high-follower button geography, the email-verification gate, never withdraw to re-send); /synergy-cite-accept-check follows through on accepted invites. /synergy-schedule stands up an every-other-day prep task. Cadence + guardrails baked in: comment same-day/connect later, the ~20-25/day LinkedIn connect ceiling, cite-don't-pitch, voice (no em-dashes, contractions, practitioner register), verified citations only. The plugin never auto-sends. v0.2.0.

Jira (project MOXY) is the single canonical task board. Sweeps non-chat sources (Google Drive Active Tasks, Google Calendar, Gmail) for genuinely-new action items, dedups them against the board (open + recently-Done), and files them to MOXY with best-practice issue authoring (Context/Acceptance/Notes descriptions, sub-items as real Subtasks, dependencies as Blocks links, Backlog default), then maintains board hygiene (priorities, column limits, In Review reviewer pairings). v0.6.0 retired the vault kanban and all Slack task flows (no Obsidian source-of-truth, no dual-authority sync-back, no Slack scraping, no #general digest) — team members file their own tickets directly in Jira, including from Slack via the Jira Slack app. Bulk writes to the shared tracker stay human-gated.

Pointer to Understand-Anything (Egonex-AI, MIT) — a multi-agent pipeline that turns a codebase into an interactive knowledge graph with guided tours, semantic search, diff-impact analysis, and an onboarding dashboard. Its analysis core is a TypeScript + native tree-sitter build, so it is installed upstream rather than re-homed into this markdown marketplace (same posture as not re-homing claude-mem's runtime). This entry documents what it does, when to reach for it vs. graphify / github-repo-analyzer, and the one-line install. A full native vendor is a follow-up decision (DR-011).

The missing code-learning loop. At session start (or on demand via /code-learn) walks the active repo(s) under ~/Documents/GitHub/, extracts a durable pattern digest — tech stack and dependency signatures, naming conventions, error-handling style, test patterns, lint/type rules, file-layout idioms, frequent imports, and what the repo intentionally does NOT use — and writes one digest per repo to MoxyWolf Vault/_Shared Knowledge/Code Patterns/<repo>.md. Incremental: only files modified since the digest's last-learned timestamp are re-read. The digest is referenced by future Claude sessions so suggestions match the team's existing patterns instead of generic boilerplate. Auto-invoked by /session-start; manual trigger via /code-learn <repo> | --project <slug> | --all. v0.1.0.

Six vault-* workflow skills vendored from az9713/claude-code-obsidian. Companion to obsidian-skills (kepano's foundational five) — those handle the file formats, these run the daily vault workflows: vault-capture (quick-drop into _inbox/), vault-save (structured save to the right folder), vault-journal (Daily Journal/YYYY-MM-DD.md authoring), vault-synthesize (multi-note synthesis with citations), vault-moc (Map-of-Content authoring), vault-health (orphan / broken-link / stale-tag audits). v1.0.0.

Converts pasted WebVTT closed-caption content into clean, readable text. Strips timestamps, merges into flowing paragraphs.