wiki (v2)

What Is This

The "wiki (v2)" skill (Skill ID: lark-wiki) for the Happycapy Skills platform is a command-line interface (CLI) tool designed to programmatically create, manage, and organize knowledge base articles within the Lark Wiki environment. It enables users and developers to interact directly with Lark Wiki spaces and nodes, allowing for robust automation and integration of knowledge management workflows into broader digital solutions. The skill supports a range of operations on both knowledge spaces and document nodes, such as creating new documents, browsing the hierarchical structure, copying nodes, and retrieving lists of available spaces or nodes.

This skill is categorized under "design" and is particularly useful for teams and organizations using Lark Suite to centralize their knowledge management practices. The source code and further information can be found at its GitHub repository.

Why Use It

The "wiki (v2)" skill is essential for teams that need to streamline and automate the management of their Lark Wiki knowledge bases. Manual handling of documentation and organizational structures in a collaborative environment can be error-prone and time-consuming. By leveraging this skill, users can reliably:

• Automate the creation and organization of documentation at scale
• Integrate knowledge management into CI/CD or other automation pipelines
• Ensure consistency in knowledge base structure and permissions
• Reduce manual overhead for repetitive tasks such as document creation, copying, or organizational restructuring
• Programmatically maintain wiki content as part of broader digital operations

This skill is especially valuable for organizations with dynamic documentation needs or those seeking to implement robust knowledge governance within Lark Suite.

How to Use It

Prerequisites

Before using the "wiki (v2)" skill, ensure you have:

• The lark-cli tool installed
• The appropriate Lark API credentials and permissions configured (see the shared SKILL.md for details on authentication and permissions)

Discovering API Structures

Before invoking any API operation, always inspect the required parameter schema:

lark-cli schema wiki.<resource>.<method>

This command returns the structure for --data or --params arguments, detailing required and optional fields. Never guess the parameter format-always use the schema command to verify.

Working with Spaces

Spaces are top-level containers in the Lark Wiki hierarchy. The skill allows you to retrieve information about spaces, list all spaces, and get details on specific nodes within a space.

Get Space Information:

lark-cli wiki spaces get --params '{"space_id": "<SPACE_ID>"}'

List All Spaces:

lark-cli wiki spaces list

Get Space Node Details:

lark-cli wiki spaces get_node --params '{"node_id": "<NODE_ID>"}'

Managing Nodes

Nodes represent documents or folders within a wiki space. The skill enables you to create nodes, copy existing nodes, and list child nodes under a given parent.

Create a Node:

lark-cli wiki nodes create --data '{
  "space_id": "<SPACE_ID>",
  "parent_node_id": "<PARENT_NODE_ID>",
  "title": "New Document Title",
  "type": "doc" // or "shortcut"
}'

Copy a Node:

lark-cli wiki nodes copy --data '{
  "node_id": "<NODE_ID>",
  "target_parent_node_id": "<TARGET_PARENT_ID>"
}'

List Child Nodes:

lark-cli wiki nodes list --params '{"parent_node_id": "<PARENT_NODE_ID>"}'

Permissions

Each method requires specific scopes, which must be granted to your API credentials:

Ensure your application or automation has been granted the necessary scopes before attempting any operation.

When to Use It

The "wiki (v2)" skill should be used whenever you need to:

• Automate the creation or organization of documentation in Lark Wiki
• Integrate wiki document management into larger workflow automations
• Programmatically reflect organizational changes in documentation structure
• Batch process documentation tasks, such as mass creation, migration, or restructuring of wiki content
• Retrieve or audit the structure of your knowledge base for compliance or reporting

This skill is not intended for ad-hoc or interactive editing but rather for systematic, programmatic management of wiki content, especially in contexts where scale, consistency, and automation are paramount.

Important Notes

• Authentication and Permissions: Always review the shared SKILL.md file referenced in the documentation for up-to-date requirements on authentication and permission handling.
• Schema Inspection: Never attempt to use an API method without first running the schema command to confirm parameter formats. Incorrect parameters can lead to failed operations or data inconsistencies.
• Granular Scopes: Each API method has a dedicated scope. Verify that your API client has exactly the scopes required for the intended operations.
• No Guesswork: The CLI is strict-do not guess at field names or formats. Use schema queries to avoid errors.
• Intended for Automation: This skill is designed for programmatic use. While it can be used directly from the CLI, its true value is in automation and integration scenarios.
• CLI Only: All operations are performed via the lark-cli tool. There is no graphical interface provided by this skill.

By following these guidelines and leveraging the "wiki (v2)" skill, organizations can achieve reliable, scalable, and well-governed management of Lark Wiki documentation through programmatic means.