Wenjuan Survey Assistant

Problem

When a task requires moving from topic to questions to publication and data review for surveys, votes, forms, or assessments, manually switching to the Wenjuan web console breaks the workflow. This skill keeps those actions script-driven. It distinguishes --type survey, --type vote, --type form, and --type assess, so votes and forms are not mistakenly created as surveys. Question content can come from local JSON, a URL, or standard input; txt, docx, xlsx, and pdf drafts can be converted into question JSON first.

How It Works

The main path is workflow_create_and_publish.js: confirm before publishing, then log in, create and import, publish, and poll review. Editing stops collection with publish_survey(action=stop), archives the project, and then uses scripts such as update_project.js and edit_question.js. For data, overview_stats.js reports responses, views, and completion rate; open_report.js opens the report page; export_data.js exports raw responses.

Boundaries

• Local tokens expire; re-scan login when needed, and use WENJUAN_TOKEN_DIR for a persistent token directory.
• Signed requests rely on generate_sign.js; signatures are short-lived and must be generated per request.
• First publication may require mobile binding. Handle errors such as JWT_EXPIRED and NOT_BIND_MOBILE according to the returned guidance.