danielmiessler
Extract system improvements from content AND monitor external sources (Anthropic ecosystem, YouTube). USE WHEN upgrade, improve system, system upgrade, analyze for improvements, check Anthropic, Anthropic changes, new Claude features, check YouTube, new videos. SkillSearch('upgrade') for docs.
bunx add-skill danielmiessler/personal_ai_infrastructure -s PAIUpgradeLoadingβ¦
Before executing, check for user customizations at:
~/.claude/skills/CORE/USER/SKILLCUSTOMIZATIONS/PAIUpgrade/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
You MUST send this notification BEFORE doing anything else when this skill is invoked.
Send voice notification:
curl -s -X POST http://localhost:8888/notify \
-H "Content-Type: application/json" \
-d '{"message": "Running the WORKFLOWNAME workflow in the PAIUpgrade skill to ACTION"}' \
> /dev/null 2>&1 &
Output text notification:
Running the **WorkflowName** workflow in the **PAIUpgrade** skill to ACTION...
This is not optional. Execute this curl command immediately upon skill invocation.
Primary Purpose: Generate prioritized upgrade recommendations for the user's existing PAI setup by understanding their context and discovering what's new in the ecosystem.
The skill runs that converge into personalized recommendations:
Thread 1: USER CONTEXT Thread 2: SOURCE COLLECTION
βββββββββββββββββββββββ βββββββββββββββββββββββ
β TELOS Analysis β β Anthropic Sources β
β Project Analysis β β YouTube Channels β
β Recent Work History β β Custom USER Sources β
β PAI System State β β Community Updates β
βββββββββββββββββββββββ βββββββββββββββββββββββ
β β
ββββββββββββ¬ββββββββββββββββββββ
βΌ
βββββββββββββββββββββββββββββββ
β PRIORITIZED RECOMMENDATIONS β
β (personalized to user) β
βββββββββββββββββββββββββββββββ
| Workflow | Trigger | File |
|---|---|---|
| Upgrade | "check for upgrades", "check sources", "any updates", "check Anthropic", "check YouTube", "upgrade", "pai upgrade" | Workflows/Upgrade.md |
| ResearchUpgrade | "research this upgrade", "deep dive on [feature]", "further research" | Workflows/ResearchUpgrade.md |
Default workflow: If user says "upgrade" or "check for upgrades" without specifics, run the Upgrade workflow.
Granular. Extracted. PAI-Contextualized.
The output provides SPECIFIC TECHNIQUES extracted from actual content, not links to watch or recommendations to read. Every tip explains WHY it matters for YOUR PAI system.
# PAI Upgrade Report
**Generated:** [timestamp]
**Sources Processed:** [N] release notes parsed | [N] videos transcribed | [N] docs analyzed
---
## π― Extracted Techniques
These are SPECIFIC techniques pulled from actual content. Each one maps to your PAI system.
### From Release Notes
#### [Feature/Change Name]
**Source:** GitHub claude-code v2.1.16, commit abc123
**What It Is (16-32 words):**
[Describe the technique itself - what it does, how it works, what capability it provides. Must be 16-32 words, concrete and specific.]
**How It Helps PAI (16-32 words):**
[Describe the specific benefit to our PAI system - which component improves, what gap it fills, what becomes possible. Must be 16-32 words.]
**The Technique:**
> [Exact code pattern, configuration, or approach - quoted or code-blocked]
**Applies To:** `hooks/SecurityValidator.hook.ts`, ISC verification
**Implementation:**
```typescript
// Before (what you have now)
[current pattern]
// After (with this technique)
[new pattern]
Source: R Amjad - "Video Title" @ 12:34
What It Is (16-32 words): [Describe the technique itself - what it does, how it works, what capability it provides. Must be 16-32 words, concrete and specific.]
How It Helps PAI (16-32 words): [Describe the specific benefit to our PAI system - which component improves, what gap it fills, what becomes possible. Must be 16-32 words.]
The Technique:
"[Exact quote or paraphrased technique from transcript]"
Applies To: Browser skill, delegation system Implementation: [Specific steps to apply this technique]
Source: Claude Docs - Tool Use section, updated 2026-01-20
What It Is (16-32 words): [Describe the technique itself - what it does, how it works, what capability it provides. Must be 16-32 words, concrete and specific.]
How It Helps PAI (16-32 words): [Describe the specific benefit to our PAI system - which component improves, what gap it fills, what becomes possible. Must be 16-32 words.]
The Technique:
[Exact documentation excerpt showing the capability]
Applies To: skills/CORE/SKILL.md, agent spawning
Implementation:
[Specific changes needed]
| # | Technique | Source | PAI Component | Impact |
|---|---|---|---|---|
| 1 | [technique name] | [source] | [component it affects] | [what changes] |
| 2 | [technique name] | [source] | [component it affects] | [what changes] |
| Content | Source | Why Skipped |
|---|---|---|
| [video/doc title] | [source] | [No extractable technique / Not relevant to PAI / Covers basics you already know] |
Release Notes Parsed:
Videos Transcribed:
Docs Analyzed:
---
## Extraction Rules
**CRITICAL: Extract, don't summarize. Techniques, not recommendations.**
1. **Every output item must be a TECHNIQUE** - A specific pattern, code snippet, configuration, or approach
2. **Quote or code-block the actual content** - Show exactly what was said/written
3. **Map to PAI components** - Every technique must connect to a specific file, skill, workflow, or system component
4. **Two mandatory description fields (16-32 words each):**
- **What It Is:** Describe the technique itself - what it does, how it works, what capability it provides
- **How It Helps PAI:** Describe the specific benefit - which component improves, what gap it fills, what becomes possible
5. **Provide implementation** - Show before/after code or specific steps
6. **Skip, don't dilute** - If content has no extractable technique, put it in Skipped Content with reason
**Anti-patterns to AVOID:**
- β "Check out this video for more"
- β "This release has improvements"
- β "Consider looking into this"
- β Vague summaries without specific techniques
- β Links without extracted content
**Source Type Labels:**
| Label | Meaning |
|-------|---------|
| `GitHub: claude-code vX.Y.Z` | Specific version release notes |
| `YouTube: Creator @ MM:SS` | Video with timestamp |
| `Docs: Section Name` | Documentation section |
| `Blog: Post Title` | Blog post |
---
## The Two-Thread Architecture
### Thread 1: User Context Analysis
**Purpose:** Deeply understand the user to personalize recommendations.
Launch **parallel agents** to analyze:
| Agent | Focus | Sources |
|-------|-------|---------|
| **TELOS Agent** | User's goals, challenges, current focus | `skills/CORE/USER/TELOS/*.md` |
| **Project Agent** | Active projects, tech stacks, dependencies | TELOS/PROJECTS.md, recent work context |
| **History Agent** | Recent work patterns, what's been done | `MEMORY/WORK/`, `MEMORY/STATE/current-work.json` |
| **PAI State Agent** | System capabilities, installed skills, gaps | `skills/`, `hooks/`, `settings.json` |
**Output:** A context object that includes:
- User's current focus areas and priorities
- Active projects and their tech stacks
- Recent work patterns and themes
- PAI system state and existing capabilities
### Thread 2: Source Collection
**Purpose:** Discover what's new in the ecosystem.
Launch **parallel agents** to check:
| Agent | Focus | Sources |
|-------|-------|---------|
| **Anthropic Agent** | Official Anthropic updates | `Tools/Anthropic.ts` (30+ sources) |
| **YouTube Agent** | Configured channels for new videos | USER customization channels |
| **Custom Source Agent** | Any USER-defined additional sources | USER/SKILLCUSTOMIZATIONS/PAIUpgrade/ |
**Output:** A collection of discoveries:
- New features, releases, changes from Anthropic
- New videos with transcripts and key insights
- Updates from custom sources
---
## Process Flow
### Step 1: Launch Both Threads in Parallel
Using BACKGROUNDDELEGATION, spawn both analysis threads simultaneously:
```markdown
## Thread 1: User Context (4 parallel agents)
### Agent 1: TELOS Analysis
Read and analyze:
- ~/.claude/skills/CORE/USER/TELOS/TELOS.md
- ~/.claude/skills/CORE/USER/TELOS/GOALS.md
- ~/.claude/skills/CORE/USER/TELOS/PROJECTS.md
- ~/.claude/skills/CORE/USER/TELOS/CHALLENGES.md
- ~/.claude/skills/CORE/USER/TELOS/STATUS.md
Extract: Current focus, priorities, active goals, project themes
### Agent 2: Recent Work Analysis
Read and analyze:
- ~/.claude/MEMORY/STATE/current-work.json
- Recent MEMORY/WORK/ directories
Extract: What user has been working on, patterns, open tasks
### Agent 3: PAI System State
Analyze:
- ~/.claude/skills/ (installed skills)
- ~/.claude/hooks/ (active hooks)
- ~/.claude/settings.json (configuration)
Extract: Current capabilities, potential gaps, system health
### Agent 4: Tech Stack Context
From PROJECTS and recent work, identify:
- Languages and frameworks in use
- Deployment targets
- Integration points
---
## Thread 2: Source Collection (3 parallel agents)
### Agent 1: Anthropic Sources
Run: bun ~/.claude/skills/PAIUpgrade/Tools/Anthropic.ts
Check all 30+ official sources for updates
### Agent 2: YouTube Channels
Check configured channels for new videos
Extract transcripts from new content
### Agent 3: Custom Sources
Check any USER-defined additional sources
Once both threads complete:
For each discovery that passes relevance filtering:
Generate the prioritized recommendations report (see format above).
Skill Files:
sources.json - Anthropic sources config (30+ sources)youtube-channels.json - Base YouTube channels (empty by default)State/last-check.json - Anthropic stateState/youtube-videos.json - YouTube stateUser Customizations (~/.claude/skills/CORE/USER/SKILLCUSTOMIZATIONS/PAIUpgrade/):
EXTEND.yaml - Extension manifestyoutube-channels.json - User's personal YouTube channels| Tool | Purpose |
|---|---|
Tools/Anthropic.ts | Check Anthropic sources for updates |
Example 1: Standard upgrade check
User: "check for upgrades"
β Launch Thread 1 (4 agents analyzing user context)
β Launch Thread 2 (3 agents checking sources)
β Wait for both threads
β Synthesize into prioritized recommendations
β Output personalized upgrade report
Example 2: Quick Anthropic-only check
User: "check Anthropic only"
β Run Anthropic.ts tool directly
β Use cached user context from recent session
β Quick-match against user focus areas
β Output filtered recommendations
These output patterns are FAILURES. If you produce these, you have not completed the skill correctly:
| β Bad Output | Why It's Wrong | β Correct Output |
|---|---|---|
| "Check out R Amjad's video on Claude Code" | Points to content instead of extracting it | "@ 5:42, R Amjad shows this technique: [quote]" |
| "v2.1.16 has task management improvements" | Vague summary, no technique | "v2.1.16 adds addBlockedBy parameter: [code example]" |
| "Consider looking into MCP updates" | Recommendation without extraction | "MCP now supports [specific feature]: [docs quote]" |
| "This could be useful for your workflows" | Vague relevance | "This improves your Browser skill because [specific gap it fills]" |
| "Several videos covered AI agents" | Count without content | "[N] videos skipped - no extractable techniques" |
| "This helps because it improves things" | Vague benefit, no word count | "How It Helps PAI (16-32 words): Our SecurityValidator currently only blocks commands. This technique enables injecting reasoning context before tool execution, making security decisions more nuanced." |
| "A new hook feature" | No description of what it IS | "What It Is (16-32 words): PreToolUse hooks can return additionalContext that gets injected into the model's context before execution, enabling reasoning-based decisions rather than binary blocks." |
The test: If you can say "show me the technique" and there's nothing to show, you've failed.
Word count test: Each "What It Is" and "How It Helps PAI" field MUST be 16-32 words. Count them. If under 16, add specificity. If over 32, condense.
This skill embodies PAI's commitment to continuous, personalized improvement - understanding YOU first, then discovering what's new, then EXTRACTING the actual techniques that matter to your system.
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.