lark-doc
Create and update working documents in Lark.
npx skills add larksuite/cli --skill lark-docPlan work, document decisions and organize everyday team workflows.
Choose a planning skill for a task still taking shape, and a workspace integration for an existing document, meeting or handoff.
Create and update working documents in Lark.
npx skills add larksuite/cli --skill lark-docReview schedules and manage calendar events inside a Lark workspace.
npx skills add larksuite/cli --skill lark-calendarCreate and organize tasks and track their completion in Lark.
npx skills add larksuite/cli --skill lark-taskTurn meeting material into a summary with decisions and follow-up actions.
npx skills add larksuite/cli --skill lark-workflow-meeting-summaryRecord current progress, decisions and remaining work for the next person or agent.
npx skills add mattpocock/skills --skill handoffPressure-test a proposal by asking focused questions about its assumptions and decisions.
npx skills add mattpocock/skills --skill grill-meNo skill in this category has a full write-up yet.
The skills on this page have one thing in common: they move work between people and between sessions. Writing a document, booking a meeting, tracking a task, summarising decisions, handing work over, stress-testing a plan — none of it is hard in isolation, and all of it is where context gets lost.
There are two halves on this page, and they answer different questions.
For a task that is still taking shape, use the planning pair from mattpocock/skills. grill-me asks the questions you skipped — it takes a proposal and pressure-tests the assumptions and decisions behind it, which is cheaper than discovering them in review. handoff then writes down progress, decisions and remaining work so the next person or the next session can start without re-reading a conversation. Run them in that order: decide, then record. A handoff written before the decision is a log of uncertainty.
For work that already exists in a workspace, use the Lark four from larksuite/cli. lark-doc creates and updates documents; lark-calendar reads schedules and manages events; lark-task creates and tracks tasks; lark-workflow-meeting-summary turns meeting material into decisions plus follow-up actions. They install from the same repo as separate skills, so install only the ones your team actually uses — the value is in the account access, not in having all four.
Writing and docs covers the long-form versions of these documents. Agent workflow covers the skill file format and how to run more than one skill in sequence.
Check ownership, next steps and permissions before an agent writes into a shared workspace.
Check that owners, next steps and access permissions match the intended team. A summary without a decision, an owner and a date is not finished.
Use the command beside the skill, select a supported agent, then reload the agent and confirm it can see the skill in your project.
The four Lark skills need an authenticated workspace and app scopes for documents, calendar and tasks. If the agent says it cannot see your files, check authorisation before suspecting the skill.
Use handoff to record progress, decisions and remaining work for the next person or agent. Use grill-me before implementation to test a plan and surface its assumptions.
Review the first three outputs. A usable summary names a decision, an owner and a date for each item; anything else is still an open question.
The connected account’s permissions determine where the agent can write. Give it a dedicated writable folder, keep shared team documents read-only and confirm changes before expanding its access.
No. They read and write Lark documents, calendars and tasks — the value is the workspace connection. For a different suite you need that suite's own skills.
lark-workflow-meeting-summary works from meeting material you provide and produces decisions and follow-up actions. Without a transcript there is nothing to summarise.