Wenjuan Survey Assistant

The problem

When a request such as 'make a survey' needs to become a real Wenjuan.com project, the hard part is not creating a form but keeping the workflow consistent: local question JSON is edited repeatedly, the publish decision is unclear, survey, vote, form, and assess types are mixed up, and report viewing, overview stats, and raw export are scattered across different APIs with separate auth and signing concerns.

How it works

The skill packages Wenjuan.com operations into confirmable workflows:
- Create and publish: show the title, type, and question summary first; after user confirmation, run workflow_create_and_publish.js to log in, import, publish, and poll review status. Question input can come from templates, local JSON, a URL, or stdin.
- Edit safely: stop collection and archive the project before changing structure or project fields, so live surveys are not modified in place.
- Inspect data: open_report.js opens the report page, overview_stats.js returns answers, views, and completion metrics, and export_data.js downloads raw responses. The related endpoints reuse the signing logic in generate_sign.js.

Boundaries

It is aimed at Wenjuan.com accounts and at turning document outlines into publishable surveys. It does not support matrix question types, assess questions must include explicit correct answers, and repeated test projects for the same topic should be avoided. Re-login, mobile binding, or review status changes need to be handled according to the relevant docs.