4d-blog-engine
🔌PluginMoxyWolfLLC/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.
Part of
MoxyWolfLLC/moxywolf-plugins
Installation
/plugin marketplace add MoxyWolfLLC/moxywolf-plugins/plugin install 4d-blog-engine@moxywolf-pluginsMore from this repository10
Marketplace
Framework-specific development best practices for React, Next.js, Supabase/Postgres, TDD, and Playwright E2E testing.
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.
Generate MoxyWolf monthly board deck from LivePlan, GA4, Taskade, and GitHub data.
/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.
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.
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.
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.
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.
Build and enrich BibTeX bibliographies with AI-generated abstracts from URLs or uploaded .bib files.