skills/suprsend-docs-support/SKILL.md
Default skill for any SuprSend question that isn't strictly authoring JSON or running a CLI command. Fetch, search, read, and explain SuprSend documentation; answer "how does X work", "what is X", "show me the docs for X". Provides docs-over-SSH (ssh suprsend.sh), the .md-suffix raw markdown URL convention, LLM-friendly bulk endpoints, in-app chat, AI copilot, Slack community, and email support. Examples that should load this skill: "fetch batching documentation", "explain digest nodes", "show me the inbox channel docs", "what fields does an email variant have", "how do conditions work in templates".
npx skillsauth add suprsend/skills suprsend-docs-supportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
SuprSend docs are available at docs.suprsend.com. For agent access, pick the method that matches the tools available in the environment:
ssh is available)If the agent can run shell commands, use the docs-over-SSH service. It exposes the full docs tree as a virtual filesystem under /suprsend/, browsable with standard Unix tools:
# Search for a topic across all docs
ssh suprsend.sh grep -rl 'inbox' /suprsend/
# Read a specific guide
ssh suprsend.sh cat /suprsend/docs/quick-start-guide.md
# Find SDK reference pages
ssh suprsend.sh find /suprsend/reference -name '*sdk*.md'
# Search the API reference with context
ssh suprsend.sh grep -r 'workflow' /suprsend/reference/ --include='*.md' -l
The VFS mirrors the live URL structure: /suprsend/reference/agent-sdk.md ↔ https://docs.suprsend.com/reference/agent-sdk. Any standard Unix tool (grep, find, cat, head, tail) works.
Run ssh suprsend.sh agents to print these instructions in a form you can append to an AGENTS.md or similar agent-instruction file.
.md to any docs URL (when ssh is not available)Every page at https://docs.suprsend.com/<path> is also served as raw markdown at https://docs.suprsend.com/<path>.md. Use this when the agent can fetch URLs but cannot run shell commands:
https://docs.suprsend.com/docs/quick-start-guidehttps://docs.suprsend.com/docs/quick-start-guide.mdThis works for both /docs/ (guides) and /reference/ (API reference) paths.
For wholesale ingestion rather than targeted lookups:
https://docs.suprsend.com/llms.txt — lightweight page listing with descriptionshttps://docs.suprsend.com/llms-full.txt — complete documentation in a single fileKai is SuprSend's built-in AI copilot, available inside the dashboard at app.suprsend.com. Access it via the orb in the bottom-right corner, or use the keyboard shortcut:
Cmd + /Ctrl + /Kai can answer questions about SuprSend features, help debug workflow configurations, and guide you through setup steps.
Users logged into the SuprSend dashboard can reach the support team directly. Click the ? (help) icon in the top navigation bar, then select "Chat with us" from the dropdown menu.
Join the SuprSend community Slack for discussions, questions, and announcements:
https://join.slack.com/t/suprsendcommunity/shared_invite/zt-3932rw936-XNWY1RC8bsffh4if4ZyoXQ
For detailed issues, bug reports, or account-specific questions:
development
JSON schema for authoring or editing SuprSend template variants (channel + locale + tenant + content). Loads the variant envelope, per-channel content schemas, and Handlebars/JSONNET syntax references needed to write valid template JSON. Covers all 9 channels: email, sms, whatsapp, inbox, slack, ms_teams, androidpush, iospush, webpush. Use ONLY when the user wants the agent to create, modify, or edit a template variant (e.g. "build an SMS variant", "add a French locale", "create a tenant-specific welcome email"). Do NOT load for documentation, lookup, or conceptual questions ("what is a variant", "how does templating work", "explain WhatsApp templates") — load suprsend-docs-support for those.
development
JSON schema for authoring or editing SuprSend workflow definitions. Loads the schemas and examples needed to write valid workflow JSON. Use ONLY when the user wants the agent to create, modify, or edit a workflow (e.g. "build a workflow that sends a welcome email", "add a 1h delay before the SMS step", "wire a branch on user plan"). Do NOT load for documentation, lookup, or conceptual questions ("how does batching work", "what is the batch node", "explain delivery nodes") — load suprsend-docs-support for those.
tools
SuprSend CLI tool for managing SuprSend account and resources from the command line — workspaces, workflows, templates, categories, events, schemas, and translations. Use ONLY when the user wants the agent to RUN a `suprsend ...` command (e.g. "push my template", "pull all workflows", "sync staging to prod", "generate Python types") or asks about a specific CLI command's flags/behavior ("what does `suprsend template commit --dry-run` do?"). Do NOT load for documentation, lookup, or conceptual SuprSend questions ("how does batching work", "what is a variant", "explain delivery nodes") — load `suprsend-docs-support` for those. Do NOT load when the user is authoring workflow or template JSON without invoking the CLI — load `suprsend-workflow-schema` or `suprsend-template-schema` for those.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.