workclaw_skill

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.