← Back to Skills Marketplace
🔌

Session Scribe

by Kitsune · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ✓ Security Clean
155
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install session-scribe-openclaw
Description
Automatically summarize active OpenClaw session transcripts into daily memory files using a cheap LLM. Run as a system cron job — reads new transcript entrie...
Usage Guidance
This skill appears to do exactly what it claims: read OpenClaw transcripts, call an external LLM, and append bullet-point summaries to daily memory files. Important things to consider before installing: - Privacy/exfiltration risk: transcripts (including any secrets, tokens, PII) will be sent to the configured LLM provider. Only enable cron runs if you are comfortable with that. Use a separate low‑privilege API key with spend limits. - Test first: run the provided --dry-run option to see exactly what content would be sent and what would be written before enabling cron. - API key handling: the script supports OPENAI_API_KEY, ANTHROPIC_API_KEY, or an --api-key-file. The registry metadata only lists OPENAI_API_KEY — if you plan to use Anthropic or a file, set the appropriate environment or file. Store key files with restrictive permissions (chmod 600) as suggested. - npm install note: SKILL.md recommends npm install, but the included scribe.js appears to use only Node core modules and no package.json is present. Inspect the skill directory before running npm install to avoid pulling unexpected packages. - Scope review: when using --all-sessions or pointing agents dir at ~/.openclaw/agents, the script may read many transcripts. If you only want a single session, use --session-id or --auto-session to limit exposure. If these tradeoffs are acceptable (you accept sending transcripts to an external provider and take key-management precautions), the skill is coherent with its stated purpose.
Capability Assessment
Purpose & Capability
Name/description (summarize session transcripts into daily memory files) align with what the code does: reading ~/.openclaw sessions, extracting user/assistant turns, calling OpenAI/Anthropic APIs, and appending summaries to a memory directory. Required binary (node) is appropriate.
Instruction Scope
Instructions and the script operate on OpenClaw session directories and sessions.json as described. This is consistent with purpose but has broad read scope: in --all-sessions mode the script iterates agents and will consider many transcripts. The SKILL.md includes a clear privacy notice; you should ensure transcripts do not contain secrets before enabling cron runs.
Install Mechanism
This is instruction-only (no install spec). SKILL.md tells users to run npm install in the skill directory, but the included scribe.js uses only Node core modules (fs/path/https) and there is no package.json in the manifest — npm install appears unnecessary and may be misleading. No remote downloads or obscure install sources are present.
Credentials
Registry lists OPENAI_API_KEY as the required env var and primary credential, which is coherent but incomplete: the script also accepts ANTHROPIC_API_KEY and an --api-key-file. The script only needs an LLM API key (or key file); it does not request unrelated credentials. Ensure you use a low-privilege key and limit file permissions.
Persistence & Privilege
always is false and the skill does not modify other skills or system-wide settings. It writes its own .scribe-state.json (kept in the skill directory) and appends memory files to the configured memory directory; this is normal for its function.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install session-scribe-openclaw
  3. After installation, invoke the skill by name or use /session-scribe-openclaw
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Adds a privacy notice about sending transcripts to external LLM providers (OpenAI/Anthropic), including warnings about secrets/PII and recommendations for secure API key use. - Updates cron setup examples to recommend storing API keys in a protected file instead of inlining secrets in environment variables. - Documents support for `--api-key-file` and for scribing all sessions across all agents with `--agents-dir` and `--all-sessions`. - No functional changes to the skill logic itself.
v1.0.0
- Initial release of session-scribe: an automated tool to summarize OpenClaw session transcripts into daily memory files using OpenAI or Anthropic APIs. - Reads only new transcript entries since last run, skipping non-conversational content, and appends concise bullet-point notes. - Runs as a system cron job with no gateway involvement or context bloat; progress tracked via state file. - Designed for seamless integration with the supermemory skill for full memory pipeline automation. - Offers extensive CLI options for session selection, provider/model switch, and dry-run mode.
Metadata
Slug session-scribe-openclaw
Version 1.0.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Session Scribe?

Automatically summarize active OpenClaw session transcripts into daily memory files using a cheap LLM. Run as a system cron job — reads new transcript entrie... It is an AI Agent Skill for Claude Code / OpenClaw, with 155 downloads so far.

How do I install Session Scribe?

Run "/install session-scribe-openclaw" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Session Scribe free?

Yes, Session Scribe is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Session Scribe support?

Session Scribe is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Session Scribe?

It is built and maintained by Kitsune (@kitsune); the current version is v1.0.1.

💬 Comments