Opus 4.7 workflow tips: permissions, session controls and a custom /go skill

Understand permission changes before using them

The 17 April 2026 description reviews six Claude Code tips and corrects misleading names or availability claims. Its first topics are Auto Mode and reducing repeat permission prompts. It specifically discusses using Auto Mode without --dangerously-skip-permissions. These are different permission approaches, not interchangeable spellings of the same setting.

1. Follow Auto Mode at 0:45 and the permission-prompt explanation at 1:50.
2. Check the intended project and allowed actions before changing a session’s permission behaviour.
3. Keep the historical Max-plan reference attached to the recording; verify present availability before planning your own workflow around it.

Use session controls for specific problems

The description names /recap for keeping track of long work, /focus for hiding intermediate material and /effort for adjusting effort from low to max. These controls address orientation, presentation and reasoning effort respectively. A cleaner display does not establish that an implementation has been tested or that a long task has finished.

1. Follow /recap at 2:43 and compare the recap with the current task and unresolved checks.
2. Use the /focus segment at 3:18 to understand which intermediate information is hidden.
3. Review /effort at 3:57 and choose effort for the actual task, keeping the required result and validation explicit.

Install the custom skill as a separate resource

At 4:35 Luke explains that the advertised /go skill does not exist as claimed and provides his own version. Its sequence is end-to-end verification, simplification and a PR. The description points to community resources rather than reproducing the full skill text: https://www.skool.com/luke and https://www.skool.com/ai-automation-hub-5735.

1. Follow the free-skill segment at 5:17 and the Arc + ClawHub installation segment at 5:48.
2. Read the skill’s actual instructions before applying it to a repository and identify the expected checks and proposed PR change.
3. Inspect the end-to-end result and simplification diff before treating the PR as a completed, reviewed deliverable.

The takeaway

Use the controls to manage work, and use explicit verification to judge it; a custom skill name is not evidence of built-in capability.