Plugin

vibe-keystone

Vibe Keystone bootstraps a CLAUDE.md for any repository — the load-bearing structural file every agent decision in that repo will rest on. Unlike a generic template, Keystone interviews the user for org / decision surface / voice rules / persona before drafting, so the produced file reflects YOUR conventions, not 626Labs defaults baked in. Tenant-aware: detects the repo type from filesystem signals (code platform / marketing site / long-form writing / mixed) and adapts the produced CLAUDE.md to the right shape. Use when starting a new repo or when an existing CLAUDE.md is stale. The keystone is what every other Claude Code workflow rests on; investing 5 minutes here saves agent-confusion across hundreds of future sessions in the repo.

• Published source
• Repository

Analysed

11 October 2026

Last observed

11 October 2026

What the code does

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.