본문으로 건너뛰기
cccskills
무료GitHub에 공개

meeting-notes

Turn rough meeting notes or a transcript into a structured recap with decisions, assigned tasks, stated deadlines, and open questions. Include a brief summary and flag missing or uncertain details so readers can identify the next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Turn raw notes or a transcript into a clean summary with decisions and action items.

설치 방법 보기

이럴 때 유용합니다

  • Turn rough meeting notes into a shareable recap
  • Extract tasks with owners and stated deadlines
  • Track unresolved questions after a discussion
  • Share decisions with people who missed the meeting

포함된 파일(1)

  • SKILL.md2.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Meeting Notes

Turn the mess of a meeting — half-sentences, tangents, crosstalk — into a record someone who wasn't there can act on. The value isn't a transcript; it's the decisions, the owners, and the next steps, pulled out and made unambiguous.

When to use this skill

Use Meeting Notes on raw notes, a rough transcript, or a recording summary to produce a structured recap: what was decided, who owns what, and what's still open. If the goal is to condense an article or report rather than a discussion, use Summarizer instead.

What a good recap captures

  • Decisions — what the group actually agreed, stated plainly. Distinguish a decision from a suggestion that went nowhere.
  • Action items — each with an owner and, where stated, a due date. An action with no owner is a wish; assign it or flag it as unassigned.
  • Open questions — things raised but not resolved, so they don't quietly vanish.
  • Context — just enough of the "why" that a decision doesn't read as arbitrary later.

Principles

  • Signal over transcript. Don't replay the conversation — extract what matters and drop the rest.
  • Attribute carefully. Only assign an owner or a decision if the input actually supports it. If it's ambiguous, mark it "unassigned" or "unconfirmed" rather than guessing.
  • Never invent. If a date, owner, or decision wasn't stated, say so. Fabricated specifics are worse than an honest gap.
  • Neutral voice. Record what was said, not your opinion of it.

How to work

  1. Read the full input and separate discussion from outcomes.
  2. Pull out decisions, then action items (owner + due date where given), then open questions.
  3. Write a two-to-three sentence summary at the top so a skimmer gets the gist.
  4. Re-check every owner, date, and decision against the source; flag anything you had to infer.

Output format

Lead with a short Summary, then Decisions, Action items (as a checklist with owners), and Open questions. Omit any section that genuinely has nothing in it rather than padding it.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Build holaOS apps for connecting external services or managing work through a dashboard. The skill uses shared SDK building blocks for stored records, actions, and synchronization, with the dashboard and agent tools working on the same data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Building an external service integration
  • Creating a CRM dashboard
  • Building a content planning workspace
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

Analyze audience demographics and engagement to identify distinct groups, understand what they want, and prioritize valuable segments. Turn those findings into recommendations for content topics, formats, posting times, and tone, while explaining limits in the data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Identify distinct groups within an audience
  • Prioritize groups that engage or convert
  • Plan topics and formats for each audience group
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

Guide an agent through efficient use of an embedded browser by choosing targeted actions, searches, and waits. Reduce repeated tool calls and unnecessary page snapshots, while using more detailed inspection when the target or result remains unclear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Act on known buttons or fields with fewer browser calls
  • Locate a known target on a large page
  • Wait for navigation or downloads to finish
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

Validate workflows and reproduce issues in an embedded browser. Distinguish application problems from incorrect targets, missing waits, or session state, then report the shortest reliable reproduction steps with only the evidence needed to support the finding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reproducing a browser workflow failure
  • Checking for regressions after a fix
  • Distinguishing timing issues from application failures
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

Build the user interface for a holaOS app whose data resources are already connected through the SDK. Choose a feed, table, kanban board, form, or calendar layout using shared components and workspace styling.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Display scheduled items in a chronological feed
  • Show CRM contacts or tickets in a table
  • Organize issues by status on a kanban board
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

Package workspace skills and their required service integrations into one named, installable capability. Create a manifest that references existing skills, install the capability, and report which integrations still need to be connected.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Bundle multiple skills for a shared outcome
  • Declare required external service integrations
  • Create a manifest that references existing skills
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

holaboss-ai의 스킬 모두 보기

이 스킬의 문제 신고