updating "core" skills

I got my clawd to improve the following things from these skills:

1. skills/gog/SKILL.md โ€” Major documentation expansion

What: Complete rewrite from a brief reference to comprehensive usage guide.

Why: Makes the gog CLI actually usable without external docs:
- Added proper markdown structure (headers, code blocks)
- Expanded command examples for all services (Gmail, Calendar, Drive, Docs, Sheets, Contacts)
- Added Slides to the supported services
- New Email Backup section with bash scripts for downloading emails as Markdown + attachments (single + bulk with subagent parallelism)
- New Direct API Access section showing how to use gog's OAuth tokens for operations gog doesn't support (like in-place Google Doc editing)
- Practical tips section

2. skills/notion/SKILL.md โ€” Security improvement

What: Changed API key storage from plaintext file to macOS Keychain.

Why: Storing secrets in ~/.config/notion/apikey is insecure. Now uses:
# Store
security add-generic-password -a "$USER" -s "notion-api-key" -w "ntn
..."
# Retrieve
security find-generic-password -a "$USER" -s "notion-api-key" -w

3. skills/oracle/SKILL.md โ€” Troubleshooting + cookie fixes

What: Added --browser-cookie-path flag example and extensive troubleshooting section.

Why: Browser mode cookie loading is brittle. New docs cover:
- Node.js < 24.4 BigInt overflow bug (breaks cookie expiry parsing)
- macOS Keychain authorization prompts timing out
- Wrong Chrome profile paths (Cookies vs Network/Cookies)
- Inline cookies fallback (ORACLE_BROWSER_COOKIES_JSON)
- Debug command with ORACLE_DEBUG_COOKIES=1



however, since they are "defined" in the clawdbot github project, it now acts as changes waiting to be comitted. How is this supposed to be managed?
Was this page helpful?