Run any Skill in Manus with one click

editor-export

Stars1

Forks0

UpdatedApril 29, 2026 at 12:38

Export reviewed quiz-editor JSON state to Moodle XML. Use when opening generated JSON in the editor, checking question statuses, and running the status-filtered json_to_moodle_xml.py script.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

avidaldo

avidaldo/tests-generator

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	editor-export
description	Export reviewed quiz-editor JSON state to Moodle XML. Use when opening generated JSON in the editor, checking question statuses, and running the status-filtered json_to_moodle_xml.py script.
argument-hint	Optional: output path or status filter to use

Editor Export Workflow

This skill covers the final stage of the quiz pipeline: reviewed JSON state to Moodle XML. The canonical workflow lives in prompts/AGENTS.md, the editor context in editor/AGENTS.md, and the export behavior in resources/json_to_moodle_xml.py.

When To Use

Export reviewed editor state to Moodle XML.
Check which statuses should be included in an export.
Re-run export after human review changes in the editor.

Procedure

Confirm the input format. Use this skill only with JSON state compatible with editor/file_io/state_io.py.
Review before export. If the JSON has not been reviewed yet, open it in the editor workflow documented in editor/README.md and complete human review first.
Choose the status scope. Default export behavior is lista only. Include revisar explicitly only when the user asks for a broader export, and use --all-statuses only for exceptional cases.
Run the export script. Use one of the documented commands from resources/json_to_moodle_xml.py:
- python resources/json_to_moodle_xml.py session.json exam.xml
- python resources/json_to_moodle_xml.py session.json exam.xml --status lista revisar
- python resources/json_to_moodle_xml.py session.json exam.xml --all-statuses
- python resources/json_to_moodle_xml.py session.json . --verbose
Validate the result. Confirm the output path is correct, the export completed without JSON parse errors, and the status filter matches the user's intent.

Guardrails

Do not bypass the editor review step by default.
Do not assume pendiente or revisar should ship to Moodle unless the user explicitly requests that scope.
Keep the export script as the canonical XML path instead of hand-editing XML unless the task specifically requires XML changes.

More from this repository

same repository

finish-question-coverage

avidaldo/tests-generator

Continue Stage 3 generation across an approved Stage 2 scope until the selected subcategories have tracked SURF coverage or a declared stop condition is reached. Use when you want an advanced delegated or background lane that keeps designing batches after the first breadth-first wave.

2026-05-191

generate-question-batches

avidaldo/tests-generator

Traverse multiple Stage 2 subcategory files in one Stage 3 run. Use when you want an advanced delegated or background lane that writes at most one new question batch per subcategory while keeping checkpointed progress under a user-provided Stage 3 root.

2026-05-191

summarize-all-sources

avidaldo/tests-generator

Fan out Stage 1 summarization across multiple material paths. Use when a subject spans several repos or topic folders and you want one summary per path while keeping each summarization in an isolated context window.

2026-05-031

customization-audit

avidaldo/tests-generator

Fetch current VS Code customization docs and audit this repo's `.github` customization layer for deprecated patterns, missing recommended fields, and newly available primitives.

2026-04-301

notebook-hygiene

avidaldo/tests-generator

Install all four enforcement layers for notebook output hygiene in a new project. Use when setting up notebook privacy controls, nbstripout integration, CI output checks, or agent hooks for .ipynb files.

2026-04-301

name	editor-export
description	Export reviewed quiz-editor JSON state to Moodle XML. Use when opening generated JSON in the editor, checking question statuses, and running the status-filtered json_to_moodle_xml.py script.
argument-hint	Optional: output path or status filter to use

Editor Export Workflow

When To Use

Export reviewed editor state to Moodle XML.
Check which statuses should be included in an export.
Re-run export after human review changes in the editor.

Procedure

Confirm the input format. Use this skill only with JSON state compatible with editor/file_io/state_io.py.
Review before export. If the JSON has not been reviewed yet, open it in the editor workflow documented in editor/README.md and complete human review first.
Choose the status scope. Default export behavior is lista only. Include revisar explicitly only when the user asks for a broader export, and use --all-statuses only for exceptional cases.
Run the export script. Use one of the documented commands from resources/json_to_moodle_xml.py:
- python resources/json_to_moodle_xml.py session.json exam.xml
- python resources/json_to_moodle_xml.py session.json exam.xml --status lista revisar
- python resources/json_to_moodle_xml.py session.json exam.xml --all-statuses
- python resources/json_to_moodle_xml.py session.json . --verbose
Validate the result. Confirm the output path is correct, the export completed without JSON parse errors, and the status filter matches the user's intent.

Guardrails

Do not bypass the editor review step by default.
Do not assume pendiente or revisar should ship to Moodle unless the user explicitly requests that scope.
Keep the export script as the canonical XML path instead of hand-editing XML unless the task specifically requires XML changes.