PTENES
MODULE 2.2 · TIER A

🥈 Almost at the top

Honorable mentions — Tier A features that almost made the Top 12. From Google Workspace piloted from the terminal to planning modes, hooks, effort levels, and the visibility layer that keeps everything under control.

6
Topics
45
Minutes
Interm.
Level
Practice
Type

Detailed content

1
A TIER · HONORABLE MENTION NO. 1

🗂️ Google Workspace CLI

Imagine running Gmail, Drive, Docs, Sheets, and Calendar from the terminal — and, on top of that, build your own skills. That's exactly what the Google Workspace CLI lets you do. Technically, it's not an official Claude "feature," but it's so useful that it makes the list as honorable mention #1: living proof that Claude can drive any CLI.

Claude in the terminal Workspace CLI + your skills Gmail · Drive Docs · Sheets Calendar any CLI …

🧩 Why it makes the list

It's not just "sending email with a command." It's a demonstration of a broader principle:

  • •If something has a CLI, Claude can operate it.
  • •You can wrap repeated office workflows in skills.
  • •Your entire Workspace becomes conversational automation.
Through the terminal

Gmail, Drive, Docs…

Surrounding skills

Wrap your workflows.

Any CLI

The principle it proves.

Honorable mention #1

Unofficial, but top-notch.

2
A TIER · WHERE YOU ARE

📨 Dispatch & Channels

Two ways to talk to Claude from where you already are. Dispatch: you start the task on your phone and Claude runs on your desktop, sending you the result. Channels: connects Telegram, Discord, or iMessage to a live session — and it works in both directions.

1

Dispatch from your phone

You send the task from your phone; Claude runs it on your desktop, with the full power of the machine.

2

Gets the result back

Great for continuing a conversation from your phone: you send it off, leave, and your desktop replies when it’s done.

3

Channels: live chat

Connect Telegram, Discord, or iMessage to a live session—you send and receive messages through the app you already use.

💡 Practical tip

Use Dispatch when the task is heavy and you don’t want to sit around waiting; use Channels when you want to chat live from inside an app that’s already open.

Dispatch

Mobile → desktop.

Result

Come back to you.

Channels

Telegram, Discord, iMessage.

Two directions

Sends and receives in real time.

3
A TIER · BASICS & CREATION

🖼️ Claude Desktop App & Claude Design

O Desktop App is the foundation on Mac/Windows for chat, Cowork, connectors, and managing local and cloud routines in one place—and it’s still better for copying and pasting text without the terminal’s weird wrapping. The Claude Design: you describe what you want, and it puts together polished designs, slides, and one-pagers.

✓ Desktop App

  • ✓Chat, Cowork, and connectors in one place.
  • ✓Manages local and cloud routines side by side.
  • ✓Copy and paste text without the terminal’s weird line wrapping.

✓ Claude Design

  • ✓Describe it, and it creates polished designs and one-pagers.
  • ✓Great for teams: comment and view design systems.
  • ✓Generates PPTs fast, without building slides one by one.

💡 Practical tip

Keep the Desktop App as the hub for your routines and use the Design whenever you need to deliver something presentable for others to view or comment on.

Local base

Mac/Windows, all together.

Routines

Local and cloud in one place.

Design

Slides and one-pagers.

For teams

Commentary and quick PPTs.

4
A TIER · CONTROL

🗺️ Plan Mode & Auto Mode

Two modes that change how Claude acts. Plan Mode: it researches and proposes a plan before touching anything. Auto Mode: approves safe actions and blocks risky ones without asking — in practice, an excellent permission level.

✓ When to use Plan/Auto

  • ✓Plan: a large or ambiguous task that deserves a plan first.
  • ✓Auto: long-running work where approving everything gets tiring.
  • ✓Auto lets safe actions through and holds back risky ones.

✗ Misunderstandings

  • ✗Thinking Auto Mode approves everything blindly — it blocks risky actions.
  • ✗Skip Plan Mode on tasks where rework is costly.
  • ✗Confusing “planning” with “execution” — Plan only proposes.

💡 Practical tip

Combine the two: start in Plan Mode to align on the approach and, once the plan is approved, let the Auto Mode keep the work moving without interrupting you at every safe step.

Plan Mode

Plan before acting.

Auto Mode

Approves only what's safe.

Blocks risk

Without asking needlessly.

Permission

Auto is a level.

5
A TIER · AUTOMATION & DEPTH

⚙️ Hooks, Effort Levels & Ultracode

Three fine-tuned levers. Hooks run their own commands automatically during session events. Effort Levels adjusts reasoning depth from low to maximum (/effort). E Ultracode is the maximum effort tier—full-throttle reasoning plus automatic multi-agent workflows.

Example events · effort · maximum
# Hooks: rode um comando seu em eventos da sessão
on: PostToolUse  →  rodar lint/format automaticamente

/effort high       # do baixo ao máximo
Ultracode          # talo + multi-agente automático

✓ Good use

  • ✓A hook that formats/lints after each edit.
  • ✓Increase the effort for difficult tasks and lower it for trivial ones.
  • ✓Ultracode for the toughest problems.

✗ What to avoid

  • ✗Keep everything at maximum effort (wastes resources unnecessarily).
  • ✗Hooks that run slow commands on every event.
  • ✗Forgetting that low effort is enough for simple tasks.
Hooks

Commands on events.

/effort

From low to maximum.

Ultracode

Maximum effort.

Multi-agent

Fully automatic.

6
A TIER · SEE & SAVE

👁️ Visibility & savings

The layer that keeps everything under control. Agent View is the dashboard for all terminals/agents running in the background and their status; /btw asks a parallel question without interrupting the main task; and /context shows what's filling up the window. Together, they give you visibility and save tokens.

The visibility layer see · ask · save
Agent View · /btw · /context · /usage · Prompt Caching · /background

✓ See and ask

  • ✓Agent View: status of all background agents.
  • ✓/btw: ask a side question without interrupting the task.
  • ✓/background: sends the session to the background.

✓ Save

  • ✓/context: what’s filling the window.
  • ✓/usage: session tokens and cost.
  • ✓Prompt Caching: reuses repeated context and saves a lot of tokens.

💡 Practical tip

O Prompt Caching runs in the background: you don’t need to configure anything to save tokens. Combine /context e /usage to see where the tokens are going.

Agent View

Agents dashboard.

/btw · /context

Question and window.

/usage

Tokens and cost.

Prompt Caching

Saves in the background.

🏁 Module summary

✓
Google Workspace CLI — Gmail/Drive/Docs/Sheets/Calendar through the terminal; proof that Claude can drive any CLI.
✓
Dispatch & Channels — phone → desktop and live chat via Telegram/Discord/iMessage.
✓
Desktop App & Design — local foundation for everything and polished design/slide generation.
✓
Plan & Auto Mode — plans before acting and approves safe actions without asking.
✓
Hooks, Effort & Ultracode — event-based automation, adjustable depth, and maximum effort.
✓
Visibility & savings — Agent View, /btw, /context, /usage, Prompt Caching, and /background.

You completed Track 2 🎉

You know Tiers B and A — the useful tier and the near-top tier. Now move up to the star tier: the Top 12, from #12 to #1.