Skill This
AI Skill Report Card

Looping Region

C+61·Sep 15, 2026·Source: Web

Looping Region

Automates a specific Logic Pro arrangement-building workflow: duplicating a block of regions across tracks, creating variation through staged muting, applying sidechain compression, setting output levels, adding a sub-bass layer, and archiving the finished project.

Quick Start12 / 15

When the user says "loop region":

  1. List recently opened Logic Pro session files.
  2. Ask: "Which session would you like to open and loop regions on?"
  3. Wait for the user to pick a session before doing anything else.
  4. Once confirmed, execute the full Workflow below on that session.

Do not skip the session-selection question — it is required every time, even if only one recent session exists.

Recommendation▾
This skill is extremely hyper-specific to one user's exact session structure (fixed track names AA-FF, fixed bar numbers, fixed dB levels) — it's more of a personal macro than a generalizable skill; consider parameterizing track names, bar ranges, and levels so it works for other arrangements.
Workflow15 / 15

Track names referenced throughout: AA, BB, CC, DD, EE, FF.

Progress:

  • Step 0: Ask user which recent session to open; confirm selection
  • Step 1: Copy regions AA/BB/CC/DD/EE/FF from bar 1–192 (extend arrangement)
  • Step 2: Set PLUCK region range to bars 17–192
  • Step 3: Apply first mute pass
  • Step 4: Apply second mute pass
  • Step 5: Add sidechain compressor on BB, configure attack/release
  • Step 6: Set Stereo Out to -6 dB
  • Step 7: Set per-track output levels (AA, BB, CC, DD, EE)
  • Step 8: Build Sub-Bass layer with ES2/ES M
  • Step 9: Save/export copy to 0001 FORMAT SCRIPTS folder, labeled FORMAT SCRIPTS
  • Step 10: Report completion to user

Step 1 — Copy Base Regions

Duplicate each of AA, BB, CC, DD, EE, FF spanning bar 1 to bar 192 (i.e., extend/repeat the existing 1–192 content so the full timeline is populated).

Step 2 — PLUCK Region

Set/trim the PLUCK region to span bars 17–192.

Step 3 — Mute Pass 1

Mute the following ranges on each track:

TrackMuted Bars
AA65–96
BB1–48
CC41–48
DD81–96
EE81–96
FF81–96

Step 4 — Mute Pass 2

Mute the following additional ranges:

TrackMuted Bars
AA145–192
BB97–144
CC141–144
DD161–192
EE161–192
FF161–192

Step 5 — BB Sidechain Compression

On the BB track:

  1. Insert Logic's stock Compressor plugin.
  2. Open the plugin window, go to the top-right sidechain section.
  3. Set Sidechain Input to the Kick drum track.
  4. Set a fast attack and quick release so the kick punches through the sub/BB content.

Step 6 — Stereo Out

Set the Stereo Out channel output level to -6 dB.

Step 7 — Output Channel Levels

Set each track's output fader to:

TrackLevel
AA-12 dB
BB-4 dB
CC-12 dB
DD-12 dB
EE-12 dB

Step 8 — Sub-Bass Layer

Create a new instrument track using ES2 or ES M:

  1. Select a clean sine wave patch/oscillator.
  2. Pull the filter cutoff down for a pure sub tone.
  3. Program a simple groove that follows the root note of the track's existing progression.

Step 9 — Archive Finished Project

  1. Save a copy of the finished project.
  2. Place it in the folder 0001 FORMAT SCRIPTS.
  3. Label the saved copy FORMAT SCRIPTS.

Step 10 — Notify Completion

Tell the user explicitly: "Loop region process complete — [session name] has been looped, muted, mixed, and archived to 0001 FORMAT SCRIPTS."

Recommendation▾
Examples are still fairly abstract/scripted dialogue rather than showing real tool-call sequences or Logic Pro scripting commands (AppleScript/MIDI automation) that would actually be executed — add a concrete example of the actual automation code or API calls used to manipulate Logic Pro.
Examples10 / 20

Example 1: Input: User says "loop region" Output: Agent lists recent sessions ("Track_Idea_04.logicx, Beat_Session_12.logicx, Vocal_Mix_Final.logicx — which would you like to open and loop regions on?"), waits for reply, then runs full Workflow on the chosen session, ending with "Loop region process complete — Beat_Session_12 has been looped, muted, mixed, and archived to 0001 FORMAT SCRIPTS."

Example 2: Input: User says "loop region" but names a session not in the recent list Output: Agent attempts to open the named session directly; if not found, asks user to confirm the correct file path before proceeding.

Recommendation▾
No mention of how the automation is technically achieved (AppleScript, Logic Pro Scripter, MIDI FX, OSC, etc.) — without this, the skill reads as a manual instruction checklist for a human engineer rather than an actionable skill Claude can execute.
Best Practices
  • Always confirm the target session before making any edits — never assume.
  • Perform mute passes in order (Pass 1 then Pass 2) so bar ranges don't get overwritten incorrectly.
  • Double-check output fader values match exactly (AA/CC/DD/EE = -12, BB = -4, Stereo Out = -6).
  • Verify the sidechain source is actually a Kick drum track before assigning it — ask the user if ambiguous (multiple kick-named tracks).
  • Keep the sub-bass groove simple and root-note-locked; avoid adding melodic movement that competes with the main bass.
  • Confirm the 0001 FORMAT SCRIPTS folder exists before saving; create it if missing.
Common Pitfalls
  • Don't skip asking which session to open, even if there's only one recent file.
  • Don't mute Pass 2 ranges before Pass 1 is fully applied — order matters for tracks with overlapping logic (e.g., CC 41-48 vs 141-144).
  • Don't confuse track output fader level with plugin gain — these are channel strip output settings.
  • Don't forget the sidechain compressor is specifically on BB, not on the kick track itself.
  • Don't save over the original session file — the archive step requires a copy in the designated folder.
  • Don't leave the completion message implicit — explicitly tell the user when done.
0
Grade C+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
12/15
Workflow
15/15
Examples
10/20
Completeness
10/20
Format
12/15
Conciseness
12/15
Save to My Skills