Skip to content
Skills Library
Programming · Testing

e2e-session-test

/e2e-session-test

Use when smoke-testing cctop end to end — verifying a real coding-agent session is tracked and shows in the panel. Trigger on "smoke test sessions", "verify session tracking", "test the hook pipeline", "check cctop picks up a claude/codex/opencode/pi session", or "run the e2e test", even without the word "skill". Creates a real CLI agent session in a terminal, confirms cctop tracks it, opens the panel programmatically, and captures screenshot proof.

Repository
cctop ↗
Licence
MIT
Last repository change
13.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/cctop-sessions.sh, scripts/launch-cli-session.sh

What it does and when to use it

Use when smoke-testing cctop end to end — verifying a real coding-agent session is tracked and shows in the panel. Trigger on "smoke test sessions", "verify session tracking", "test the hook pipeline", "check cctop picks up a claude/codex/opencode/pi session", or "run the e2e test", even without the word "skill". Creates a real CLI agent session in a terminal, confirms cctop tracks it, opens the panel programmatically, and captures screenshot proof.

Triggers from the description

smoke test sessionsverify session trackingtest the hook pipelinecheck cctop picks up a claude/codex/opencode/pi sessionrun the e2e testskill
Original author description

Use when smoke-testing cctop end to end — verifying a real coding-agent session is tracked and shows in the panel. Trigger on "smoke test sessions", "verify session tracking", "test the hook pipeline", "check cctop picks up a claude/codex/opencode/pi session", or "run the e2e test", even without the word "skill". Creates a real CLI agent session in a terminal, confirms cctop tracks it, opens the panel programmatically, and captures screenshot proof.

How it works

  1. Capabilities, not tools
  2. Create the session with a CLI agent in a terminal
  3. Steps (run from the repo root)
  4. PASS
Original SKILL.md headings · 64 lines, 356 words
SKILL.md preview
---
name: e2e-session-test
description: >-
  Use when smoke-testing cctop end to end — verifying a real coding-agent session
  is tracked and shows in the panel. Trigger on "smoke test sessions", "verify
  session tracking", "test the hook pipeline", "check cctop picks up a
  claude/codex/opencode/pi session", or "run the e2e test", even without the word
  "skill". Creates a real CLI agent session in a terminal, confirms cctop tracks
  it, opens the panel programmatically, and captures screenshot proof.
---

# cctop end-to-end session test

Verify a real session flows all the way through:

```
agent in a terminal → cctop hooks → ~/.cctop/sessions/<pid>.json → panel card
```

A good smoke test after touching hooks, the session schema, or the panel.

## Capabilities, not tools

Harness-agnostic — it needs three generic capabilities. Use your environment's
equivalent; don't assume a specific tool:

- **run shell commands**
- **capture a screenshot** of the screen (or fall back to the `screencapture` CLI)
- **view an image** you captured

## Create the session with a CLI agent in a terminal

Drive a CLI agent (`claude` / `codex` / `opencode` / `pi`) in a terminal window —
it's a real session and one shell command starts it. Don't try to puppet a
*desktop* agent's GUI: if it's the app hosting you, screen capture hides its window
and you can't confirm input landed (see `references/troubleshooting.md`). Requires a
cctop build with the `cctop://` URL scheme (ships with this skill).

## Steps (run from the repo root)

```bash
# 1. Baseline — note the PIDs
.claude/skills/e2e-session-test/scripts/cctop-sessions.sh

# 2. Create a session — opens a terminal running the agent, waits for it to register
.claude/skills/e2e-session-test/scripts/launch-cli-session.sh claude ~/projects/cctop

# 3. Verify — a new PID entry with the right source (cc/codex/opencode/pi) appears
.claude/skills/e2e-session-test/scripts/cctop-sessions.sh

# 4. Summon the panel
open cctop://toggle
```

Then **capture a screenshot** and confirm the new session's card is in the panel
(right status, source, project). Run `open cctop://toggle` again to close it — a
clean closed/open pair if you want before/after proof. For a shareable record,
write a small HTML log embedding the screenshots.

Two details the launcher handles, because they otherwise make this fail silently: a
**login shell** (so the agent's `PATH`, e.g. `~/.local/bin`, resolves) and a
**trusted directory** (so the agent doesn't stall at a folder-trust prompt).
`open cctop://toggle` is used instead of a menu-bar click or hotkey because those
need extra OS permissions under automation.

## PASS

- New tracked session within ~5s, correct `source`.
- `open cctop://toggle` opens **and** closes the panel.
- A screenshot shows the card.

On failure, grab the relevant `~/.cctop/logs/<session>.log` entry and see
`references/troubleshooting.md`.
Files in this package (4)
  • SKILL.md 3 KB
  • references/troubleshooting.md 3 KB
  • scripts/cctop-sessions.sh 1 KB
  • scripts/launch-cli-session.sh 2 KB

Versions

The database has no other skills named e2e-session-test.

Database snapshot: 13.11.2026 · package version e1bd183ff536 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86cctop-restart
    Restart cctop for local development and testing. Use when the user asks to restart, relaunch, run, or prepare the cctop app locally; ensures the current cctop-hook is installed before the menubar app is relaunched and verified.
  • 100cctop
    Open the cctop dashboard in a right-hand pane beside this session. Use when the user types /cctop or asks to see the session dashboard, monitor, or "top" for Claude Code.
  • 100cctop-setup
    Use when cctop-hook command fails or is not found. Guides user to install the cctop menubar app.
  • 100cctop-insights
    Answer questions about the current Claude Code session's cost, tokens, context, cache behaviour, tools, subagents and cctop's recommendations by querying cctop. Use when the user asks why a session is expensive or slow, what is filling the context, whether they will hit a rate…
  • 84run-e2e
    When the bundled run skill resolves in this session, prefer it to launch the app for a quick look; this skill for evidenced verification flows. End-to-end live app verification. Check prerequisites, start the app, drive UI/API flows, and capture evidence (screenshots, responses,…
  • 100smoke-test
    Smoke testing patterns for verifying backend implementations end-to-end. Covers build verification, service health checks, authentication flows, test data setup, and HTTP endpoint validation. USE WHEN: user mentions "smoke test", "verify implementation", "test endpoints", "check…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.