Skip to main content
Claude Code

I Automate My Wife’s Content Marketing with Claude Code, Building a Custom Skill System

Published by
SectorHQ Editorial
I Automate My Wife’s Content Marketing with Claude Code, Building a Custom Skill System

Photo by Lightsaber Collection (unsplash.com/@lightsabercollection) on Unsplash

15 agents, 43,000 lines of Python—Doneyli reports he built this autonomous Claude Code system to run his wife’s solo content marketing.

Key Facts

  • Key company: Claude Code

Claude Code’s latest release has turned a hobbyist‑level scripting tool into a full‑stack execution engine, and Doneyli De Jesus’ recent build showcases exactly how far the platform can stretch. According to Doneyli’s March 19, 2026 post, the system he delivered for his wife’s solo‑entrepreneur venture runs 15 autonomous agents, processes more than 3,000 files, and generates 10‑12 pieces of content each week across four distribution channels—all without human intervention. The core of the pipeline is a custom “skill” architecture that lives inside Claude Code’s CLI, allowing the author to treat the tool as a programmable autopilot rather than a simple autocomplete.

The architecture hinges on a two‑wave batch pipeline that moves content from signal discovery through analytics collection. In the first wave, a “signal” agent monitors niche forums, newsletters, and social feeds, extracting raw ideas and storing them in a local memory store. Doneyli notes that the memory system relies on embeddings generated by a locally‑hosted Qwen 3‑0.6B model quantized to INT8 via ONNX Runtime, a choice driven by the need for 1,024‑dimensional vectors and zero external API calls (see the “Local Qwen3‑0.6B INT8” report). The model’s cosine‑similarity threshold of 0.75 proved more discriminating than off‑the‑shelf sentence‑transformers, reducing false positives that would otherwise flood the pipeline with structurally similar but semantically unrelated logs.

Once embeddings are computed, the second wave of agents takes over: a “topic clustering” skill groups related signals, a “content drafting” skill assembles outlines, and a “copy‑generation” skill invokes Claude Opus 4.6 (as referenced in VentureBeat’s coverage of the new 1M‑token context model) to flesh out drafts. Each skill is encapsulated as a reusable Claude Code module, and the system’s state is persisted between runs, enabling the agents to learn from prior outputs. Doneyli emphasizes that this persistent state avoids the “one‑shot prompt” trap common in many AI workflows, where each execution starts from a blank slate and discards any contextual knowledge (see his “Custom Skill System” article).

Scheduling and self‑maintenance are handled by a “Chief of Staff” agent that Doneyli previously described in a separate Build Log (43,000 lines of Python, seven agents managing his personal life). In the content system, this agent orchestrates daily runs, monitors token usage, and triggers re‑training of the Qwen embedding model when drift is detected. The agent also routes analytics data back to a “performance dashboard” skill, which aggregates engagement metrics from each platform and feeds them into a “SEO optimization” skill. This feedback loop allows the pipeline to adjust headline phrasing and keyword density automatically, a capability that Doneyli claims has already lifted his wife’s organic reach by a measurable margin, though exact figures are not disclosed.

Error handling and resilience are baked into the workflow through “sub‑agents” that act as watchdogs. Four in‑conversation sub‑agents monitor API health, retry failed calls, and fall back to cached embeddings when the local ONNX model experiences a cold‑start latency of roughly three seconds—a problem Doneyli solved by pre‑loading the model at system start (as detailed in the embedding report). The system also includes a “batch‑aging” skill that prunes stale content ideas after a configurable retention period, ensuring the memory store remains performant despite the 3,000‑file baseline.

Overall, Doneyli’s implementation demonstrates that Claude Code, especially when paired with locally‑hosted embedding models like Qwen 3‑0.6B, can support production‑grade autonomous content operations. The combination of custom skills, persistent state, and self‑orchestrating agents bridges the gap between simple code‑completion tools and enterprise‑level workflow automation—a trend hinted at by Anthropic’s recent Claude Sonnet 4.5 and Claude Opus 4.6 releases, which both tout richer context windows and agent‑team capabilities (CNET; VentureBeat). As the line between developer tooling and autonomous AI agents continues to blur, Doneyli’s work offers a concrete blueprint for solopreneurs seeking to outsource the relentless grind of content marketing.

Sources

Primary source
Other signals
  • Dev.to AI Tag
  • Reddit - r/LocalLLaMA New

Reporting based on verified sources and public filings. Sector HQ editorial standards require multi-source attribution.

More from SectorHQ:📊Intelligence📝Blog

🏢Companies in This Story

Related Stories