HavenSkills

Claude Productivity Skills

Plan work, document decisions and organize everyday team workflows.

Skills
6 skills

How to choose

Choose a planning skill for a task still taking shape, and a workspace integration for an existing document, meeting or handoff.

Filter

All skills in this category

lark-doc

Create and update working documents in Lark.

by larksuite
npx skills add larksuite/cli --skill lark-doc
Author
larksuite
Repo
GitHub

lark-calendar

Review schedules and manage calendar events inside a Lark workspace.

by larksuite
npx skills add larksuite/cli --skill lark-calendar
Author
larksuite
Repo
GitHub

lark-task

Create and organize tasks and track their completion in Lark.

by larksuite
npx skills add larksuite/cli --skill lark-task
Author
larksuite
Repo
GitHub

lark-workflow-meeting-summary

Turn meeting material into a summary with decisions and follow-up actions.

by larksuite
npx skills add larksuite/cli --skill lark-workflow-meeting-summary
Author
larksuite
Repo
GitHub

handoff

Record current progress, decisions and remaining work for the next person or agent.

by mattpocock
npx skills add mattpocock/skills --skill handoff
Author
mattpocock
Repo
GitHub

grill-me

Pressure-test a proposal by asking focused questions about its assumptions and decisions.

by mattpocock
npx skills add mattpocock/skills --skill grill-me
Author
mattpocock
Repo
GitHub

What productivity skills are for

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.

Which half you need

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.

Where these skills break in practice

  • A summary that is not decisions. Meeting notes that read back the agenda are useless. The output you want is: what was decided, who owns it, by when. Ask for those three explicitly.
  • Tasks with no owner. An agent creating tasks from a transcript will happily create five unassigned ones. Participants and assignees have to be named in the prompt, not inferred.
  • Handoffs that describe the past. A handoff listing what was done is a diary. The useful part is what is left, what was decided against, and where the bodies are buried.
  • Calendar writes without checking. Reviewing a schedule and mutating it are different permissions. Say which one you mean before an agent touches a shared calendar.
  • Documents overwritten instead of appended. “Update the doc” can mean either. State it, or lose the section someone else wrote.

The check that catches most of it

  1. Check that every action item has an owner and a date. Anything without both is a wish.
  2. Open the created document or task yourself and compare with the transcript — permissions are the usual failure: it landed in a workspace the team cannot see.
  3. For a handoff, read only the “remaining work” section and ask whether you could start from it. If not, it is incomplete.
  4. Re-run the summary on the same material. A summary that changes materially between runs is inventing structure rather than reading it.

Which page to read next

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.

How to evaluate the result

Check ownership, next steps and permissions before an agent writes into a shared workspace.

How to check the result

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.

Frequently asked questions

How do I install one of these productivity skills?

Use the command beside the skill, select a supported agent, then reload the agent and confirm it can see the skill in your project.

Why do the Lark skills fail with a permission error?

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.

What is the difference between handoff and grill-me?

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.

How do I check a meeting summary before sending it to the team?

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.

Can an agent write directly into team documents?

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.

Do the Lark skills work outside Lark?

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.

Can it summarise a meeting I upload?

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.