{"id":"670a450d-3cbd-45f7-9ea1-54dfb306714f","entityType":"agent","slug":"clawhub-hith3sh-postmark-email","name":"Postmark Email","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-postmark-email","canonicalPath":"/agent/clawhub-hith3sh-postmark-email","generatedAt":"2026-10-09T18:08:41.283Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T13:55:08.129Z","emptyReason":null},"description":"Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this ski... Skill: Postmark Email Owner: hith3sh Summary: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this ski... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:15:45.661Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffi","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.5K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:postmark-email","sourceUrl":"https://clawhub.ai/hith3sh/postmark-email","homepage":"https://clawhub.ai/hith3sh/skills/postmark-email","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/postmark-email","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/postmark-email","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this ski..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:55:08.129Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:55:08.129Z","emptyReason":null},"stars":null,"forks":null,"downloads":2531,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"2.5K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:55:08.129Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T13:55:08.129Z","lastCrawledAt":"2026-10-09T13:55:08.129Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T13:55:08.129Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-06-09T07:15:45.661Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":6372},{"version":"1.0.4","createdAt":"2026-06-09T05:02:36.400Z","changelog":"- Removed the sample file skill-card.md to clean up unused documentation. - No changes were made to the skill functionality or user-facing documentation.","fileCount":3,"zipByteSize":6160},{"version":"1.0.1","createdAt":"2026-06-08T16:41:01.021Z","changelog":"- Added a Postmark logo image to the documentation for improved visual clarity. - Minor edits to the documentation (SKILL.md) for presentation and branding consistency. - Removed the skill-card.md file to streamline documentation.","fileCount":3,"zipByteSize":6174},{"version":"0.1.1","createdAt":"2026-06-07T13:34:46.821Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":5960},{"version":"0.1.0","createdAt":"2026-05-17T06:06:46.760Z","changelog":"Initial release. - Inspect transactional email activity, templates, messages, and delivery workflows in Postmark via ClawLink. - Guided setup instructions for pairing ClawLink and connecting Postmark, no need for manual API credential entry. - Safeguards to confirm actions before write operations, with emphasis on read-first workflows. - Dynamic discovery and usage of available Postmark tools through ClawLink integration. - Clear rules to ensure security and prevent credential sharing in chat.","fileCount":3,"zipByteSize":3499}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:postmark-email","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T18:08:41.281Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-postmark-email/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T13:55:08.129Z","emptyReason":null},"readme":"Skill: Postmark Email\n\nOwner: hith3sh\n\nSummary: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this ski...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-06-09T07:15:45.661Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.4 | 2026-06-09T05:02:36.400Z | auto\n\n- Removed the sample file skill-card.md to clean up unused documentation.\n- No changes were made to the skill functionality or user-facing documentation.\n\nv1.0.1 | 2026-06-08T16:41:01.021Z | auto\n\n- Added a Postmark logo image to the documentation for improved visual clarity.\n- Minor edits to the documentation (SKILL.md) for presentation and branding consistency.\n- Removed the skill-card.md file to streamline documentation.\n\nv0.1.1 | 2026-06-07T13:34:46.821Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-17T06:06:46.760Z | auto\n\nInitial release.\n\n- Inspect transactional email activity, templates, messages, and delivery workflows in Postmark via ClawLink.\n- Guided setup instructions for pairing ClawLink and connecting Postmark, no need for manual API credential entry.\n- Safeguards to confirm actions before write operations, with emphasis on read-first workflows.\n- Dynamic discovery and usage of available Postmark tools through ClawLink integration.\n- Clear rules to ensure security and prevent credential sharing in chat.\n\nArchive index:\n\nArchive v1.0.5: 3 files, 6372 bytes\n\nFiles: skill-card.md (2862b), SKILL.md (15950b), _meta.json (133b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: postmark-email\ndescription: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this skill when users want to monitor email delivery, manage templates, check bounce and spam reports, and configure transactional email workflows via Postmark.\n---\n\n# Postmark Email\n\n![Postmark Email](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/postmark.svg)\n\nAccess Postmark's transactional email platform via the Postmark API. Inspect outbound messages, templates, and delivery events. Review bounce, spam, and engagement statistics. Manage webhooks and message streams.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=postmark-email) for hosted connection flows and credentials so you do not need to configure Postmark API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Postmark |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Postmark |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│  Postmark API   │\n│   (User Chat)   │     │   (API Key)  │     │                  │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n          │                       │                       │\n          │  1. Install Plugin   │                       │\n          │2. Pair Device      │                       │\n          │3. Connect Postmark  │                       │\n          │                      │  4. Secure Proxy      │\n          │                      │  5. API Requests      │\n          │                      │                       │\n          ▼ ▼                       ▼\n    ┌──────────┐           ┌──────────┐           ┌──────────┐\n    │  SKILL   │           │ Dashboard│           │ Postmark │\n    │  File    │           │ Auth     │           │ Platform │\n    └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Postmark again.\"\n\n## Quick Start\n\n```bash\n# Get outbound overview\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" --params '{}'\n\n# Search outbound messages\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" --params '{\"status\": \"sent\"}'\n\n# List templates\nclawlink_call_tool --tool \"postmark_list_templates\" --params '{}'\n```\n\n## Authentication\n\nAll Postmark tool calls are authenticated automatically by ClawLink using the user's Postmark account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every Postmark API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=postmark and connect Postmark.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `postmark` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration postmark\n```\n\n**Response:** Returns the live tool catalog for Postmark.\n\n### Reconnect\n\nIf Postmark tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=postmark\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration postmark`\n\n## Security& Permissions\n\n- Access is scoped to messages, templates, streams, and webhooks within the connected Postmark server.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete webhook, archive stream) must be confirmed.\n- Server configuration changes affect all email sending on that server.\n\n## Tool Reference\n\n### Message Streams\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_message_streams` | List all message streams for a server | Read |\n| `postmark_get_message_stream` | Get details of a specific stream | Read |\n| `postmark_create_message_stream` | Create a new message stream | Write |\n| `postmark_update_message_stream` | Update a stream's name or description | Write |\n| `postmark_archive_message_stream` | Archive a message stream (soft delete) | Write |\n| `postmark_unarchive_message_stream` | Restore an archived stream | Write |\n\n### Outbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_outbound_messages` | Search sent messages with filters | Read |\n| `postmark_get_sent_counts` | Get sent message counts by date range | Read |\n| `postmark_get_delivery_stats` | Get delivery statistics | Read |\n| `postmark_list_outbound_message_opens` | List open events for outbound messages | Read |\n| `postmark_list_outbound_message_clicks` | List click events for outbound messages | Read |\n\n### Inbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_inbound_messages` | Search inbound messages | Read |\n\n### Templates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_templates` | List all templates | Read |\n| `postmark_get_template` | Get template details by ID | Read |\n| `postmark_create_template` | Create a new template | Write |\n| `postmark_edit_template` | Update an existing template | Write |\n| `postmark_delete_template` | Delete a template permanently | Write |\n| `postmark_validate_template` | Validate a template against sample data | Read |\n\n### Bounces & Spam\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_bounce_counts` | Get aggregate bounce counts | Read |\n| `postmark_get_bounces` | List bounces with filters | Read |\n| `postmark_get_spam_complaints` | Get spam complaint counts | Read |\n| `postmark_check_spam_score` | Check spam score of raw email | Read |\n\n### Statistics & Engagement\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_outbound_overview` | Get outbound statistics overview | Read |\n| `postmark_get_email_open_counts` | Get email open counts | Read |\n| `postmark_get_click_counts` | Get link click counts | Read |\n| `postmark_get_email_client_usage` | Get email client usage statistics | Read |\n| `postmark_get_browser_usage` | Get browser usage for clicks | Read |\n| `postmark_get_browser_platform_usage` | Get browser platform usage | Read |\n| `postmark_get_clicks_by_browser_family` | Get clicks grouped by browser | Read |\n| `postmark_get_clicks_by_location` | Get clicks by content type (HTML/Text) | Read |\n| `postmark_get_opens_by_platform` | Get opens by platform | Read |\n| `postmark_get_tracked_email_counts` | Get counts of tracked emails | Read |\n\n### Suppressions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_suppressions` | List suppressed email addresses | Read |\n| `postmark_create_suppressions` | Add addresses to suppression list | Write |\n| `postmark_delete_suppressions` | Remove addresses from suppression list | Write |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_webhooks` | List all webhooks | Read |\n| `postmark_get_webhook` | Get webhook details | Read |\n| `postmark_create_webhook` | Create a new webhook | Write |\n| `postmark_edit_webhook` | Update a webhook's URL or triggers | Write |\n| `postmark_delete_webhook` | Delete a webhook permanently | Write |\n\n### Inbound Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_inbound_rules` | List inbound rule triggers | Read |\n| `postmark_create_inbound_rule` | Create an inbound rule | Write |\n| `postmark_delete_inbound_rule` | Delete an inbound rule | Write |\n\n### Server Configuration\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_server` | Get server configuration details | Read |\n| `postmark_edit_server` | Update server settings | Write |\n\n## Code Examples\n\n### Get outbound overview\n\n```bash\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" \\\n  --params '{\n    \"from\": \"2024-01-01\",\n    \"to\": \"2024-01-31\"\n  }'\n```\n\n### Search outbound messages\n\n```bash\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" \\\n  --params '{\n    \"recipient\": \"customer@example.com\",\n    \"status\": \"sent\",\n    \"tag\": \"welcome\"\n  }'\n```\n\n### Get template details\n\n```bash\nclawlink_call_tool --tool \"postmark_get_template\" \\\n  --params '{\n    \"template_id\": \"TEMPLATE_ID\"\n  }'\n```\n\n### Create a webhook\n\n```bash\nclawlink_call_tool --tool \"postmark_create_webhook\" \\\n  --params '{\n    \"url\": \"https://example.com/webhook/postmark\",\n    \"triggers\": {\n      \"open\": true,\n      \"click\": true,\n      \"bounce\": true,\n      \"spam_complaint\": true\n    },\n    \"http_headers\": {\n      \"Authorization\": \"Bearer secret_token\"\n    }\n  }'\n```\n\n### List suppressions\n\n```bash\nclawlink_call_tool --tool \"postmark_list_suppressions\" \\\n  --params '{\n    \"message_stream\": \"outbound\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Postmark is connected.\n2. Call `clawlink_list_tools --integration postmark` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `postmark`.\n5. If no Postmark tools appear, direct the user to https://claw-link.dev/dashboard?add=postmark.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → search → describe → call                      │\n│                                                             │\n│  Example: Get outbound overview → List templates → Report  │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call           │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                  │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Postmark API has rate limits. Use exponential backoff when encountering 429 errors.\n- SpamComplaint suppressions cannot be removed from the suppression list — only HardBounce and ManualSuppression can be deleted.\n- Archived message streams are permanently deleted after 45 days.\n- Webhook triggers require link tracking to be enabled for click and open events.\n- Date range filters use ISO 8601 format (YYYY-MM-DD).\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration postmark`. |\n| Missing connection | Postmark is not connected. Direct the user to https://claw-link.dev/dashboard?add=postmark. |\n| `not_found` | Template, webhook, or stream does not exist. Check the ID. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `postmark`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview)\n- [Message Streams API](https://postmarkapp.com/developer/api/message-streams)\n- [Templates API](https://postmarkapp.com/developer/api/templates)\n- [Webhooks API](https://postmarkapp.com/developer/api/webhooks)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=postmark-email\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Postmark](https://clawhub.ai/hith3sh/postmark-email) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=postmark-email)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"postmark-email\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1780989345661\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nInspect transactional email activity, manage templates, review message delivery events, configure webhooks, and administer Postmark email workflows via the Postmark API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, support teams, and email operations staff use this skill to inspect Postmark delivery activity, troubleshoot bounces and spam complaints, manage templates and message streams, and configure webhooks or server settings through confirmed Postmark tool calls.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The integration depends on ClawLink and connected Postmark credentials for server access.\n\nMitigation: Install only from a trusted ClawHub source, use a narrowly scoped and revocable Postmark token where possible, and revoke credentials when the integration is no longer needed.\n\nRisk: Write-capable tools can create, update, archive, or delete Postmark resources such as templates, webhooks, suppressions, message streams, inbound rules, and server settings.\n\nMitigation: Review write previews, confirm the target resource and intended effect with the user, and execute write calls only after the preview matches the user's request.\n\nRisk: Server configuration changes can affect all email sending on the connected Postmark server.\n\nMitigation: Prefer read and describe operations before writes, validate parameters against the live tool schema, and reserve server-level changes for explicit administrative requests.\n\n## Reference(s):\n\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview)\n- [Postmark Message Streams API](https://postmarkapp.com/developer/api/message-streams)\n- [Postmark Templates API](https://postmarkapp.com/developer/api/templates)\n- [Postmark Webhooks API](https://postmarkapp.com/developer/api/webhooks)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=postmark-email)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May initiate Postmark tool calls through ClawLink after connection checks and user confirmation for writes.]\n\n## Skill Version(s):\n\n1.0.5 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 6160 bytes\n\nFiles: skill-card.md (2577b), SKILL.md (15749b), _meta.json (133b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: postmark-email\ndescription: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this skill when users want to monitor email delivery, manage templates, check bounce and spam reports, and configure transactional email workflows via Postmark.\n---\n\n# Postmark Email\n\n![Postmark Email](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/postmark.svg)\n\nAccess Postmark's transactional email platform via the Postmark API. Inspect outbound messages, templates, and delivery events. Review bounce, spam, and engagement statistics. Manage webhooks and message streams.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Postmark API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Postmark |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Postmark |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│  Postmark API   │\n│   (User Chat)   │     │   (API Key)  │     │                  │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n          │                       │                       │\n          │  1. Install Plugin   │                       │\n          │2. Pair Device      │                       │\n          │3. Connect Postmark  │                       │\n          │                      │  4. Secure Proxy      │\n          │                      │  5. API Requests      │\n          │                      │                       │\n          ▼ ▼                       ▼\n    ┌──────────┐           ┌──────────┐           ┌──────────┐\n    │  SKILL   │           │ Dashboard│           │ Postmark │\n    │  File    │           │ Auth     │           │ Platform │\n    └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Postmark again.\"\n\n## Quick Start\n\n```bash\n# Get outbound overview\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" --params '{}'\n\n# Search outbound messages\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" --params '{\"status\": \"sent\"}'\n\n# List templates\nclawlink_call_tool --tool \"postmark_list_templates\" --params '{}'\n```\n\n## Authentication\n\nAll Postmark tool calls are authenticated automatically by ClawLink using the user's Postmark account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every Postmark API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=postmark and connect Postmark.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `postmark` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration postmark\n```\n\n**Response:** Returns the live tool catalog for Postmark.\n\n### Reconnect\n\nIf Postmark tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=postmark\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration postmark`\n\n## Security& Permissions\n\n- Access is scoped to messages, templates, streams, and webhooks within the connected Postmark server.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete webhook, archive stream) must be confirmed.\n- Server configuration changes affect all email sending on that server.\n\n## Tool Reference\n\n### Message Streams\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_message_streams` | List all message streams for a server | Read |\n| `postmark_get_message_stream` | Get details of a specific stream | Read |\n| `postmark_create_message_stream` | Create a new message stream | Write |\n| `postmark_update_message_stream` | Update a stream's name or description | Write |\n| `postmark_archive_message_stream` | Archive a message stream (soft delete) | Write |\n| `postmark_unarchive_message_stream` | Restore an archived stream | Write |\n\n### Outbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_outbound_messages` | Search sent messages with filters | Read |\n| `postmark_get_sent_counts` | Get sent message counts by date range | Read |\n| `postmark_get_delivery_stats` | Get delivery statistics | Read |\n| `postmark_list_outbound_message_opens` | List open events for outbound messages | Read |\n| `postmark_list_outbound_message_clicks` | List click events for outbound messages | Read |\n\n### Inbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_inbound_messages` | Search inbound messages | Read |\n\n### Templates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_templates` | List all templates | Read |\n| `postmark_get_template` | Get template details by ID | Read |\n| `postmark_create_template` | Create a new template | Write |\n| `postmark_edit_template` | Update an existing template | Write |\n| `postmark_delete_template` | Delete a template permanently | Write |\n| `postmark_validate_template` | Validate a template against sample data | Read |\n\n### Bounces & Spam\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_bounce_counts` | Get aggregate bounce counts | Read |\n| `postmark_get_bounces` | List bounces with filters | Read |\n| `postmark_get_spam_complaints` | Get spam complaint counts | Read |\n| `postmark_check_spam_score` | Check spam score of raw email | Read |\n\n### Statistics & Engagement\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_outbound_overview` | Get outbound statistics overview | Read |\n| `postmark_get_email_open_counts` | Get email open counts | Read |\n| `postmark_get_click_counts` | Get link click counts | Read |\n| `postmark_get_email_client_usage` | Get email client usage statistics | Read |\n| `postmark_get_browser_usage` | Get browser usage for clicks | Read |\n| `postmark_get_browser_platform_usage` | Get browser platform usage | Read |\n| `postmark_get_clicks_by_browser_family` | Get clicks grouped by browser | Read |\n| `postmark_get_clicks_by_location` | Get clicks by content type (HTML/Text) | Read |\n| `postmark_get_opens_by_platform` | Get opens by platform | Read |\n| `postmark_get_tracked_email_counts` | Get counts of tracked emails | Read |\n\n### Suppressions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_suppressions` | List suppressed email addresses | Read |\n| `postmark_create_suppressions` | Add addresses to suppression list | Write |\n| `postmark_delete_suppressions` | Remove addresses from suppression list | Write |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_webhooks` | List all webhooks | Read |\n| `postmark_get_webhook` | Get webhook details | Read |\n| `postmark_create_webhook` | Create a new webhook | Write |\n| `postmark_edit_webhook` | Update a webhook's URL or triggers | Write |\n| `postmark_delete_webhook` | Delete a webhook permanently | Write |\n\n### Inbound Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_inbound_rules` | List inbound rule triggers | Read |\n| `postmark_create_inbound_rule` | Create an inbound rule | Write |\n| `postmark_delete_inbound_rule` | Delete an inbound rule | Write |\n\n### Server Configuration\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_server` | Get server configuration details | Read |\n| `postmark_edit_server` | Update server settings | Write |\n\n## Code Examples\n\n### Get outbound overview\n\n```bash\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" \\\n  --params '{\n    \"from\": \"2024-01-01\",\n    \"to\": \"2024-01-31\"\n  }'\n```\n\n### Search outbound messages\n\n```bash\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" \\\n  --params '{\n    \"recipient\": \"customer@example.com\",\n    \"status\": \"sent\",\n    \"tag\": \"welcome\"\n  }'\n```\n\n### Get template details\n\n```bash\nclawlink_call_tool --tool \"postmark_get_template\" \\\n  --params '{\n    \"template_id\": \"TEMPLATE_ID\"\n  }'\n```\n\n### Create a webhook\n\n```bash\nclawlink_call_tool --tool \"postmark_create_webhook\" \\\n  --params '{\n    \"url\": \"https://example.com/webhook/postmark\",\n    \"triggers\": {\n      \"open\": true,\n      \"click\": true,\n      \"bounce\": true,\n      \"spam_complaint\": true\n    },\n    \"http_headers\": {\n      \"Authorization\": \"Bearer secret_token\"\n    }\n  }'\n```\n\n### List suppressions\n\n```bash\nclawlink_call_tool --tool \"postmark_list_suppressions\" \\\n  --params '{\n    \"message_stream\": \"outbound\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Postmark is connected.\n2. Call `clawlink_list_tools --integration postmark` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `postmark`.\n5. If no Postmark tools appear, direct the user to https://claw-link.dev/dashboard?add=postmark.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → search → describe → call                      │\n│                                                             │\n│  Example: Get outbound overview → List templates → Report  │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call           │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                  │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Postmark API has rate limits. Use exponential backoff when encountering 429 errors.\n- SpamComplaint suppressions cannot be removed from the suppression list — only HardBounce and ManualSuppression can be deleted.\n- Archived message streams are permanently deleted after 45 days.\n- Webhook triggers require link tracking to be enabled for click and open events.\n- Date range filters use ISO 8601 format (YYYY-MM-DD).\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration postmark`. |\n| Missing connection | Postmark is not connected. Direct the user to https://claw-link.dev/dashboard?add=postmark. |\n| `not_found` | Template, webhook, or stream does not exist. Check the ID. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `postmark`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview)\n- [Message Streams API](https://postmarkapp.com/developer/api/message-streams)\n- [Templates API](https://postmarkapp.com/developer/api/templates)\n- [Webhooks API](https://postmarkapp.com/developer/api/webhooks)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Postmark](https://clawhub.ai/hith3sh/postmark-email) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"postmark-email\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1780981356400\n}\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nInspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users and developers use this skill to inspect Postmark email delivery activity, manage templates, review bounces and spam reports, and configure transactional email workflows through ClawLink-mediated Postmark API tools. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Postmark and ClawLink access can expose sensitive business-email data and account capabilities. <br>\nMitigation: Install only when the user trusts ClawLink and intends to connect it to their Postmark account. <br>\nRisk: Write operations can change webhooks, templates, suppressions, message streams, or server settings. <br>\nMitigation: Review targets and intended effects carefully, preview write actions where available, and require explicit user confirmation before execution. <br>\nRisk: Webhook secrets and Postmark tokens may be sensitive if included in chat or examples. <br>\nMitigation: Do not paste real webhook secrets or Postmark tokens into chat, command examples, or skill output. <br>\n\n\n## Reference(s): <br>\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview) <br>\n- [Postmark Message Streams API](https://postmarkapp.com/developer/api/message-streams) <br>\n- [Postmark Templates API](https://postmarkapp.com/developer/api/templates) <br>\n- [Postmark Webhooks API](https://postmarkapp.com/developer/api/webhooks) <br>\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration, API calls, markdown] <br>\n**Output Format:** [Markdown with inline shell commands and JSON tool-call parameters] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires a connected Postmark account through ClawLink; write actions should be previewed and confirmed before execution.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 3 files, 6174 bytes\n\nFiles: skill-card.md (2653b), SKILL.md (15749b), _meta.json (133b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: postmark-email\ndescription: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this skill when users want to monitor email delivery, manage templates, check bounce and spam reports, and configure transactional email workflows via Postmark.\n---\n\n# Postmark Email\n\n![Postmark Email](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/postmark.svg)\n\nAccess Postmark's transactional email platform via the Postmark API. Inspect outbound messages, templates, and delivery events. Review bounce, spam, and engagement statistics. Manage webhooks and message streams.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Postmark API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Postmark |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Postmark |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│  Postmark API   │\n│   (User Chat)   │     │   (API Key)  │     │                  │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n          │                       │                       │\n          │  1. Install Plugin   │                       │\n          │2. Pair Device      │                       │\n          │3. Connect Postmark  │                       │\n          │                      │  4. Secure Proxy      │\n          │                      │  5. API Requests      │\n          │                      │                       │\n          ▼ ▼                       ▼\n    ┌──────────┐           ┌──────────┐           ┌──────────┐\n    │  SKILL   │           │ Dashboard│           │ Postmark │\n    │  File    │           │ Auth     │           │ Platform │\n    └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Postmark again.\"\n\n## Quick Start\n\n```bash\n# Get outbound overview\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" --params '{}'\n\n# Search outbound messages\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" --params '{\"status\": \"sent\"}'\n\n# List templates\nclawlink_call_tool --tool \"postmark_list_templates\" --params '{}'\n```\n\n## Authentication\n\nAll Postmark tool calls are authenticated automatically by ClawLink using the user's Postmark account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every Postmark API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=postmark and connect Postmark.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `postmark` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration postmark\n```\n\n**Response:** Returns the live tool catalog for Postmark.\n\n### Reconnect\n\nIf Postmark tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=postmark\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration postmark`\n\n## Security& Permissions\n\n- Access is scoped to messages, templates, streams, and webhooks within the connected Postmark server.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete webhook, archive stream) must be confirmed.\n- Server configuration changes affect all email sending on that server.\n\n## Tool Reference\n\n### Message Streams\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_message_streams` | List all message streams for a server | Read |\n| `postmark_get_message_stream` | Get details of a specific stream | Read |\n| `postmark_create_message_stream` | Create a new message stream | Write |\n| `postmark_update_message_stream` | Update a stream's name or description | Write |\n| `postmark_archive_message_stream` | Archive a message stream (soft delete) | Write |\n| `postmark_unarchive_message_stream` | Restore an archived stream | Write |\n\n### Outbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_outbound_messages` | Search sent messages with filters | Read |\n| `postmark_get_sent_counts` | Get sent message counts by date range | Read |\n| `postmark_get_delivery_stats` | Get delivery statistics | Read |\n| `postmark_list_outbound_message_opens` | List open events for outbound messages | Read |\n| `postmark_list_outbound_message_clicks` | List click events for outbound messages | Read |\n\n### Inbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_inbound_messages` | Search inbound messages | Read |\n\n### Templates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_templates` | List all templates | Read |\n| `postmark_get_template` | Get template details by ID | Read |\n| `postmark_create_template` | Create a new template | Write |\n| `postmark_edit_template` | Update an existing template | Write |\n| `postmark_delete_template` | Delete a template permanently | Write |\n| `postmark_validate_template` | Validate a template against sample data | Read |\n\n### Bounces & Spam\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_bounce_counts` | Get aggregate bounce counts | Read |\n| `postmark_get_bounces` | List bounces with filters | Read |\n| `postmark_get_spam_complaints` | Get spam complaint counts | Read |\n| `postmark_check_spam_score` | Check spam score of raw email | Read |\n\n### Statistics & Engagement\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_outbound_overview` | Get outbound statistics overview | Read |\n| `postmark_get_email_open_counts` | Get email open counts | Read |\n| `postmark_get_click_counts` | Get link click counts | Read |\n| `postmark_get_email_client_usage` | Get email client usage statistics | Read |\n| `postmark_get_browser_usage` | Get browser usage for clicks | Read |\n| `postmark_get_browser_platform_usage` | Get browser platform usage | Read |\n| `postmark_get_clicks_by_browser_family` | Get clicks grouped by browser | Read |\n| `postmark_get_clicks_by_location` | Get clicks by content type (HTML/Text) | Read |\n| `postmark_get_opens_by_platform` | Get opens by platform | Read |\n| `postmark_get_tracked_email_counts` | Get counts of tracked emails | Read |\n\n### Suppressions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_suppressions` | List suppressed email addresses | Read |\n| `postmark_create_suppressions` | Add addresses to suppression list | Write |\n| `postmark_delete_suppressions` | Remove addresses from suppression list | Write |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_webhooks` | List all webhooks | Read |\n| `postmark_get_webhook` | Get webhook details | Read |\n| `postmark_create_webhook` | Create a new webhook | Write |\n| `postmark_edit_webhook` | Update a webhook's URL or triggers | Write |\n| `postmark_delete_webhook` | Delete a webhook permanently | Write |\n\n### Inbound Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_inbound_rules` | List inbound rule triggers | Read |\n| `postmark_create_inbound_rule` | Create an inbound rule | Write |\n| `postmark_delete_inbound_rule` | Delete an inbound rule | Write |\n\n### Server Configuration\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_server` | Get server configuration details | Read |\n| `postmark_edit_server` | Update server settings | Write |\n\n## Code Examples\n\n### Get outbound overview\n\n```bash\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" \\\n  --params '{\n    \"from\": \"2024-01-01\",\n    \"to\": \"2024-01-31\"\n  }'\n```\n\n### Search outbound messages\n\n```bash\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" \\\n  --params '{\n    \"recipient\": \"customer@example.com\",\n    \"status\": \"sent\",\n    \"tag\": \"welcome\"\n  }'\n```\n\n### Get template details\n\n```bash\nclawlink_call_tool --tool \"postmark_get_template\" \\\n  --params '{\n    \"template_id\": \"TEMPLATE_ID\"\n  }'\n```\n\n### Create a webhook\n\n```bash\nclawlink_call_tool --tool \"postmark_create_webhook\" \\\n  --params '{\n    \"url\": \"https://example.com/webhook/postmark\",\n    \"triggers\": {\n      \"open\": true,\n      \"click\": true,\n      \"bounce\": true,\n      \"spam_complaint\": true\n    },\n    \"http_headers\": {\n      \"Authorization\": \"Bearer secret_token\"\n    }\n  }'\n```\n\n### List suppressions\n\n```bash\nclawlink_call_tool --tool \"postmark_list_suppressions\" \\\n  --params '{\n    \"message_stream\": \"outbound\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Postmark is connected.\n2. Call `clawlink_list_tools --integration postmark` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `postmark`.\n5. If no Postmark tools appear, direct the user to https://claw-link.dev/dashboard?add=postmark.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → search → describe → call                      │\n│                                                             │\n│  Example: Get outbound overview → List templates → Report  │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call           │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                  │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Postmark API has rate limits. Use exponential backoff when encountering 429 errors.\n- SpamComplaint suppressions cannot be removed from the suppression list — only HardBounce and ManualSuppression can be deleted.\n- Archived message streams are permanently deleted after 45 days.\n- Webhook triggers require link tracking to be enabled for click and open events.\n- Date range filters use ISO 8601 format (YYYY-MM-DD).\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration postmark`. |\n| Missing connection | Postmark is not connected. Direct the user to https://claw-link.dev/dashboard?add=postmark. |\n| `not_found` | Template, webhook, or stream does not exist. Check the ID. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `postmark`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview)\n- [Message Streams API](https://postmarkapp.com/developer/api/message-streams)\n- [Templates API](https://postmarkapp.com/developer/api/templates)\n- [Webhooks API](https://postmarkapp.com/developer/api/webhooks)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Postmark](https://clawhub.ai/hith3sh/postmark-email) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"postmark-email\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1780936861021\n}\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nInspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, operators, and support teams use this skill to inspect Postmark delivery activity, manage templates, review bounces and spam complaints, and configure message streams and webhooks through ClawLink-authenticated Postmark tools. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill requires access to sensitive Postmark credentials through ClawLink. <br>\nMitigation: Install only when the user trusts ClawLink to store and proxy Postmark account access. <br>\nRisk: Postmark operations can expose message bodies, recipient lists, suppression records, webhook headers, or bearer tokens. <br>\nMitigation: Avoid sharing sensitive Postmark data in chat unless explicitly needed for the task. <br>\nRisk: Write operations can change templates, webhooks, message streams, suppressions, inbound rules, or server configuration. <br>\nMitigation: Preview write operations and confirm the target resource and intended effect before execution. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/postmark-email) <br>\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview) <br>\n- [Postmark Message Streams API](https://postmarkapp.com/developer/api/message-streams) <br>\n- [Postmark Templates API](https://postmarkapp.com/developer/api/templates) <br>\n- [Postmark Webhooks API](https://postmarkapp.com/developer/api/webhooks) <br>\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown guidance with shell command examples and ClawLink tool-call parameters.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses the live ClawLink Postmark tool catalog as source of truth and requires previews plus explicit confirmation before write or destructive operations.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v0.1.1: 3 files, 5960 bytes\n\nFiles: skill-card.md (2086b), SKILL.md (15630b), _meta.json (133b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: postmark-email\ndescription: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this skill when users want to monitor email delivery, manage templates, check bounce and spam reports, and configure transactional email workflows via Postmark.\n---\n\n# Postmark Email\n\nAccess Postmark's transactional email platform via the Postmark API. Inspect outbound messages, templates, and delivery events. Review bounce, spam, and engagement statistics. Manage webhooks and message streams.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Postmark API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Postmark |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Postmark |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│  Postmark API   │\n│   (User Chat)   │     │   (API Key)  │     │                  │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n          │                       │                       │\n          │  1. Install Plugin   │                       │\n          │2. Pair Device      │                       │\n          │3. Connect Postmark  │                       │\n          │                      │  4. Secure Proxy      │\n          │                      │  5. API Requests      │\n          │                      │                       │\n          ▼ ▼                       ▼\n    ┌──────────┐           ┌──────────┐           ┌──────────┐\n    │  SKILL   │           │ Dashboard│           │ Postmark │\n    │  File    │           │ Auth     │           │ Platform │\n    └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Postmark again.\"\n\n## Quick Start\n\n```bash\n# Get outbound overview\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" --params '{}'\n\n# Search outbound messages\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" --params '{\"status\": \"sent\"}'\n\n# List templates\nclawlink_call_tool --tool \"postmark_list_templates\" --params '{}'\n```\n\n## Authentication\n\nAll Postmark tool calls are authenticated automatically by ClawLink using the user's Postmark account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every Postmark API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=postmark and connect Postmark.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `postmark` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration postmark\n```\n\n**Response:** Returns the live tool catalog for Postmark.\n\n### Reconnect\n\nIf Postmark tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=postmark\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration postmark`\n\n## Security& Permissions\n\n- Access is scoped to messages, templates, streams, and webhooks within the connected Postmark server.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete template, delete webhook, archive stream) must be confirmed.\n- Server configuration changes affect all email sending on that server.\n\n## Tool Reference\n\n### Message Streams\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_message_streams` | List all message streams for a server | Read |\n| `postmark_get_message_stream` | Get details of a specific stream | Read |\n| `postmark_create_message_stream` | Create a new message stream | Write |\n| `postmark_update_message_stream` | Update a stream's name or description | Write |\n| `postmark_archive_message_stream` | Archive a message stream (soft delete) | Write |\n| `postmark_unarchive_message_stream` | Restore an archived stream | Write |\n\n### Outbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_outbound_messages` | Search sent messages with filters | Read |\n| `postmark_get_sent_counts` | Get sent message counts by date range | Read |\n| `postmark_get_delivery_stats` | Get delivery statistics | Read |\n| `postmark_list_outbound_message_opens` | List open events for outbound messages | Read |\n| `postmark_list_outbound_message_clicks` | List click events for outbound messages | Read |\n\n### Inbound Messages\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_search_inbound_messages` | Search inbound messages | Read |\n\n### Templates\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_templates` | List all templates | Read |\n| `postmark_get_template` | Get template details by ID | Read |\n| `postmark_create_template` | Create a new template | Write |\n| `postmark_edit_template` | Update an existing template | Write |\n| `postmark_delete_template` | Delete a template permanently | Write |\n| `postmark_validate_template` | Validate a template against sample data | Read |\n\n### Bounces & Spam\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_bounce_counts` | Get aggregate bounce counts | Read |\n| `postmark_get_bounces` | List bounces with filters | Read |\n| `postmark_get_spam_complaints` | Get spam complaint counts | Read |\n| `postmark_check_spam_score` | Check spam score of raw email | Read |\n\n### Statistics & Engagement\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_outbound_overview` | Get outbound statistics overview | Read |\n| `postmark_get_email_open_counts` | Get email open counts | Read |\n| `postmark_get_click_counts` | Get link click counts | Read |\n| `postmark_get_email_client_usage` | Get email client usage statistics | Read |\n| `postmark_get_browser_usage` | Get browser usage for clicks | Read |\n| `postmark_get_browser_platform_usage` | Get browser platform usage | Read |\n| `postmark_get_clicks_by_browser_family` | Get clicks grouped by browser | Read |\n| `postmark_get_clicks_by_location` | Get clicks by content type (HTML/Text) | Read |\n| `postmark_get_opens_by_platform` | Get opens by platform | Read |\n| `postmark_get_tracked_email_counts` | Get counts of tracked emails | Read |\n\n### Suppressions\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_suppressions` | List suppressed email addresses | Read |\n| `postmark_create_suppressions` | Add addresses to suppression list | Write |\n| `postmark_delete_suppressions` | Remove addresses from suppression list | Write |\n\n### Webhooks\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_webhooks` | List all webhooks | Read |\n| `postmark_get_webhook` | Get webhook details | Read |\n| `postmark_create_webhook` | Create a new webhook | Write |\n| `postmark_edit_webhook` | Update a webhook's URL or triggers | Write |\n| `postmark_delete_webhook` | Delete a webhook permanently | Write |\n\n### Inbound Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_list_inbound_rules` | List inbound rule triggers | Read |\n| `postmark_create_inbound_rule` | Create an inbound rule | Write |\n| `postmark_delete_inbound_rule` | Delete an inbound rule | Write |\n\n### Server Configuration\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `postmark_get_server` | Get server configuration details | Read |\n| `postmark_edit_server` | Update server settings | Write |\n\n## Code Examples\n\n### Get outbound overview\n\n```bash\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" \\\n  --params '{\n    \"from\": \"2024-01-01\",\n    \"to\": \"2024-01-31\"\n  }'\n```\n\n### Search outbound messages\n\n```bash\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" \\\n  --params '{\n    \"recipient\": \"customer@example.com\",\n    \"status\": \"sent\",\n    \"tag\": \"welcome\"\n  }'\n```\n\n### Get template details\n\n```bash\nclawlink_call_tool --tool \"postmark_get_template\" \\\n  --params '{\n    \"template_id\": \"TEMPLATE_ID\"\n  }'\n```\n\n### Create a webhook\n\n```bash\nclawlink_call_tool --tool \"postmark_create_webhook\" \\\n  --params '{\n    \"url\": \"https://example.com/webhook/postmark\",\n    \"triggers\": {\n      \"open\": true,\n      \"click\": true,\n      \"bounce\": true,\n      \"spam_complaint\": true\n    },\n    \"http_headers\": {\n      \"Authorization\": \"Bearer secret_token\"\n    }\n  }'\n```\n\n### List suppressions\n\n```bash\nclawlink_call_tool --tool \"postmark_list_suppressions\" \\\n  --params '{\n    \"message_stream\": \"outbound\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Postmark is connected.\n2. Call `clawlink_list_tools --integration postmark` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `postmark`.\n5. If no Postmark tools appear, direct the user to https://claw-link.dev/dashboard?add=postmark.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → search → describe → call                      │\n│                                                             │\n│  Example: Get outbound overview → List templates → Report  │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call           │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                  │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Postmark API has rate limits. Use exponential backoff when encountering 429 errors.\n- SpamComplaint suppressions cannot be removed from the suppression list — only HardBounce and ManualSuppression can be deleted.\n- Archived message streams are permanently deleted after 45 days.\n- Webhook triggers require link tracking to be enabled for click and open events.\n- Date range filters use ISO 8601 format (YYYY-MM-DD).\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration postmark`. |\n| Missing connection | Postmark is not connected. Direct the user to https://claw-link.dev/dashboard?add=postmark. |\n| `not_found` | Template, webhook, or stream does not exist. Check the ID. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `postmark`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview)\n- [Message Streams API](https://postmarkapp.com/developer/api/message-streams)\n- [Templates API](https://postmarkapp.com/developer/api/templates)\n- [Webhooks API](https://postmarkapp.com/developer/api/webhooks)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [Postmark](https://clawhub.ai/hith3sh/postmark-email) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v0.1.1:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"postmark-email\",\n  \"version\": \"0.1.1\",\n  \"publishedAt\": 1780839286821\n}\n\nFile v0.1.1:skill-card.md\n\n## Description: <br>\nInspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nOpenClaw users and developers use this skill to inspect Postmark delivery activity, message streams, templates, bounces, suppressions, and webhooks. It also guides confirmed changes to Postmark resources when write operations are requested. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Review before execution as proposals could introduce incorrect or misleading guidance into skills. <br>\nMitigation: Review and scan skill before deployment. <br>\n\n## Reference(s): <br>\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview) <br>\n- [Postmark Message Streams API](https://postmarkapp.com/developer/api/message-streams) <br>\n- [Postmark Templates API](https://postmarkapp.com/developer/api/templates) <br>\n- [Postmark Webhooks API](https://postmarkapp.com/developer/api/webhooks) <br>\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw) <br>\n- [ClawLink Verification](https://claw-link.dev/verify) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Shell commands, Configuration instructions, API calls] <br>\n**Output Format:** [Markdown with inline bash commands and JSON tool parameters] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires a connected Postmark account through ClawLink; write operations require explicit user confirmation.] <br>\n\n## Skill Version(s): <br>\n0.1.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v0.1.0: 3 files, 3499 bytes\n\nFiles: skill-card.md (2322b), SKILL.md (5108b), _meta.json (133b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: postmark-email\ndescription: Inspect transactional email activity, templates, messages, and delivery workflows in Postmark — powered by ClawLink.\n---\n\n# Postmark\n\nWork with Postmark from chat — inspect transactional email activity, templates, messages, and delivery workflows.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Postmark API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Postmark at [claw-link.dev/dashboard?add=postmark](https://claw-link.dev/dashboard?add=postmark)\n7. When the user confirms Postmark is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `postmark` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Postmark\n\nTell the user to open https://claw-link.dev/dashboard?add=postmark and connect Postmark there. The page opens the add-connection panel filtered to Postmark. ClawLink's hosted page runs whichever provider flow is needed (hosted provider setup) — the user follows the hosted provider setup form. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `postmark`.\n\n## Using Postmark tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Postmark is connected.\n2. Call `clawlink_list_tools` with integration `postmark`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `postmark`.\n5. If no Postmark tools appear, direct the user to https://claw-link.dev/dashboard?add=postmark.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer read, list, search, and get operations before writes.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Postmark tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Inspect outbound messages, templates, and delivery events\n- Review bounce, spam, and activity data\n- Manage templates or server settings only after confirmation\n- Use read-first workflows for diagnostics and reporting\n- Confirm before changing transactional email configuration\n\n## Rules\n\n- Always use ClawLink tools for Postmark. Do not ask the user for separate Postmark credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before destructive, external-facing, or bulk write actions.\n- If Postmark is not connected, direct the user to https://claw-link.dev/dashboard?add=postmark.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Postmark API: https://postmarkapp.com/developer/api/overview\n\nFile v0.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"postmark-email\",\n  \"version\": \"0.1.0\",\n  \"publishedAt\": 1778998006760\n}\n\nFile v0.1.0:skill-card.md\n\n## Description: <br>\nInspect transactional email activity, templates, messages, and delivery workflows in Postmark - powered by ClawLink. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to inspect Postmark activity, templates, messages, and delivery workflows from chat through ClawLink. It supports read-first diagnostics and guided, confirmed changes to transactional email configuration when the connected account and live tool catalog allow them. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Postmark write actions can change templates, server settings, or other transactional email behavior. <br>\nMitigation: Use read-first workflows, preview proposed tool calls, and require explicit user confirmation before write, destructive, external-facing, or bulk actions. <br>\nRisk: A broad ClawLink connection could expose more Postmark access than the user needs for a specific task. <br>\nMitigation: Review ClawLink and the connected Postmark account separately, connect only the required account and permissions, and avoid sharing raw credentials in chat. <br>\n\n\n## Reference(s): <br>\n- [Postmark API](https://postmarkapp.com/developer/api/overview) <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw) <br>\n- [ClawLink Verification](https://claw-link.dev/verify) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Shell commands, API Calls, Configuration instructions] <br>\n**Output Format:** [Markdown with inline shell commands and tool-call guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses the live ClawLink Postmark tool catalog as the source of truth and requires confirmation before write or destructive actions.] <br>\n\n## Skill Version(s): <br>\n0.1.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Postmark Email Owner: hith3sh Summary: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this ski... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:15:45.661Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffi","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│  Postmark API   │\n│   (User Chat)   │     │   (API Key)  │     │                  │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n          │                       │                       │\n          │  1. Install Plugin   │                       │\n          │2. Pair Device      │                       │\n          │3. Connect Postmark  │                       │\n          │                      │  4. Secure Proxy      │\n          │                      │  5. API Requests      │\n          │                      │                       │\n          ▼ ▼                       ▼\n    ┌──────────┐           ┌──────────┐           ┌──────────┐\n    │  SKILL   │           │ Dashboard│           │ Postmark │\n    │  File    │           │ Auth     │           │ Platform │\n    └──────────┘           └──────────┘           └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# Get outbound overview\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" --params '{}'\n\n# Search outbound messages\nclawlink_call_tool --tool \"postmark_search_outbound_messages\" --params '{\"status\": \"sent\"}'\n\n# List templates\nclawlink_call_tool --tool \"postmark_list_templates\" --params '{}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration postmark"},{"language":"bash","snippet":"clawlink_call_tool --tool \"postmark_get_outbound_overview\" \\\n  --params '{\n    \"from\": \"2024-01-01\",\n    \"to\": \"2024-01-31\"\n  }'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: postmark-email\ndescription: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this skill when users want to monitor email delivery, manage templates, check bounce and spam reports, and configure transactional email workflows via Postmark.\n---\n\n# Postmark Email\n\n![Postmark Email](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/postmark.svg)\n\nAccess Postmark's transactional email platform via the Postmark API. Inspect outbound messages, templates, and delivery events. Review bounce, spam, and engagement statistics. Manage webhooks and message streams.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=postmark-email) for hosted connection flows and credentials so you do not need to configure Postmark API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Postmark |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Postmark |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│  Postmark API   │\n│   (User Chat)   │     │   (API Key)  │     │                  │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n          │                       │                       │\n          │  1. Install Plugin   │                       │\n          │2. Pair Device      │                       │\n          │3. Connect Postmark  │                       │\n          │                      │  4. Secure Proxy      │\n          │                      │  5. API Requests      │\n          │                      │                       │\n          ▼ ▼                       ▼\n    ┌──────────┐           ┌──────────┐           ┌──────────┐\n    │  SKILL   │           │ Dashboard│           │ Postmark │\n    │  File    │           │ Auth     │           │ Platform │\n    └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Postmark again.\"\n\n## Quick Start\n\n```bash\n# Get outbound overview\nclawlink_call_tool --tool \"postmark_get_outbound_overview\" --params '{}'"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"postmark-email\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1780989345661\n}"},{"path":"skill-card.md","content":"## Description:\n\nInspect transactional email activity, manage templates, review message delivery events, configure webhooks, and administer Postmark email workflows via the Postmark API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, support teams, and email operations staff use this skill to inspect Postmark delivery activity, troubleshoot bounces and spam complaints, manage templates and message streams, and configure webhooks or server settings through confirmed Postmark tool calls.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The integration depends on ClawLink and connected Postmark credentials for server access.\n\nMitigation: Install only from a trusted ClawHub source, use a narrowly scoped and revocable Postmark token where possible, and revoke credentials when the integration is no longer needed.\n\nRisk: Write-capable tools can create, update, archive, or delete Postmark resources such as templates, webhooks, suppressions, message streams, inbound rules, and server settings.\n\nMitigation: Review write previews, confirm the target resource and intended effect with the user, and execute write calls only after the preview matches the user's request.\n\nRisk: Server configuration changes can affect all email sending on the connected Postmark server.\n\nMitigation: Prefer read and describe operations before writes, validate parameters against the live tool schema, and reserve server-level changes for explicit administrative requests.\n\n## Reference(s):\n\n- [Postmark API Documentation](https://postmarkapp.com/developer/api/overview)\n- [Postmark Message Streams API](https://postmarkapp.com/developer/api/message-streams)\n- [Postmark Templates API](https://postmarkapp.com/developer/api/templates)\n- [Postmark Webhooks API](https://postmarkapp.com/developer/api/webhooks)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=postmark-email)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May initiate Postmark tool calls through ClawLink after connection checks and user confirmation for writes.]\n\n## Skill Version(s):\n\n1.0.5 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this ski... Skill: Postmark Email Owner: hith3sh Summary: Inspect transactional email activity, manage templates, review message delivery events, and configure webhooks in Postmark via the Postmark API. Use this ski... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-06-09T07:15:45.661Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffi","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1082,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:55:08.129Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:55:08.129Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:08:41.283Z","emptyReason":null},"items":[{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-10T18:48:31.762Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}