AI Leverage
Installing the stack and sharing it with your team
Pour the four layers in order, get past Claude's security refusals, keep your personalizations through updates, and share everything through a private repo.
Prep for Week 4: AI, live Tuesday, October 27Coming soonThis lesson is not recorded yet. Ty films it next. It will appear here, with its video and the written walkthrough, the day it goes live.
What this lesson will cover
- Known limitation to state plainly: the Enterprise/Chrome account mismatch has no workaround
- The install stack as four layers poured in order: RTK/GSD, SifStack, API, skills
- The refusal decision tree: refusal, permissions, trusted-link phrase, model switch, manual upload
- Public repo (read-only tap) filling a private team reservoir
- Plan mode as a gate: plan, questions, approve, execute
- The library today: 74 QA'd agents in 9 divisions with 22 skills, one install command, plus the DataSift API
- Shoot note: present only the current shape (74 agents, 9 divisions, 22 skills, one install command, the DataSift API); the old 19-skill framing appears only as the manual way this used to take.
‹ Installing the skills library from the guide link, livePlan mode doctrine: the discipline that gates every build ›
We build this with you live in Week 4: AI, Tuesday, October 27, 1 to 4 PM ET. Add it to your calendar.
