lexiang-skill_skill

This skill helps you manage Lexiang knowledge base content via API, including teams, spaces, entries, AI search, uploads, and permissions.
  • Python

2.6k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill lexiang-skill

  • _meta.json272 B
  • README.md8.8 KB
  • SKILL.md7.2 KB

Overview

This skill integrates with the Lexiang (Tencent 乐享) knowledge base API to provide full CRUD for teams, spaces, entries, files, and document blocks. It also supports address book management, AI search and QA, file upload, and task management. The skill is optimized for programmatic content and permission management within enterprise knowledge platforms.

How this skill works

The skill authenticates using AppKey/AppSecret and caches a short-lived token, then calls Lexiang REST endpoints with proper headers (Authorization and x-staff-id for write operations). It maps the platform data model (Team -> Space -> Entry tree -> File) and uses JSON:API conventions to create or update entries and blocks. The integration prefers API-provided links but can assemble canonical URLs using the tenant domain when links are absent.

When to use it

  • Automate creation or bulk import of documentation into a corporate knowledge base.
  • Manage team and space permissions or synchronize an external directory with the Lexiang address book.
  • Upload files, create structured pages, or programmatically edit online document blocks.
  • Run AI-driven search or Q&A over organizational knowledge for chatbots or internal assistants.
  • Build scheduled exports, backups, or audits of knowledge content and access logs.

Best practices

  • Store credentials in environment variables and rely on the provided init script to refresh and cache tokens (tokens last ~2 hours).
  • Always include x-staff-id for write operations, AI search/QA, and permission changes to avoid authorization errors.
  • Use the Markdown upload path for bulk or batch content; use the blocks API for fine-grained, programmatic edits and nested structures.
  • Prefer API response links when constructing user-facing URLs; otherwise format links using the tenant domain and resource patterns.
  • Respect rate limits (most endpoints ~3000/min; token acquire limit ~20/10min) and implement retry/backoff for 401/429 responses.

Example use cases

  • Batch import a set of Markdown product guides into a Space, optionally nesting under a parent entry.
  • Implement an internal chatbot that calls AI search and QA endpoints to answer staff questions from the knowledge base.
  • Automate user and department provisioning by syncing from an HR system into the Lexiang address book.
  • Create a CI job that updates release notes via the blocks API to keep documentation in sync with deployments.
  • Build a backup workflow that lists teams, spaces, entries, and exports content HTML or Markdown for archival.

FAQ

Set LEXIANG_APP_KEY, LEXIANG_APP_SECRET, and LEXIANG_STAFF_ID in environment variables or the configured credentials files; the init script sources them and fetches a token.

When do I need x-staff-id header?

Include x-staff-id on all write operations, AI search/QA calls, and any API that modifies permissions or resources to avoid "must specify staff" errors.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational