Lark CLI Dev Hub Base for Openclaw

An automated development knowledge hub utility that provisions, structures, and synchronizes Feishu or Lark Base databases directly via command-line tools.

afengzi
v0.1.1
May 20, 2026
0
609
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install lark-cli-devhub-base

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install lark-cli-devhub-base using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Lark CLI Dev Hub Base?

The Lark CLI Dev Hub Base is a robust integration designed to establish an AI-readable, highly structured database within Feishu or Lark Base (Bitable). Operating as a key component in the ecosystem of Openclaw Skills, this utility allows developer environments and autonomous agents to systematically track execution states, system relationships, and project milestones directly from terminal workflows.

By serving as a bridge between local command-line operations and cloud-based collaborative sheets, it ensures that technical teams maintain a single, synchronized source of truth. Leveraging the Lark CLI Dev Hub Base alongside other Openclaw Skills empowers teams to execute schema provisioning, automate record tracking, and maintain resilient data-logging pipelines with zero manual overhead.

Lark CLI Dev Hub Base Use Cases

  • Automated Developer Knowledge Hubs: Automatically provision and sync master trackers for active repositories, module risks, and engineering ownership structures.
  • Structured Bug & Playbook Tracking: Instantly document complex bug fixes, historical root causes, and executable command-line diagnostic playbooks within a searchable database.
  • Agentic Memory Logging: Provide automated agents and continuous integration runtimes with a structured Bitable schema to log execution histories and verification trails.
  • Architecture Decision Logs (ADR): Archive critical project trade-offs, architecture selections, and future review triggers directly from developers' terminal workspaces.
  • Network Resiliency Buffering: Maintain write integrity during outages or API rate limit events by keeping records queued inside a local fallback outbox.

How Lark CLI Dev Hub Base Works

  1. Schema Reading: The tool retrieves structural layouts directly from the pre-configured local schema definitions file.
  2. Database Provisioning: Initializes and seeds the Lark or Feishu Base space with ready-to-use tables by processing standard seed configurations.
  3. Active Connection Querying: Utilizes lark-cli or feishu-cli binaries to fetch current table structures and verify active developer session access.
  4. Metadata-Enriched Writing: Validates rules locally to ensure mandatory context fields like Projects, Areas, and Search Keywords are strictly formatted and cleanly injected.
  5. Outbox Fallback Syncing: Detects API transport failures and automatically writes pending changes to a local outbox queue for future reconciliation.

Lark CLI Dev Hub Base Setup

Prerequisites

Make sure you have python3 and the lark-cli (or feishu-cli) tool locally installed and authenticated in your terminal.

Environment Configuration

Set your environment variables to locate your schema and point to your target Lark Base:

export BASE_TOKEN="your_lark_or_feishu_base_token"
export DEVHUB_HOME="$HOME/.codex/devhub"

Provisioning the Base

To automatically generate the default structure and seed mock information into your Lark Base, execute:

python3 "$DEVHUB_HOME/bin/devhub.py" provision \
  --schema "$DEVHUB_HOME/templates/base-schema.json" \
  --seed "$DEVHUB_HOME/templates/seed.example.json"

Accessing the Schema via CLI

You can inspect your structures and verify table layouts at any time using raw cli requests:

lark-cli base +table-list --base-token "$BASE_TOKEN" --as user --format json

Lark CLI Dev Hub Base Data Schema & Taxonomy

The Lark CLI Dev Hub Base organizes your development workflows into ten specialized relational tables designed for clean, metadata-heavy record keeping:

Table Name Description & Key Fields
Projects Tracks repository identities, focus domains, and active developer initiatives.
Areas Modules, filesystems, operational risks, and primary code ownership.
Tasks User-facing action items, current progress states, and next step checklists.
Bugfixes Records historical failures, root causes, technical resolutions, and validation checklists.
Pitfalls Reusable warnings, critical dependency quirks, and "check this first" recommendations.
Playbooks Repeatable system diagnostics, debug steps, and command checklists.
Decisions Technical choices, alternative paths evaluated, architecture tradeoffs, and triggers.
Releases Deployment steps, pre-push checklists, and evidence reports prior to production merges.
Artifacts Central link indices for external documentation, whiteboards, spreadsheets, and drawings.
AI Runs Execution outcomes, runtime summaries, and agent verification traces.

Lark CLI Dev Hub Base Advanced Features

  • Local Outbox Synchronization: Intercepts failed API calls and registers a local outbox receipt to ensure write consistency during transient offline periods.
  • Strict Metadata Validation Hooks: Mandates dense summarizations and indexed search keywords for every entry to optimize semantic discovery.
  • Cross-Platform Compatibility: Fully compatible with both standard Lark and localized Feishu (Bitable) enterprise environments.
  • Zero-UI DB Provisioning: Allows systems administrators to script, version-control, and spin up standardized team knowledge boards programmatically without using a web browser.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*