Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize, update, and visualize codebase or personal knowledge wikis using LangChain OpenWiki. Enforces OKF v0.2, Grounded Claims, interactive visualizer graph, and MCP page-job lifecycle.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill integrates the official OpenWiki (langchain-ai/openwiki) into BDB Agent OS and Google Antigravity workflows. It provides autonomous documentation generation, Grounded Claims verification, an interactive local node graph visualizer, and host integrations for coding agents via Model Context Protocol (MCP).
OpenWiki is distributed globally via npm:
openwiki (v0.5.0+)To check and pull the latest upstream version:
# Check installed vs latest version
npm view openwiki version
# Update to latest upstream release
npm install -g openwiki@latest
# Verify installation
openwiki integrations list
A companion helper script is available in scripts/update_openwiki.sh:
bash skills/global_config/openwiki-skill/scripts/update_openwiki.sh
flowchart TD
A[Repository / Git Changes] --> B[openwiki --init / --update]
B --> C[Page-Job Queue & Grounded Claims]
C --> D[Coding Agent MCP Host / DeepAgents]
D --> E[Write Markdown Wiki in openwiki/]
E --> F[Claims Persistence in openwiki/.claims/]
E --> G[Interactive Visualizer: openwiki visualize]
openwiki/ (with .claims/ and .page-manifest.json).repo://src/server.ts#L40-L82). Stale or changed code automatically flags propositions for revision.openwiki/.run.json and resume deterministically.openwiki visualize) or deployable static bundle (openwiki visualize --export <dir>).# Initialize a new repository wiki in openwiki/
openwiki --init
# Update existing repository wiki based on changes and stale claims
openwiki --update
# Non-interactive one-shot update
openwiki -p --update "Document recent architecture updates"
# Initialize or update personal knowledge wiki (stores in ~/.openwiki/wiki)
openwiki personal --init
openwiki personal --update
# Launch interactive node graph on 127.0.0.1:4321
openwiki visualize
# Launch on custom port without opening browser automatically
openwiki visualize openwiki --port 4321 --no-open
# Export static HTML/JS/CSS bundle for GitHub Pages or MkDocs
openwiki visualize openwiki --export docs/openwiki-visualizer
OpenWiki connects to coding agents (Claude Code, OpenCode, Codex, Cursor) via MCP so the agent uses its own model and tools while OpenWiki manages the durable lifecycle.
openwiki integrations install claude
openwiki integrations install opencode
openwiki integrations install codex
openwiki integrations install cursor
openwiki integrations list
The integration exposes the native generation lifecycle:
openwiki_begin: Initiates run, checks Git root and diff status.openwiki_submit_plan: Submits page breakdown and taxonomy.openwiki_next_page: Fetches the next pending page in the queue.openwiki_inspect_page_claims: Optional inspection of claims requiring attention.openwiki_submit_page: Submits page prose and sparse Claim updates.openwiki_finish: Finalizes OKF manifest and provenance.Every factual Markdown page generated under openwiki/ MUST begin with valid OKF frontmatter:
---
type: <short descriptive concept type>
title: <human-readable title in the run language>
description: <one or two sentence retrieval-oriented summary in the run language>
tags: [<stable English tag>, ...]
---
Do not author generated, verified, sources, timestamp, or OpenWiki control fields. OpenWiki owns those. On update preserve accurate unknown producer-defined frontmatter fields.
A Claim is one substantive, independently falsifiable system truth. Prefer behavior, responsibilities, architecture/ownership, relationships, flow, invariants, lifecycle/failure semantics, configuration, security, persistence, operations, and extension seams.
repo://src/auth.ts#L20-L48.repo:// and use a repository-relative path; never submit a bare path such as src/auth.ts.openwiki/.claims/.Every repository using OpenWiki must maintain references in root files:
agent.md or CLAUDE.md## Documentation & Wiki
- Entrypoint: [openwiki/quickstart.md](openwiki/quickstart.md)
- Reference guides: [openwiki/architecture.md](openwiki/architecture.md)
README.mdInclude link to openwiki/quickstart.md or the exported visualizer directory.
/Users/username/...) be written to repository files, documentation, README, or wiki markdown files. Always use repository-relative paths (openwiki/...) or generic home folder variables (e.g. ~/.openwiki/).<API_KEY>.openwiki/ and root redirects.openwiki binary is installed and executable (openwiki integrations list).openwiki/ contains valid markdown pages with OKF frontmatter.openwiki visualize openwiki --export <dir>).agent.md/CLAUDE.md) reference openwiki/quickstart.md..md files.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。