SuperAPI AI Directory

larc-onboarding

General & other

View repository

Updated 10-16 11:21

About this skill

LARC Onboarding — OpenClaw Channel First

TRIGGER: When the user needs LARC initial setup, connection verification, onboarding, test user guidance, or clarification of the roles of the plugin/channel.

Purpose of this skill

Prevent the following confusions during onboarding:

  • OpenClaw Feishu/Lark channel
  • official openclaw-lark plugin
  • LARC runtime
  • lark-cli の App ID / App Secret

Principles:

  1. The entry point the user actually talks to is the bot / chat app connected by the OpenClaw Feishu/Lark channel
  2. official openclaw-lark The plugin performs atomic Lark API operations behind it
  3. LARC governs the gate / queue / audit / memory
  4. lark-cli app credentials are for runtime authentication, not another conversation entry point

Division of roles

Layer Role Typical commands
OpenClaw Feishu/Lark channel User-facing chat app / bot connection, DM / group entry points, pairing openclaw channels login --channel feishu
official openclaw-lark plugin Atomic operations such as IM / Docs / Base / Calendar OpenClaw plugin-side configuration
LARC Permission explanation, approve gate, queue, write-back, audit larc quickstart, larc ingress ...
lark-cli auth Authentication for the LARC runtime to connect to tenant resources lark-cli config init, lark-cli auth login

Standard onboarding order

Step 0. Fix the conversation entry point

First, state the following clearly:

  • What the test user uses is the bot / chat app on the OpenClaw channel side
  • The app credentials for LARC are not an additional chat app to guide the user to

Step 1. Check OpenClaw

which openclaw
openclaw --version

If it is not installed, set up the OpenClaw usage environment before LARC.

Step 2. Connect the OpenClaw Feishu/Lark channel

openclaw channels login --channel feishu
openclaw gateway restart

As needed:

openclaw pairing list feishu
openclaw pairing approve feishu <CODE>

For group operation, check groupPolicy、groupAllowFrom、requireMention .

Success conditions:

  • The bot / chat app to guide the user to is settled on one
  • You can explain "which chat to talk to"

Step 3. official openclaw-lark Check the plugin

State clearly that the plugin is not a chat entry point, but a layer that calls the Lark API behind OpenClaw.

Check items:

  • official openclaw-lark Is it available
  • Is the configuration such that atomic actions such as IM / Docs / Base are handled on the plugin side

Step 4. Install the LARC runtime skill

bash scripts/install-openclaw-larc-runtime-skill.sh
openclaw skills list | rg larc-runtime

Step 5. Set up the LARC main body and lark-cli authentication

npm install -g @larksuite/cli
curl -fsSL https://raw.githubusercontent.com/ShunsukeHayashi/lark-agent-runtime/main/scripts/install.sh | bash
larc version

After that:

lark-cli config init --app-id <APP_ID> --app-secret-stdin --brand lark
lark-cli auth login
lark-cli auth status

Step 6. Run the LARC quickstart

larc quickstart --dry-run
larc quickstart

Step 7. Perform operation checks separately

A. Runtime-side check

larc status
larc ingress enqueue --text "onboarding test" --agent main --source claude-code
larc ingress openclaw --agent main --days 14

B. Chat entry point check

  • The user sends a message to the OpenClaw channel bot / chat app
  • Do not have them send it to the LARC auth app

What the agent must always state clearly

  • "Installing the plugin" does not mean "the number of chat apps increases"
  • The "conversation entry point" is on the OpenClaw channel side
  • lark-cli 's App ID / App Secret is runtime plumbing
  • the experimental IM daemon loop is not the main onboarding path

Common failures

Failure Cause Correct guidance
A different app launches lark-cli confusing 's credentials with the conversation entry point State clearly that the user talks to the OpenClaw channel bot
Thinking that just installing the plugin enables chat Confusing the roles of channel and plugin First openclaw channels login --channel feishu
Making the LARC daemon the main path Guiding the experimental path first Guiding the supervised / OpenClaw-assisted path first
The queue works, but chat does not go through pairing / allowlist / mention conditions not verified Check the OpenClaw channel settings

Completion criteria

Conditions for considering onboarding complete:

  1. The chat app / bot that the user is guided to is fixed to one
  2. Able to explain the roles of the OpenClaw channel and the official plugin
  3. larc quickstart passes
  4. larc status passes
  5. larc ingress openclaw Able to output the bundle with
  6. The test user can send to the correct chat app / bot

Reference