begin-session

Load client, project, and initiative context into concise operational briefings.

Updated May 7, 2026
One-click install
npx skills add https://github.com/BeltDoor/aios-template --skill begin-session-beltdoor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: begin-session
Source: https://github.com/BeltDoor/aios-template/tree/main/.claude/skills/begin-session
Command: npx skills add https://github.com/BeltDoor/aios-template --skill begin-session-beltdoor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of starting work without the right client, project, or initiative context by gathering scattered information into a focused briefing.

Core Features & Use Cases

  • Topic Context Loading: Resolves named clients, projects, or initiatives and gathers relevant folder information, memory, and connected sources.
  • Briefing Synthesis: Produces concise CEO-style summaries of current status, activity, open threads, and next steps while avoiding unsupported details.
  • Use Case: When preparing for a client discussion, use this Skill to quickly understand recent updates, relationship state, and outstanding actions across connected systems.

Quick Start

Use the begin-session skill to load the latest context for Atlas Brewery and summarize where things stand.

Frequently Asked Questions about begin-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load client context and generate a project briefing before starting work?

Yes, connector-aware fallbacks allow the context loading process to retrieve information from connected business tools. If a primary connector fails, the system attempts alternative sources to ensure a comprehensive operational briefing.

What is the best way to summarize project status across connected business tools?

You need a named client, project, or initiative to resolve. The system requires access to your local folders, memory, and connected business tools to perform topic resolution and gather the necessary operational context.

Does this context loading approach work with local folders and memory?

The main limitation is that it avoids fabricating missing information. If topic resolution fails or connectors cannot retrieve data, the briefing synthesis will lack those details rather than inventing unsupported information.

Why does my project briefing lack recent updates from connected systems?

Your project briefing may lack recent updates due to connector-aware fallbacks failing to retrieve data. The system does not fabricate missing information, so if connected business tools are inaccessible, those updates will be absent from the summary.