Maintain project continuity across coding-agent sessions (Claude Code and any AGENTS.md-style harness) using a markdown session briefing that pairs with the project's agent context file (AGENTS.md, CLAUDE.md, GEMINI.md). Use when working in a local repo or project that spans multiple sessions, when the user asks to create or update a session briefing, status doc, or handoff note, when resuming prior work, or at the end of a session/context window to capture state for the next one. The briefing holds timestamped state — current status, decisions, next steps, open questions; the context file holds timeless operational reference. Briefings live in the session-briefings hub, one per project, with a pointer wired into each project's context file. For chat-based (claude.ai) projects that have no context file, use chat-session-briefing instead.
EnglishMaintain continuity across multi-session projects in a chat interface (claude.ai web or desktop) using a single structured markdown session briefing. Use this skill whenever the user is working on a project that spans multiple conversations, whenever they ask to create or update a session briefing, project status document, or context handoff note, or whenever they mention resuming work from a previous session. Also trigger when the user starts a new multi-step project and needs a system for tracking progress across sessions — even if they don't explicitly say "session briefing." If the user references prior sessions, version histories, or asks to "pick up where we left off," this skill applies. Covers both creating the first briefing for a new project and updating an existing one. For coding agents that run in a repo with a context file (AGENTS.md/CLAUDE.md) and git, use agent-session-briefing instead.
EnglishOne-time guided setup for agent-session-briefing — creates the briefings hub, scaffolds your first briefing, and wires the continuity pointer into this repo's context file. Run this before first use of agent-session-briefing, or when you want to add a project to the constellation. Walks you through hub location, single-vs-constellation, and the context file, then scaffolds it for you.
English
AGENT SKILLS ATLASIncludes Agent Session Briefing, Chat Session Briefing, and Setup Session Briefing.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Agent Session Briefing
Maintain project continuity across coding-agent sessions (Claude Code and any AGENTS.md-style harness) using a markdown session briefing that pairs with the project's agent context file (AGENTS.md, CLAUDE.md, GEMINI.md). Use when working in a local repo or project that spans multiple sessions, when the user asks to create or update a session briefing, status doc, or handoff note, when resuming prior work, or at the end of a session/context window to capture state for the next one. The briefing holds timestamped state — current status, decisions, next steps, open questions; the context file holds timeless operational reference. Briefings live in the session-briefings hub, one per project, with a pointer wired into each project's context file. For chat-based (claude.ai) projects that have no context file, use chat-session-briefing instead.
Chat Session Briefing
Maintain continuity across multi-session projects in a chat interface (claude.ai web or desktop) using a single structured markdown session briefing. Use this skill whenever the user is working on a project that spans multiple conversations, whenever they ask to create or update a session briefing, project status document, or context handoff note, or whenever they mention resuming work from a previous session. Also trigger when the user starts a new multi-step project and needs a system for tracking progress across sessions — even if they don't explicitly say "session briefing." If the user references prior sessions, version histories, or asks to "pick up where we left off," this skill applies. Covers both creating the first briefing for a new project and updating an existing one. For coding agents that run in a repo with a context file (AGENTS.md/CLAUDE.md) and git, use agent-session-briefing instead.
Setup Session Briefing
One-time guided setup for agent-session-briefing — creates the briefings hub, scaffolds your first briefing, and wires the continuity pointer into this repo's context file. Run this before first use of agent-session-briefing, or when you want to add a project to the constellation. Walks you through hub location, single-vs-constellation, and the context file, then scaffolds it for you.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Agent Session Briefing skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.