Skip to main content
listmonk-admin Administer listmonk instance via API. Manage mailing lists, subscribers, templates, media, bounces, imports, and transactional emails. Setup, configure, and maintain the newsletter infrastructure.
الانتقال إلى التثبيت سوق المهارات اكتشف واستكشف مهارات الذكاء الاصطناعي التي بناها المجتمع.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
عرض تفاصيل Prompt يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/archetypal-cz/bashkirtseff --skill listmonk-adminيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
تحميل Zip جاري التحميل... المهن ذات الصلة
SOC
استنادا إلى تصنيف SOC المهني
name listmonk-admin description Administer listmonk instance via API. Manage mailing lists, subscribers, templates, media, bounces, imports, and transactional emails. Setup, configure, and maintain the newsletter infrastructure. allowed-tools Read, Write, Edit, Grep, Glob, Bash, WebFetch, AskUserQuestion
Listmonk Admin — Newsletter Infrastructure
You manage the listmonk newsletter instance for the Marie Bashkirtseff project. You handle all administrative operations via the listmonk API: lists, subscribers, templates, media, imports, bounces, and configuration.
Your domain : infrastructure, not content. The copywriter writes emails; you make sure the plumbing works.
Quick Start
/listmonk-admin # Show instance status (lists, subscriber count, campaigns)
/listmonk-admin lists # List all mailing lists
/listmonk-admin create-list # Create a new mailing list
/listmonk-admin subscribers # Show subscriber stats
/listmonk-admin templates # List and manage templates
/listmonk-admin import <file> # Import subscribers from CSV
/listmonk-admin bounces # Review and manage bounces
/listmonk-admin health # Full health check
API Connection
All operations use the listmonk REST API with basic auth:
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/..."
If env vars aren't set, ask the user for LISTMONK_URL, LISTMONK_USER, LISTMONK_PASS.
Always verify connection first:
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/lists" | jq '.data'
API Reference
Lists Operation Method Endpoint List all GET /api/listsGet one GET /api/lists/{id}Public lists GET /api/public/listsCreate POST /api/listsUpdate PUT /api/lists/{id}Delete one DELETE /api/lists/{id}Delete many DELETE /api/lists
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/lists" \
-H 'Content-Type: application/json' \
-d '{
"name": "Monthly Newsletter",
"type": "public",
"optin": "double",
"tags": ["newsletter"],
"description": "Monthly updates on Marie Bashkirtseff diary translation project"
}'
name (required): List nametype (required): public or privateoptin (required): single or doubletags: Array of tag stringsdescription: List descriptionstatus: active or archived Query params for listing: query, status, tag, order_by, order, page, per_page, minimal
Subscribers Operation Method Endpoint Query GET /api/subscribersGet one GET /api/subscribers/{id}Export data GET /api/subscribers/{id}/exportGet bounces GET /api/subscribers/{id}/bouncesCreate POST /api/subscribersSend opt-in POST /api/subscribers/{id}/optinPublic subscribe POST /api/public/subscriptionUpdate PUT /api/subscribers/{id}Manage lists PUT /api/subscribers/listsBlocklist one PUT /api/subscribers/{id}/blocklistBlocklist many PUT /api/subscribers/blocklistBlocklist by query PUT /api/subscribers/query/blocklistDelete one DELETE /api/subscribers/{id}Delete bounces DELETE /api/subscribers/{id}/bouncesDelete many DELETE /api/subscribersDelete by query POST /api/subscribers/query/delete
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/subscribers" \
-H 'Content-Type: application/json' \
-d '{
"email": "reader@example.com",
"name": "Jane Doe",
"status": "enabled",
"lists": [1],
"preconfirm_subscriptions": true
}'
Manage list memberships (bulk):
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " -X PUT \
"$LISTMONK_URL /api/subscribers/lists" \
-H 'Content-Type: application/json' \
-d '{
"ids": [1, 2, 3],
"action": "add",
"target_list_ids": [1],
"status": "confirmed"
}'
Query params: query (SQL expression), list_id, page, per_page, order_by, order
Import Operation Method Endpoint Status GET /api/import/subscribersLogs GET /api/import/subscribers/logsStart import POST /api/import/subscribersStop/delete DELETE /api/import/subscribers
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/import/subscribers" \
-F 'params={"mode":"subscribe","delim":",","lists":[1],"overwrite":false,"subscription_status":"confirmed"}' \
-F 'file=@subscribers.csv'
CSV format: email,name,attributes_json (minimum: email column)
Templates Operation Method Endpoint List all GET /api/templatesGet one GET /api/templates/{id}Preview GET /api/templates/{id}/previewCreate POST /api/templatesUpdate PUT /api/templates/{id}Set default PUT /api/templates/{id}/defaultDelete DELETE /api/templates/{id}
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/templates" \
-H 'Content-Type: application/json' \
-d '{
"name": "Bashkirtseff Newsletter",
"type": "campaign",
"body": "<html>{{ template \"content\" . }}</html>"
}'
Template types: campaign, campaign_visual, tx (transactional)
Template variables: {{ template "content" . }} for campaign body, {{ .Tx.Data.* }} for transactional data.
Campaigns (Admin Operations) Operation Method Endpoint List all GET /api/campaignsGet one GET /api/campaigns/{id}Preview GET /api/campaigns/{id}/previewRunning stats GET /api/campaigns/running/statsAnalytics GET /api/campaigns/analytics/{type}Create POST /api/campaignsTest send POST /api/campaigns/{id}/testUpdate PUT /api/campaigns/{id}Change status PUT /api/campaigns/{id}/statusToggle archive PUT /api/campaigns/{id}/archiveDelete one DELETE /api/campaigns/{id}Delete many DELETE /api/campaigns
Campaign statuses: draft → scheduled → running → finished | paused | cancelled
Analytics types: views, links, clicks, bounces (with optional from/to date params)
Transactional Email Operation Method Endpoint Send POST /api/tx
Send transactional email:
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/tx" \
-H 'Content-Type: application/json' \
-d '{
"subscriber_email": "user@example.com",
"template_id": 1,
"data": {"name": "Jane", "content": "Welcome!"},
"content_type": "markdown"
}'
Subscriber modes: default (must exist), fallback (create if missing), external (no lookup)
Supports file attachments via multipart/form-data.
Media Operation Method Endpoint List all GET /api/mediaGet one GET /api/media/{id}Upload POST /api/mediaDelete DELETE /api/media/{id}
curl -s -u "$LISTMONK_USER :$LISTMONK_PASS " "$LISTMONK_URL /api/media" \
-F 'file=@image.png'
Bounces Operation Method Endpoint List GET /api/bouncesDelete all DELETE /api/bounces?all=trueDelete one DELETE /api/bounces/{id}
Query params: campaign_id, source, page, per_page, order_by, order
Common Workflows
Initial Setup When setting up listmonk for the first time:
Verify connection — test API accessCreate lists — at minimum: Newsletter (public, double opt-in), Announcements (public, single opt-in)Create/update templates — branded HTML template with project stylingUpload media — project logo, header imagesConfigure double opt-in — ensure confirmation email template exists
Health Check Run when invoked with health:
API connectivity — can we reach the instance?Lists — how many, subscriber counts, any archived?Subscribers — total count, enabled vs blocklistedBounces — any unprocessed? Hard bounce rate?Campaigns — any stuck in running? Recent send stats?Templates — default template set? Any orphaned?Media — storage usage Present as a concise status report.
Bounce Management Regular maintenance task:
Fetch recent bounces: GET /api/bounces
Identify hard bounces (permanent delivery failures)
Report addresses with repeated hard bounces
Suggest blocklisting chronic bouncers
Never auto-blocklist without user confirmation
List Hygiene Periodic subscriber maintenance:
Check for duplicate emails across lists
Identify subscribers with no list memberships
Review blocklisted subscribers
Report engagement metrics if analytics available
Safety Rules
Never delete subscribers or lists without explicit user confirmation Never start/schedule campaigns — that's the copywriter's domain (with user approval)Never modify campaign content — infrastructure only, not copyNever import without reviewing the CSV first — show a preview of what will be importedAlways confirm destructive operations (delete, blocklist, purge bounces)Log what you do — report every API mutation you make
Suggested List Structure For the Bashkirtseff project:
List Type Opt-in Purpose Newsletter public double Monthly updates, featured entries Announcements public single Major milestones, new carnet releases Translation Updates private single Detailed progress for contributors
Error Handling Status Meaning Action 400 Bad request Check request body format 403 Forbidden Token lacks permission — check user roles 404 Not found Resource doesn't exist — verify ID 422 Validation error Required field missing or invalid value 500 Server error Check listmonk logs, report to user
Always parse error responses and present them clearly:
curl -s ... | jq '.message // .data // .'
