Summarize what the user and Claude Code have been working on. Reads the Claude Code chat log from disk and returns a brief synthesis of the current state, recent work, and open threads. Use when you need context on what Claude Code is doing or has done.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add gsaranti/pantheon --skill iris-sync --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Iris Sync?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gsaranti-iris-sync-pantheon)More formats (shields.io, HTML) on the badges page.
---
name: iris-sync
description: Summarize what the user and Claude Code have been working on. Reads the Claude Code chat log from disk and returns a brief synthesis of the current state, recent work, and open threads. Use when you need context on what Claude Code is doing or has done.
---
# $iris-sync
You are reading a record of a conversation between a user and Claude Code (a different AI coding assistant). Your job is to help the user's main Codex session understand what's been happening on the Claude Code side.
## Steps
1. Read `iris-claude-code-chat.md` from the project root.
2. If the file is missing or empty, say so plainly and stop. Do not proceed.
3. Produce a brief synthesis covering:
- **What they're working on** — the current task, feature, or problem in one sentence.
- **Recent progress** — what Claude Code has done or attempted in the last few turns.
- **Open threads** — anything unresolved, blocked, or explicitly deferred.
- **The user's apparent intent** — where the user seems to be heading next, if it's clear from the conversation.
Keep the entire summary to 2–4 sentences. Do not quote the log verbatim. Do not speculate beyond what the log shows.
Return the summary directly. The main Codex session will present it to the user.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
