Before executing specific methods, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Task starting point
First read the source material and confirm the delivery purpose, target dimensions or duration, modification scope, and required format. Directly adopt reasonable defaults for details that can be determined from the task and source material; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off 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
- Mark the segments to keep and the segments to delete, and determine cut points by semantics or beat.
- Cut in low-energy regions where possible, and add appropriate crossfades at the seams.
- Organize the spacing and start/end times of the clips, and preserve tail sounds.
- Listen through the entire process and check the total duration.
Tool implementation
Use open_session/new_session to manage sessions; import_audio to import, inspect_session to check, and consult live tools for other edits; save_session to save the project, and bounce_mix to output audio.
First read the actual tool schema, then fill in the parameters; use the returned values for object or document IDs. The queried commands must be available on the current backend. Before saving, choose a new output path and preserve the input. When a required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as a substitute.
Result checking
- No clicks, repeated words, or truncated tail sounds.
- The clip order and content match the original intent.
- The output duration and sample rate meet the requirements.
Check the actual content against the user's goal, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the whole page; for time-based media, inspect the start/end and key segments. For abnormal results, first check the current project to avoid repeating irreversible operations.
Delivery
Return the editable project, the 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 the source project from this session and modify it locally, preserving the accepted content.