From getlark
This skill should be used when the user asks to "run a workflow", "invoke a larkci workflow", "run getlark tests", "trigger a test", "run all workflows", or runs `/getlark:invoke-workflow`. Invokes one or more getlark workflows, waits for terminal status, and reports pass/fail summaries. Prefer `validate-branch` when the user wants to gate a git branch (it picks the right workflows automatically); use `manage` to inspect past executions without kicking off a new run; use `create-workflow` first if no workflow exists yet.
How this skill is triggered — by the user, by Claude, or both
Slash command
/getlark:invoke-workflow [workflow-id | --all | --group <name>][workflow-id | --all | --group <name>]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run one or more getlark workflows and wait for completion, then report results. Default behavior is **invoke + poll** — the user gets a verdict, not just an execution ID.
Run one or more getlark workflows and wait for completion, then report results. Default behavior is invoke + poll — the user gets a verdict, not just an execution ID.
Accept any of:
wf_...)getlark workflows list)--all / "all" to run everythingIf the user ran /getlark:invoke-workflow <arg>, parse <arg> accordingly. Otherwise ask.
Based on input shape:
| Input | Resolution |
|---|---|
Starts with wf_ | Use directly as --workflow-ids |
| Looks like a name | getlark workflows list --limit 100, find match by name, use its id. If multiple match, ask. |
Group ID (wfl_grp_* or similar) | Use --group-id |
| Group name | Use --group-name "<name>" |
all / --all / unspecified + user said "everything" | Use --all |
Always pass --wait by default. Set a timeout that matches the expected run time; --timeout 600 (10 min) is a reasonable default for a single workflow, scale up for --all or large groups.
getlark workflows invoke \
--workflow-ids <id> \
--wait \
--timeout 600
Or for multiple:
getlark workflows invoke --all --wait --timeout 1800
If the user explicitly says "don't wait" / "fire and forget", drop --wait.
| Exit | Meaning | Action |
|---|---|---|
| 0 | All invoked workflows succeeded | Report ✅ with execution IDs |
| 1 | One or more workflows failed | List failing workflow IDs + their summaries |
| 2 | Timed out | Tell the user, offer to extend --timeout or check via /getlark:manage |
| 3 | Unexpected error | Surface stderr verbatim |
The CLI prints one line per workflow:
Workflow <id> executed successfully. Execution ID: <exec_id>Workflow <id> executed with failure. Execution ID: <exec_id>. Summary: <summary>Workflow <id> was cancelled. Execution ID: <exec_id>Parse these lines into a concise report for the user.
If any workflow failed, offer — do not auto-execute — follow-ups:
getlark workflows executions get <wf_id> <exec_id> to see step-by-step details?"getlark workflows executions logs <wf_id> <exec_id>?"getlark workflows repairs trigger <wf_id>?"Wait for user confirmation before running any of these.
For any execution, surface: https://dashboard.getlark.ai/workflows/<wf_id>/executions/<exec_id>
Single workflow by ID:
getlark workflows invoke --workflow-ids wf_abc123 --wait
Group by name:
getlark workflows invoke --group-name "Checkout Flow" --wait --timeout 1800
Everything:
getlark workflows invoke --all --wait --timeout 3600
list/get calls.npx claudepluginhub getlark/skills --plugin getlarkProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.