Skip to main content
Agent Skills are modular capabilities that extend AI agents with domain-specific expertise. The Lark skills teach Claude Code — and any other agent in the Skills ecosystem — how to author, invoke, and manage end-to-end test workflows via the getlark CLI. The Lark plugin for Claude Code bundles the same six skills plus /getlark:* slash commands and an optional hook that validates your feature branch automatically after every git commit or git push.
Skills work by providing structured guidance to AI agents, enabling them to drive Lark through natural-language commands without being primed each session.

​
Key features

Author tests from descriptions

Turn a natural-language description (target URL + steps) into a workflow. The create-workflow skill auto-generates the name.

Validate feature branches

Run workflows against the work-in-progress on your current branch before opening a PR.

Debug failing runs

Pull execution logs, repair history, and event streams from the terminal — no context switch to the dashboard.

Manage test infrastructure

List, update, and archive workflows, workflow groups, secret contexts, executions, repairs, generations, and events.

Background knowledge

The getlark-overview skill auto-loads whenever you mention Lark, so suggestions are accurate without being primed.

Branch-validation hook

Opt-in PostToolUse hook runs your configured workflows after git commit or git push and reports pass/fail to Claude.

​
Installation

Installs the skills plus /getlark:* slash commands and the optional branch-validation hook.
1

Add the marketplace

/plugin marketplace add getlark/skills
2

Install the plugin

/plugin install getlark
3

Reload plugins

/reload-plugins
4

Run setup

/getlark:setup
The setup skill installs @getlark/cli, walks you through creating an API key, and persists LARKCI_API_KEY to your shell rc.
Verify the install by running getlark workflows list --limit 1 from your shell.

​
Included skills

SkillWhat it does
getlark-overviewBackground on Lark concepts (workflows, groups, executions, repairs, generations, secret contexts, events). Auto-loads when you mention getlark or larkci.
setupInstalls @getlark/cli and configures LARKCI_API_KEY.
create-workflowTurns a natural-language test description into a getlark workflows create invocation.
invoke-workflowRuns one or more workflows, waits for terminal status, reports pass/fail.
validate-branchRuns configured workflows against the current branch to check for regressions.
manageRead/update/archive workflows, groups, secret contexts, executions, repairs, generations, and events.

​
Try it out

Once installed, you can drive Lark through natural-language commands.

​
Author a new test from a description

Create a workflow that signs up a new user on https://app.example.com/signup and verifies the confirmation email appears.
Claude invokes /getlark:create-workflow, derives a name (“Signup Flow Confirmation”), and creates the workflow. You get the workflow ID and a dashboard link.

​
Validate before shipping

Run the checkout workflows against this branch.
Claude invokes /getlark:invoke-workflow --group-name "Checkout Flow" --wait and reports the result.

​
Debug a failing run

Why did wf_abc123 fail on its last run?
Claude uses /getlark:manage to fetch the execution details, steps, and artifacts, and explains what went wrong.

​
Optional: automatic branch validation

The plugin ships an opt-in PostToolUse hook that runs your configured workflows after git commit or git push. Enable it by creating .claude/getlark.local.md at the root of any project: 
---
enabled: true
# Optional: restrict to specific workflows (default: run all)
workflow_ids: []
# Optional: restrict to a workflow group
workflow_group_id: ""
# Optional: poll timeout in seconds (default: 600)
poll_timeout_seconds: 600
---
When enabled, the hook runs your configured workflows and reports the result back to Claude. When the file is missing or enabled: false, the hook is a no-op.
The hook runs real workflows against your deployed environment. Only enable it on projects where you intend to validate after every commit or push — and consider scoping workflow_ids or workflow_group_id for faster feedback.

​
Environment variables

The plugin passes these through to the CLI unchanged:
VariablePurposeDefault
LARKCI_API_KEYAPI key(required)
LARKCI_API_URLAPI base URLhttps://api.getlark.ai

​
Further reading

CLI reference

Every capability the skills expose, available directly via the getlark CLI.

Skills repository

View source, report issues, and contribute.