home / skills / yousufjoyian / claude-skills / workclaw

workclaw skill

safe

This skill exports the active terminal discussion to Google Drive and updates the Visual tab with completion status, improving workflow efficiency.

npx playbooks add skill yousufjoyian/claude-skills --skill workclaw

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

833 B

---
name: workclaw
description: Work-only shortcut skill for exporting current terminal discussion to Google Drive and showing completion in the terminal Visual tab. Use when the user says "workclaw".
---

# WorkClaw

Run a work-only export of the active terminal discussion and post completion status into the Visual tab.

## Command

```bash
python3 /home/yousuf/local_workspaces/skills/terminal-discussion-export/scripts/export_terminal_discussion.py \
  --terminal-id "$TC_TERMINAL_ID" \
  --lines 1800 \
  --a2ui on
```

## Result

- Markdown export is saved to Drive.
- Visual tab receives an A2UI completion card.
- Command output JSON should include:
  - `success: true`
  - `a2uiUpdated: true`

## Rules

- Treat this as **work-only**.
- If `a2uiUpdated` is false, rerun with explicit `--a2ui-log` path and confirm success.

Overview

This skill exports the active terminal discussion to Google Drive and reports completion to the terminal Visual tab. It is designed as a work-only shortcut triggered when the user says "workclaw," producing a Drive markdown file and an A2UI completion card in the Visual tab.

How this skill works

The skill runs a Python export script with the current terminal ID, a configurable line limit, and A2UI reporting enabled. On success it saves a markdown file to Google Drive and posts an A2UI completion card to the Visual tab; the command returns JSON with success and a2uiUpdated flags. If A2UI reporting fails, the script can be rerun with an explicit log path to confirm completion.

When to use it

When you want a saved markdown copy of the current terminal discussion in Google Drive.
When you need a visible completion card in the Visual tab summarizing the export.
When working in a controlled work-only context and you need an auditable export.
When you want an automated, repeatable export that returns JSON status flags.

Best practices

Invoke the skill only in work-only contexts to respect policy rules.
Verify the returned JSON contains success: true and a2uiUpdated: true.
If a2uiUpdated is false, rerun with an explicit --a2ui-log path and check the log.
Adjust the --lines argument to capture the desired amount of discussion history.

Example use cases

Save a long debugging session as markdown to Drive for later review or sharing.
Generate an export at the end of a work shift so teammates can see completed work in the Visual tab.
Automate periodic exports of active terminal discussions for audit or documentation.
Quickly produce a Drive-hosted summary when handing off work between engineers.

FAQ

What indicates a successful export?

The command outputs JSON with success: true and a2uiUpdated: true, the markdown is saved to Drive, and an A2UI completion card appears in the Visual tab.

What should I do if the Visual tab card isn't posted?

Rerun the export with an explicit --a2ui-log path to capture A2UI events, then confirm the log shows successful posting and that a2uiUpdated becomes true.