本文へ移動
cccskills
無料GitHub で公開

follow-up-from-granola

Turn a meeting into work — read its Granola notes, extract the commitments that belong to this user, and carry each one out or draft it (a code change, a ticket, a reply) with a trace back to the note. Use when the user says "do the follow-ups from", "implement what we agreed", "make tickets from", or points at a meeting after a sync, planning session, or customer call.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Turn the meeting into work

A meeting produces commitments, and most of them evaporate because nobody turned them into tasks. The job is to read the notes, find the commitments that are this user's to act on, and take each one as far as the workspace allows — without inventing work the meeting did not ask for.

1. Read the whole meeting before extracting anything

Fetch the meeting with get_meetings. If the user gave a title or a date, find it with list_meetings first and confirm it is the right instance — a recurring meeting has many. Read the notes end to end: action items sit in a section, but commitments also hide in the discussion ("I'll take a look at that", "we should ship that first").

2. Extract commitments, and attribute each one

For each commitment record what, who owns it, by when, and the sentence in the notes it comes from. Keep only what the notes support. When ownership is unclear, check get_meeting_transcript for who actually said it; if it is still unclear, list it as unassigned rather than handing it to the user.

3. Sort by what the workspace can do

  • A code change the user owns — make it in the workspace and open it for review, citing the meeting.
  • A ticket or issue — file it through whichever tracker plugin is connected, with the note's wording and the meeting in the body.
  • A message or reply — draft it. Never send on the user's behalf unless they asked for exactly that.
  • Someone else's item — list it under "not yours" so the user can nudge them; do not act on it.

Ask before acting only when a commitment is ambiguous or expensive. A clear "fix the flaky test" in the notes does not need a second confirmation.

4. Report with the trace

Finish with one line per commitment: what you did with it (changed, filed, drafted, skipped and why) and the meeting and line it came from. The user should be able to check every item against the notes.

Anti-patterns

  • Doing the generated "next steps" verbatim. Summaries guess at action items; verify each against the discussion before treating it as a commitment.
  • Turning every mention into a task. "Someone should look at that eventually" is not a commitment; a name and a timeframe are.
  • Acting on other people's items. A meeting assigns work to many people; the user asked for their follow-ups.
  • Losing the trace. A ticket that does not say which meeting asked for it gets re-litigated at the next one.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

10x

無料

Personalized audit that teaches the advanced Superset features the user isn't using yet (automations, parallel agents, tasks, multi-host, terminal remote control, custom commands, MCP, pages) and sets them up live. Use when the user wants to get more out of Superset, asks "what else can Superset do", "how do I 10x my workflow", "what am I missing", or wants to learn a specific Superset feature.

日本語の概要は準備中です。原文の説明を表示しています。

superset-sh/superset1.5万2026年10月13日 更新

automate

無料

Turn a recurring chore into a Superset automation. Drafts the agent prompt, confirms the schedule or event trigger and the target, creates it with the CLI, and reviews the first run together. Use when the user wants a scheduled or recurring agent, a daily or weekly job, or an agent that reacts to a Slack message, GitHub pull request, Linear issue, Sentry issue or incoming email, or says things like "every morning do X", "automate this", "set up a cron agent", "run this on a schedule", "when someone opens a PR, do X".

日本語の概要は準備中です。原文の説明を表示しています。

superset-sh/superset1.5万2026年10月13日 更新

browser

無料

Open, navigate, screenshot, read, click, and type in web pages from an agent. Use when the user asks to open a URL, preview or verify a running web app, check a page's console, fill a form, click through a web flow, or automate anything in a browser, including "open localhost:3000", "screenshot the page", "what does the console say", "click the submit button", "I'm logged in on Chrome". Drives the in-app browser pane of a Superset workspace by default and Browser Use for browsers the panes cannot reach.

日本語の概要は準備中です。原文の説明を表示しています。

superset-sh/superset1.5万2026年10月13日 更新

Write Stripe code against what the API does today — plan the product shape, confirm every parameter from Stripe's own docs and schemas, and keep the agent in a sandbox. Use when adding checkout, billing, subscriptions, invoicing, or webhooks to a codebase, or when debugging Stripe integration code that compiles but behaves wrong.

日本語の概要は準備中です。原文の説明を表示しています。

superset-sh/superset1.5万2026年10月13日 更新

Verify UI behavior end-to-end by driving the running desktop app over the Chrome DevTools Protocol. Use when asked to verify, reproduce, or confirm a UI change, bug, or regression in the real app rather than in tests.

日本語の概要は準備中です。原文の説明を表示しています。

superset-sh/superset1.5万2026年10月13日 更新

ci-triage

無料

Diagnose a failing GitHub Actions run — find the first real error in the logs, tell a flake apart from a genuine failure, and identify the commit that broke it. Use when checks are red on a PR, a workflow failed, the build is broken, CI is flaky, or the user asks why a run failed or whether a failure is real.

日本語の概要は準備中です。原文の説明を表示しています。

superset-sh/superset1.5万2026年10月13日 更新

superset-sh のスキルをすべて見る

このスキルの問題を報告する