lark-docx-ops

Create and edit Lark cloud documents via NyxID-brokered docx/v1 and drive/v1 APIs.

Updated May 4, 2026
One-click install
npx skills add https://github.com/ChronoAIProject/nyx-skills --skill lark-docx-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-docx-ops
Source: https://github.com/ChronoAIProject/nyx-skills/tree/main/lark-docx-ops
Command: npx skills add https://github.com/ChronoAIProject/nyx-skills --skill lark-docx-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation and editing of Lark cloud documents (Docx), eliminating the need for manual document creation and management.

Core Features & Use Cases

  • Document Creation and Editing: Create and edit documents directly through the bot's NyxID-brokered APIs.
  • Access Control: Grant full access to created documents to the requester.
  • Scope Probe: Acts as a docx-scope probe to report missing permissions.
  • Use Case: Ideal for team collaboration where multiple users need to access and edit shared documents.

Quick Start

Use the lark-docx-ops skill to create a new document titled 'Meeting Notes' and append the following headings and text paragraphs.

Frequently Asked Questions about lark-docx-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Lark cloud documents automatically for team collaboration?

You can create Lark cloud documents automatically by using this Skill to call docx/v1 APIs through NyxID authentication. It handles document creation and grants full access to the requester.

Can I edit existing Lark Docx files through an API integration?

Yes, editing Lark Docx files is supported through the bot's NyxID-brokered APIs. The Skill manages document editing by interacting directly with the docx/v1 endpoints.

What NyxID permissions do I need to manage Lark documents?

Managing Lark documents requires proper NyxID authentication along with access to both docx and drive scopes. The Skill acts as a scope probe to report any missing permissions.

How does access control work for newly created Lark documents?

Access control for newly created Lark documents is handled by granting full access directly to the requester. This ensures team members can immediately edit shared documents.

What is the best way to probe missing permissions for Lark document APIs?

The best way to probe missing permissions is using this Skill's built-in scope probe functionality. It checks your NyxID authentication against required docx and drive scopes.

Why does Lark document creation fail when using API integrations?

Lark document creation fails when proper NyxID authentication is missing or access to docx and drive scopes is insufficient. The Skill reports these missing permissions as a scope probe.