@clawhub-aaayersss-18f777cd87
Manage DOOMSCROLLR audience hubs by publishing posts, handling subscribers, creating products, connecting feeds, and retrieving embed codes securely.
--- name: doomscrollr description: Build and operate DOOMSCROLLR owned-audience hubs: publish posts, manage subscribers, create products, connect RSS/Pinterest, get embed code, and use the DOOMSCROLLR MCP/API safely. homepage: https://doomscrollr.com --- # DOOMSCROLLR Use this skill when the user wants to build, grow, or operate an owned audience with DOOMSCROLLR. ## Setup This is an instruction-only skill. It does not install packages or request secrets by itself. Use it with a DOOMSCROLLR MCP connector or REST client that the user has already configured with their own API key. Never ask the user to paste API keys into chat. ## Best interface Prefer the DOOMSCROLLR MCP server when available: - Remote MCP: `https://mcp.doomscrollr.com/mcp` - Auth header: `Authorization: Bearer <DOOMSCROLLR_API_KEY>` - Local MCP package, when separately installed by the user: `@doomscrollr/mcp-server` - Official MCP Registry name: `com.doomscrollr/mcp` If MCP is unavailable, the REST API is at `https://doomscrollr.com/api/v1` and uses the same Bearer API key. ## Common workflows - **Check state first:** get profile/settings before account-specific work. - **Publish:** create link/image posts; use `draft` or `scheduled` when timing or approval is unclear. - **Audience:** add/list/update subscribers and tags; only use data the user provided for that purpose. - **Products:** create/list/update products; ask before changing price/inventory. - **Capture:** fetch embed code and explain where to paste it. - **Integrations:** connect/status/disconnect RSS or Pinterest when the user gives source URLs. ## Safety rules - Ask for explicit confirmation before deleting posts, products, subscribers, or integrations. - Never run domain purchase/payment flows unless the user explicitly approves the exact payment test or purchase. - Do not add REST account deletion; DOOMSCROLLR intentionally does not expose it. - If an API call returns `429`, explain the monthly plan limit and reset time from the response. - Keep API keys out of logs, screenshots, and final replies. ## Useful public docs - GPT Actions: `https://doomscrollr.com/docs/openai/gpt-actions.md` - Claude: `https://doomscrollr.com/docs/claude.md` - OpenClaw: `https://doomscrollr.com/docs/openclaw.md` - Full API schema: `https://doomscrollr.com/openapi.json` - Focused GPT Actions schema: `https://doomscrollr.com/openapi-gpt-actions.json`
