Skills

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

Claude Code plugin
Vercel Skills CLI

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

Add the marketplace

/plugin marketplace add getlark/skills

Install the plugin

/plugin install getlark

Reload plugins

/reload-plugins

Run setup

/getlark:setup

The setup skill installs @getlark/cli, walks you through creating an API key, and persists GETLARK_API_KEY to your shell rc.

The Vercel Skills CLI installs just the skills (no slash commands or hooks) and works with Claude Code, Cursor, Codex, OpenCode, Windsurf, Gemini CLI, Copilot, and more.

Install the skills

npx skills add getlark/skills

The CLI detects your agent and drops the skills in the right place (Claude SKILL.md, Cursor rules, AGENTS.md, etc.).

Run setup

Ask your agent to run the setup skill. It installs @getlark/cli, helps you create an API key at the dashboard, and persists GETLARK_API_KEY to your shell rc.

Verify the install by running getlark workflows list --limit 1 from your shell.

Included skills

Skill	What it does
`getlark-overview`	Background on Lark concepts (workflows, groups, executions, repairs, generations, secret contexts, events). Auto-loads when you mention getlark or larkci.
`setup`	Installs `@getlark/cli` and configures `GETLARK_API_KEY`.
`create-workflow`	Turns a natural-language test description into a `getlark workflows create` invocation.
`invoke-workflow`	Runs one or more workflows, waits for terminal status, reports pass/fail.
`validate-branch`	Runs configured workflows against the current branch to check for regressions.
`manage`	Read/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:

Variable	Purpose	Default
`GETLARK_API_KEY`	API key	(required)
`GETLARK_API_URL`	API base URL	`https://api.getlark.ai`

CLI reference

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

Skills repository

View source, report issues, and contribute.

Getting started

Agents

Guides

Concepts

Integrations

Beta features

Key features

Author tests from descriptions

Validate feature branches

Debug failing runs

Manage test infrastructure

Background knowledge

Branch-validation hook

Installation

Included skills

Try it out

Author a new test from a description

Validate before shipping

Debug a failing run

Optional: automatic branch validation

Environment variables

Further reading

CLI reference

Skills repository

​Key features

Author tests from descriptions

Validate feature branches

Debug failing runs

Manage test infrastructure

Background knowledge

Branch-validation hook

​Installation

​Included skills

​Try it out

​Author a new test from a description

​Validate before shipping

​Debug a failing run

​Optional: automatic branch validation

​Environment variables

​Further reading

CLI reference

Skills repository

Key features

Installation

Included skills

Try it out

Author a new test from a description

Validate before shipping

Debug a failing run

Optional: automatic branch validation

Environment variables

Further reading