Taku Compact

PassAudited by ClawScan on May 11, 2026.

Overview

This instruction-only skill is coherent and benign, but it will inspect your project/session state and save a local summary in .taku.

This appears safe for its intended purpose, but generated briefs can include local diffs, decisions, command results, and conversation context. Review `.taku/context/current.md` and timestamped compact files before committing, syncing, or sharing them.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The agent may inspect local repository state and changed-file content to summarize active work.

Why it was flagged

The skill instructs the agent to run local git/file inspections. This is purpose-aligned for producing an accurate work brief, but users should know repo changes and diffs may be read.

Skill content
Inspect git and file-system evidence when a repo is available: - `git status --short` - `git diff --stat` - `git diff --name-only` - relevant `git diff` hunks
Recommendation

Use the skill in repositories where you are comfortable having the current diff and project context summarized; review generated briefs before sharing them.

What this means

Briefs may remain on disk and influence future handoffs or agent work if they are inaccurate or contain sensitive details.

Why it was flagged

The skill creates persistent local context files that may later be reused by users or agents. This is disclosed and scoped, but stored summaries can contain sensitive project/session details or stale claims.

Skill content
Default persistence: 1. Create `.taku/context/` if needed. 2. Write the latest brief to `.taku/context/current.md`. 3. Write the same brief to `.taku/context/compact-YYYYMMDD-HHMMSS.md`.
Recommendation

Review `.taku/context` briefs periodically, avoid including secrets, and delete or edit stale summaries before sharing the project.