Support Flow Builder
v1.0.0Turn ecommerce support policies, ticket patterns, and channel context into reusable support flows, agent playbooks, macros, bot handoff logic, and governance...
⭐ 0· 48·0 current·0 all-time
byhaidong@harrylabsj
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (support flow design for ecommerce CX) align with included code and SKILL.md. The skill does not request cloud credentials, binaries, or config paths that would be unrelated to producing policy-grounded flow documents.
Instruction Scope
SKILL.md instructs the agent to collect scenario and policy context and produce a markdown pack. It explicitly states it does not connect to live helpdesks, edit production bots, or inspect real ticket systems. The included handler.py only processes input text and renders a markdown output; there are no instructions to read unrelated files, environment variables, or external endpoints.
Install Mechanism
There is no install spec (instruction-first). No download/install steps are present. The bundle includes a small local Python handler and tests but nothing that fetches or executes remote code.
Credentials
The skill declares no required environment variables, credentials, or config paths. The code does not access os.environ or other secrets. The lack of requested secrets is proportionate to the skill's documentation/templating purpose.
Persistence & Privilege
Flags are default (always: false, user-invocable: true, disable-model-invocation: false). The skill does not persist configuration, modify other skills, or request permanent agent privileges.
Assessment
This skill appears internally consistent and safe for generating offline support flow documentation. Before installing or running: (1) review the included handler.py if you will run code locally — it only formats input into markdown and reads stdin/argv; (2) if you later integrate these outputs with live helpdesk systems or automation, you will need additional connectors and credentials — those integrations should be reviewed separately; (3) monitor future updates for added network calls or env-var access (those would be the main cause for concern). If you require stricter guarantees, run the provided tests in an isolated environment first and inspect any new versions for remote-install or secret-access behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk97atrz61n2w8apc71nqak9ghh84s9wg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.