lark-router

Select authentication type and minimum scopes for Lark API calls.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ShunsukeHayashi/lark-harness --skill lark-router
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-router
Source: https://github.com/ShunsukeHayashi/lark-harness/tree/main/.claude/skills/lark-router
Command: npx skills add https://github.com/ShunsukeHayashi/lark-harness --skill lark-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decides the appropriate authentication level (user/bot/blocked) and the minimum scopes needed before calling the Lark API, preventing misconfigurations and API errors.

Core Features & Use Cases

  • Automatic auth routing based on simple task analysis to choose between user, bot, or blocked.
  • Minimum scope guidance to use the least privileged access required for the operation.
  • Safe execution flow that integrates with lark-cli to apply the correct credentials for common actions like IM, wiki, or calendar tasks.

Quick Start

Run larc auth router "<task description>" to determine the appropriate authentication and minimum scopes before executing any Lark API call.

Frequently Asked Questions about lark-router

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

FAQPage Schema
How do I determine the correct authentication type for Lark API calls?▼

To determine Lark API authentication, analyze the task to decide between user, bot, or blocked access. Automating this selection prevents misconfigurations and API errors before executing actions like IM notifications or calendar events.

What is the minimum scope required for a Lark wiki update?▼

The minimum scope for a Lark wiki update is determined by analyzing the task's required access level. The router applies a three-rule evaluation to output the least privileged scopes needed for the bot or user to execute the action safely.

How do I configure lark-cli credentials for automated IM notifications?▼

To configure lark-cli credentials for IM notifications, run an auth router evaluation with the task description. It outputs CLI invocation guidance to apply the correct user or bot credentials and minimum scopes before the API call.

Does the Lark API auth router support tasks outside of IM, wiki, and calendar?▼

The Lark API auth router evaluates IM, wiki, and calendar tasks to choose authentication. While its three-rule evaluation logic can process simple task descriptions, metadata explicitly confirms support for these common action types.

Why does my Lark API call fail with a permission error?▼

Lark API calls fail with permission errors when the authentication level or scopes are misconfigured. Applying an auth routing step before execution ensures you select the correct user or bot access and minimum scopes to prevent these errors.