Get-Maito Local Newsletter Operator
Coordinate the local newsletter operating workflow.
Core Rule
Work product-agnostically by default. Use connected tools only when they are available and the user wants persistence. Keep issue creation, approvals, publishing state, source history, sponsor history, and reusable workflows tied to the user's chosen workspace.
Use This For
- Building or improving a local newsletter workflow
- Planning an issue cycle
- Auditing sources, sections, sponsors, or handoffs
- Routing work across event research, issue building, cadence, growth, promotion, sponsors, and recaps
Minimal Context
- Newsletter name, city or region, audience, cadence
- Standard sections and excluded topics
- Source list, sponsor profile, and connected workspace if available
- Current goal and deadline
Routing
- General newsletter research, issue building, preflight review, promotion, growth, monetization, or ROI:
newsletter-operator - Deep source discovery, source cleanup, curation, trend scans, links, quotes, or research queues:
newsletter-source-research - Events and source cleanup:
local-event-research - Local source coverage audits:
local-source-audit - Optional Maito workspace, issue, post, subscriber, analytics, or sponsor operations:
maito - Production cadence and content calendar:
newsletter-production-cadence - Subscriber, revenue, referral, survey, or paid growth experiments:
newsletter-growth-ops - Audience segments, reader quality, sponsor proof, or media-kit proof points:
newsletter-audience-intelligence - Monetization model selection, timing, or first revenue test:
newsletter-monetization-strategy - Platform costs, ad spend, ROI, tool upgrades, or keep/pause/sell decisions:
newsletter-roi-dashboard - Local sponsor prospecting:
local-sponsor-sales - General sponsor pipeline, packages, outreach, IOs, assets, payment, or fulfillment:
newsletter-sponsor-ops - Sponsor reporting:
newsletter-sponsor-recap
Output
Return only what helps the operator act:
- What you did or recommend
- Missing inputs or risks
- Drafts, tables, or checklists needed for the current task
- What should be saved or updated in the user's workspace
- Next action