Vote Duck Creator Assistant

The problem it solves

Building a poll, adjusting choices, and checking results usually means switching between a web console and ad hoc API calls. This skill moves the common Vote Duck workflow into a CLI: find templates, create a project, maintain choices and groups, upload assets, and pull voting or traffic data. It fits scripted campaign pages and routine data checks.

How it works

The skill depends on requests; asset upload also needs cos-python-sdk-v5. Auth reuses X-Openclaw-Token from ~/.toupiaoya/config.json or accepts --access-token.

• Template search: query by --keywords, --color, pagination, and sort fields, then pass the selected templateId to project create.
• Project creation: send briefTitle, briefDesc, voteType, time range, and groupList; if times are omitted, the service defaults to a 10-day window.
• Choice and group management: use get_choices, add_choices, update_choices, and group commands to manage content, cover, rank, and group placement.
• Data and assets: project list returns projects; voting data returns obj, map, and list; project view-data returns uv, pv, spv, and fpv; uploads use COS PutObject before saving the asset.

Boundaries

It assumes an existing Vote Duck account and token. Responses are JSON-first; when id == 0, the payload may only include data.code for preview URL assembly. Creation failures commonly show 400 or 404. If COS upload succeeds but saveFile fails, the error retains the cos fields for debugging.