meeting-notes
Turn Meeting Notes into Clear Minutes
Rough meeting notes can hide decisions, responsibilities, and unresolved issues. This skill organizes pasted notes into concise minutes with clear actions and explicit markers for missing details.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "meeting-notes" from https://skillstore.io/skills/alapha888-meeting-notes.md and its manifest at https://skillstore.io/api/skills/alapha888-meeting-notes/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「meeting-notes」を使用しています。 The team approved a cache pilot. Maria will draft the proposal by 14 October. Pricing remains undecided until Finance shares estimates.
期待される結果:
- Conclusion: The team approved a cache pilot. Pricing remains unresolved.
- Decision: Run a cache pilot.
- Action: Maria will draft the proposal by 14 October.
- Open question: Pricing awaits Finance estimates; follow-up owner [unassigned], deadline [TBD].
「meeting-notes」を使用しています。 Everyone agreed to test the revised onboarding checklist. Someone needs to update the guide. Launch timing was discussed but not decided.
期待される結果:
- Conclusion: Test the revised onboarding checklist. Launch timing remains undecided.
- Decision: Test the revised onboarding checklist.
- Action: Update the guide; owner [unassigned], deadline [TBD].
- Open question: Launch timing; blocker [to confirm], next step [to confirm], owner [unassigned].
セキュリティ監査
安全All nine static findings are false positives from Markdown delimiters, placeholder labels, and meeting examples. No evidence found of command execution, system reconnaissance, data exfiltration, or prompt injection in SKILL.md.
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/alapha888-meeting-notes/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/alapha888-meeting-notes?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/alapha888-meeting-notes?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alapha888-meeting-notes/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/alapha888-meeting-notes.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
alapha888. (2026). meeting-notes security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alapha888-meeting-notes/audits/1BibTeX形式の引用
@techreport{alapha888-alapha888-meeting-notes-2026,
author = {alapha888},
title = {meeting-notes security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/alapha888-meeting-notes/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "meeting-notes security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "alapha888"
date-released: "2026-10-06"
url: "https://skillstore.io/skills/alapha888-meeting-notes/audits/1"
identifiers:
- type: other
value: "skillstore:alapha888-meeting-notes:audit:1"
description: "Skillstore immutable audit report identifier"
バリアントを比較
インストール可能なバリアント 3 件各作者のスキルは個別のインストール項目として維持されます。推奨バリアントは Skillstore の証拠で順位付けされます。
このバリアントが首位の理由
shubhamsaboo-meeting-notes
2026-09-09
curiouslearner-meeting-notes
2026-09-09
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Document project decisions
Turn project discussions into concise decisions, assigned follow-up work, and unresolved dependencies.
Summarize engineering meetings
Separate approved technical choices from proposals, then capture implementation owners and deadlines.
Prepare stakeholder minutes
Organize rough stakeholder notes into readable minutes while marking missing names, dates, and next steps.
これらのプロンプトを試す
Turn these notes into meeting minutes with a short conclusion, decisions, action items, and open questions: [paste notes].
Summarize these notes and list each action with its stated owner and deadline. Mark missing owners [unassigned] and missing deadlines [TBD]: [paste notes].
Create minutes from this transcript. Separate confirmed decisions from unresolved proposals, and record stated blockers and next steps: [paste transcript].
Produce concise minutes from these notes. Check each decision, owner, and deadline against the source; flag unsupported details and ambiguous dates: [paste notes].
ベストプラクティス
- Provide complete notes with explicit decisions, participant names, and dates when available.
- Review every action owner and deadline against the source before sharing minutes.
- Keep unresolved questions visible and confirm their blockers and next steps with attendees.
回避
- Treating every proposal or discussion topic as an approved decision.
- Guessing action owners, dates, or numbers that the notes do not establish.
- Replaying the conversation chronologically instead of extracting conclusions.