Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking within.
Task Starting Point
First read the material, confirm the delivery purpose, target size or duration, scope of modification, and required format. Details that can be determined from the task and material should directly adopt reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand it over to the soundcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/soundcraft-skills --skill soundcraft-editor. The currently added skill is a local candidate; before release, use the local companion plugin, and do not treat this installation command as proof of release.
Execution Steps
- Group by instrument and role, first mute effects to listen to the dry sound.
- Establish the balance of drums, bass, and main melody, and control panning.
- Use a small amount of EQ to carve out frequency space, then add spatial effects.
- Compare reference loudness without pursuing excessive limiting.
Tool Implementation
Use open_session/new_session to manage sessions; import_audio to import, inspect_session to check, and consult real-time tools for other edits; save_session to save the project, bounce_mix to output audio.
First read the actual tool schema, then fill in parameters; use the returned values for object or document IDs. Queried commands must be available on the current backend. Before saving, choose a new output path and keep the input. If the required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as the real thing.
Result Checking
- Low frequencies are not muddy, and the main melody is clear.
- Key parts do not disappear in mono.
- The project retains editable tracks and effect parameters.
Check the actual content against the user's goals, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the entire page; for time-based media, inspect the start, end, and key segments. For abnormal results, first check the current project to avoid repeatedly performing irreversible operations.
Delivery
Return the editable project, actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently reworks it, read this session's source project and make local modifications, preserving the content that has already been accepted.