PAIUpgrade
Customization
Before executing, check for user customizations at:
~/.claude/PAI/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.
🚨 MANDATORY: Voice Notification (REQUIRED BEFORE ANY ACTION)
You MUST send this notification BEFORE doing anything else when this skill is invoked.
- Send voice notification:
curl -s -X POST http://localhost:31337/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...
PAIUpgrade
Primary Purpose: Generate prioritized upgrade recommendations for PAI by understanding the user's context and discovering what's new in the ecosystem.
The skill runs four parallel agent threads that converge into personalized recommendations:
- Thread 0 — Prior-Work Audit (Algorithm, PATTERNS.yaml, hooks, skills, recent ISAs, KNOWLEDGE, feedback memory)
- Thread 1 — User Context (TELOS, projects, recent work, PAI state)
- Thread 2 — Source Collection (Anthropic, YouTube, custom sources, GitHub trending)
- Thread 3 — Internal Reflections (algorithm-reflections.jsonl)
Thread 0 is the guard rail against recommending what's already implemented, already researched-and-deferred, or already decided against. Synthesis MUST filter every candidate recommendation through Thread 0's state inventory — never emit a recommendation without a Prior Status assignment.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| Upgrade | "check for upgrades", "check sources", "any updates", "check Anthropic", "check YouTube", "upgrade", "pai upgrade" | Workflows/Upgrade.md |
| MineReflections | "mine reflections", "check reflections", "what have we learned", "internal improvements", "reflection insights" | Workflows/MineReflections.md |
| AlgorithmUpgrade | "algorithm upgrade", "upgrade algorithm", "improve the algorithm", "algorithm improvements", "fix the algorithm" | Workflows/AlgorithmUpgrade.md |
| ResearchUpgrade | "research this upgrade", "deep dive on [feature]", "further research" | Workflows/ResearchUpgrade.md |
| FindSources | "find upgrade sources", "find new sources", "discover channels" | Workflows/FindSources.md |
| TwitterBookmarks | "check bookmarks", "scan bookmarks", "twitter bookmarks", "X bookmarks", "bookmarks for upgrades", "what have I bookmarked" | Workflows/TwitterBookmarks.md |
Default workflow: If user says "upgrade" or "check for upgrades" without specifics, run the Upgrade workflow (which includes Thread 3 reflection mining).
Output Format
Canonical spec: References/OutputFormat.md — single source of truth for section order, Prior Status legend, table columns, and hard rules. Both this skill and Workflows/Upgrade.md reference that file rather than inlining their own copies.
Section order: Discoveries → Recommendations → Technique Details → Internal Reflections → Summary → Skipped → Sources Processed.
Print only non-empty Recommendation tiers (no empty 🟡 MEDIUM headers).
Extraction Rules
Extract, don't summarize. Techniques, not recommendations. Verify prior state before recommending.
- Every output item is a TECHNIQUE — a specific pattern, code snippet, configuration, or approach.
- Quote or code-block the actual content — show exactly what was said/written.
- Map to PAI components — every technique connects to a specific file, skill, workflow, or system component.
- Verify Prior State (Thread 0 gate) — Before emitting ANY recommendation, confirm against Thread 0 inventory: is it already in Algorithm / PATTERNS.yaml / hooks / SKILL files / KNOWLEDGE / prior ISAs? Assign a Prior Status emoji and cite evidence. Items that are ✅ DONE go to Skipped, not Recommendations.
- Two mandatory description fields, ≤2 sentences each, concrete and specific:
- What It Is: the technique itself — what it does, how it works, what capability it provides
- How It Helps PAI: the specific benefit — which component improves, what gap it fills
- Provide implementation — show before/after code or specific steps.
- Skip, don't dilute — if content has no extractable technique, put it in Skipped Content with reason.
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 |
Configuration
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 stateState/github-trending.json— GitHub trending state (seen repos)State/twitter-bookmarks-seen.json— Previously processed bookmark URLs
User Customizations (~/.claude/PAI/USER/SKILLCUSTOMIZATIONS/PAIUpgrade/):
EXTEND.yaml— Extension manifestyoutube-channels.json— User's personal YouTube channelsuser-sources.json— Additional source definitions (e.g.,github_trendingblock)
Tool Reference
| Tool | Purpose |
|---|---|
Tools/Anthropic.ts |
Check 30+ Anthropic sources (blogs, GitHub repos, changelogs, docs) for updates |
Key Principles
- Extract, Don't Summarize — pull specific techniques, never just link to sources.
- Quote the Source — actual code, doc quotes, or transcript excerpts.
- PAI-Contextualized — every technique maps to a specific PAI file, skill, or component.
- Explain "Why You" — "this helps because your [X] currently [Y]".
- TELOS-Connected — reference user's goals and challenges when explaining relevance.
- Skip Boldly — if content has no extractable technique, skip it entirely.
- Implementation-Ready — provide actual code changes, not vague recommendations.
- Claude Code Freshness via claude-code-guide — when discoveries involve Claude Code internals (hooks, settings, slash commands, MCP, agent types, keybindings, Agent SDK, Claude API), spawn
Agent(subagent_type="claude-code-guide")to verify PAI's current references match the latest API surface.
Anti-Patterns (What NOT to Output)
These output patterns are FAILURES:
| ❌ 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 | "How It Helps PAI: SecurityValidator currently only blocks commands. additionalContext enables reasoning context before tool execution, making decisions more nuanced." |
| "A new hook feature" | No description of what it IS | "What It Is: PreToolUse hooks can return additionalContext that gets injected into the model's context before execution, enabling reasoning-based decisions rather than binary blocks." |
| "Top 3 Actions" or flat recommendation list | No priority tiers | Recommendations section with 🔴/🟠/🟡/🟢 tiers, each with PAI Relevance column |
| Recommendations at the bottom | Actionable items buried after technique dump | 🔥 Recommendations section appears SECOND, technique details third |
| Recommending something already implemented | Wastes user trust | Move to Skipped with file:line evidence |
| Re-surfacing rejected ideas without new context | Drift from prior decisions | Only re-recommend if reason has changed; say what changed |
| Missing Prior Status column | Bypasses Thread 0 gate | Every recommendation row cites evidence from Thread 0's inventory |
The test: if you can say "show me the technique" and there's nothing to show, you've failed.
Workflows
- Upgrade.md — primary workflow; full four-thread analysis with prioritized recommendations
- MineReflections.md — Thread 3 standalone (deep reflection mining)
- AlgorithmUpgrade.md — Algorithm-version-bump-focused upgrade flow
- ResearchUpgrade.md — deep dive on a specific upgrade opportunity
- FindSources.md — discover and evaluate new sources to monitor
Gotchas
- Check ALL sources in parallel — Anthropic blog, changelog, YouTube channels, GitHub releases. Don't check sequentially.
- Upgrades must not break existing skills or workflows. Verify backward compatibility before applying.
- Full upgrade check can take 5-7 minutes. Use
run_in_background: truefor the outer agent.
Execution Log
After completing any workflow, append a single JSONL entry:
echo '{"ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","skill":"PAIUpgrade","workflow":"WORKFLOW_USED","input":"8_WORD_SUMMARY","status":"ok|error","duration_s":SECONDS}' >> ~/.claude/PAI/MEMORY/SKILLS/execution.jsonl
Replace WORKFLOW_USED with the workflow executed, 8_WORD_SUMMARY with a brief input description, and SECONDS with approximate wall-clock time. Log status: "error" if the workflow failed.
More from danielmiessler/personal_ai_infrastructure
osint
Structured OSINT investigations — people lookup, company intel, investment due diligence, entity/threat intel, domain recon, organization research using public sources with ethical authorization framework. USE WHEN OSINT, due diligence, background check, research person, company intel, investigate, company lookup, domain lookup, entity lookup, organization lookup, threat intel, discover OSINT sources.
259firstprinciples
Physics-based reasoning framework (Musk/Elon methodology) that deconstructs problems to irreducible fundamental truths rather than reasoning by analogy. Three-step structure: DECONSTRUCT (break to constituent parts and actual values), CHALLENGE (classify every element as hard constraint / soft constraint / unvalidated assumption — only physics is truly immutable), RECONSTRUCT (build optimal solution from fundamentals alone, ignoring inherited form). Outputs: constituent-parts breakdown, constraint classification table, and reconstructed solution with key insight. Three workflows: Deconstruct.md, Challenge.md, Reconstruct.md. Integrates with RedTeam (attack assumptions before deploying adversarial agents), Security (decompose threat model), Architecture (challenge design constraints), and Pentesters (decompose assumed security boundaries). Other skills invoke via: Challenge on all stated constraints → classify as hard/soft/assumption. Cross-domain synthesis: solutions from unrelated fields often apply once the fundamental truths are exposed. NOT FOR incident investigation and causal chains (use RootCauseAnalysis). NOT FOR structural feedback loops (use SystemsThinking). USE WHEN first principles, fundamental truths, challenge assumptions, is this a real constraint, rebuild from scratch, what are we actually paying for, what is this really made of, start over, physics first, question everything, reasoning by analogy, is this really necessary.
160documents
Read, write, convert, and analyze documents — routes to PDF, DOCX, XLSX, PPTX sub-skills for creation, editing, extraction, and format conversion. USE WHEN document, process file, create document, convert format, extract text, PDF, DOCX, XLSX, PPTX, Word, Excel, spreadsheet, PowerPoint, presentation, slides, consulting report, large PDF, merge PDF, fill form, tracked changes, redlining.
114council
Multi-agent collaborative debate that produces visible round-by-round transcripts with genuine intellectual friction. All council members are custom-composed via ComposeAgent (Agents skill) with domain expertise, unique voice, and personality tailored to the specific topic — never built-in generic types. ComposeAgent invoked as: bun run ~/.claude/skills/Agents/Tools/ComposeAgent.ts. Two workflows: DEBATE (3 rounds, full transcript + synthesis, parallel execution within rounds, 40-90 seconds total) and QUICK (1 round, fast perspective check). Context files: CouncilMembers.md (agent composition instructions), RoundStructure.md (three-round structure and timing), OutputFormat.md (transcript format templates). Agents are designed per debate topic to create real disagreement; 4-6 well-composed agents outperform 12 generic ones. Council is collaborative-adversarial (debate to find best path); for pure adversarial attack on an idea, use RedTeam instead. NOT FOR parallel task execution across agents (use Delegation skill). USE WHEN council, debate, multiple perspectives, weigh options, deliberate, get different views, multi-agent discussion, what would experts say, is there consensus, pros and cons from multiple angles.
112privateinvestigator
Ethical people-finding using 15 parallel research agents (45 search threads) across public records, social media, reverse lookups. Public data only, no pretexting. USE WHEN find person, locate, reconnect, people search, skip trace, reverse lookup, social media search, public records search, verify identity.
112redteam
Military-grade adversarial analysis that deploys 32 parallel expert agents (engineers, architects, pentesters, interns) to stress-test ideas, strategies, and plans — not systems or infrastructure. Two workflows: ParallelAnalysis (5-phase: decompose into 24 atomic claims → 32-agent parallel attack → synthesis → steelman → counter-argument, each 8 points) and AdversarialValidation (competing proposals synthesized into best solution). Context files: Philosophy.md (core principles, success criteria, agent types), Integration.md (how to combine with FirstPrinciples, Council, and other skills; output format). Targets arguments, not network vulnerabilities. Findings ranked by severity; goal is to strengthen, not destroy — weaknesses delivered with remediation paths. Collaborates with FirstPrinciples (decompose assumptions before attacking) and Council (Council debates to find paths; RedTeam attacks whatever survives). Also invoked internally by Ideate (TEST phase) and WorldThreatModel (horizon stress-testing). NOT FOR AI instruction set auditing (use BitterPillEngineering). NOT FOR network/system vulnerability testing (use a security assessment skill). USE WHEN red team, attack idea, counterarguments, critique, stress test, devil's advocate, find weaknesses, break this, poke holes, what could go wrong, strongest objection, adversarial validation, battle of bots.
112