tap-in

Generates concise session-briefing.md summaries of Git Tagging Toolbox operations from tracked Git events and todo lists, highlighting incomplete items.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/justSteve/GasTownOperations --skill tap-in
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tap-in
Source: https://github.com/justSteve/GasTownOperations/tree/main/.claude/skills/tap-in
Command: npx skills add https://github.com/justSteve/GasTownOperations --skill tap-in

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a quick session initialization that orients operators by collecting recent activity and system state, surfacing open work and health issues so handoffs and ongoing work remain continuous and safe.

Core Features & Use Cases

  • Context collection: Read the most recent entries from DaysActivity.md and CurrentStatus.md to capture last activity, carried work, and continuity threads.
  • Health and continuity checks: Verify daily housekeeping, run GT doctor --fix via a tmux session, and capture recent console output to detect regressions or failures.
  • Structured briefings: Emit a concise session-briefing.md that highlights last activity, open work, current system state, and attention items for the incoming operator.

Quick Start

Run the tap-in skill to generate a concise session-briefing.md summarizing recent activity, open work, and system health.

Frequently Asked Questions about tap-in

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

FAQPage Schema
How do I generate a session briefing for daily operations handoffs?

To generate a session briefing, run the initialization process to read DaysActivity.md and CurrentStatus.md, execute local shell health checks, and output a concise session-briefing.md summarizing recent activity and open work.

What is a tmux-invoked health check for session initialization?

A tmux-invoked health check executes gt doctor --fix within a tmux session during initialization to detect regressions, capture recent console output, and verify system state before writing the final briefing.

How do I track continuity threads and open work from markdown activity logs?

Tracking continuity threads involves reading the most recent entries from DaysActivity.md and CurrentStatus.md to capture last activity, carried work, and attention items into a structured summary.

Does session initialization require specific local files to produce a briefing?

Session initialization requires DaysActivity.md and CurrentStatus.md to exist locally for context collection, plus access to local shell commands and tmux to execute health checks and write the output file.

Can I automate daily operations handoffs with a session-briefing markdown file?

Automating daily handoffs uses this initialization to collect recent activity and system state, surfacing open work and health issues so ongoing operations remain continuous and safe across operators.

Why does my operations briefing flag issues during session initialization?

The operations briefing flags issues because the initialization process runs local shell checks and a tmux-invoked gt doctor --fix, capturing console output to detect regressions or failures that require attention.