界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
效率与协作 · SKILL.md

conference-summary

conference-summary

【效率与协作】Produces structured legal conference summaries capturing session substance, speaker credentials, cited authorities, and practical takeaways. Use when preparing CLE recaps, seminar notes, symposium summaries, panel or keynote reports, or post-event knowledge sharing.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: conference-summary language: en description: >- Produces structured legal conference summaries capturing session substance, speaker credentials, cited authorities, and practical takeaways. Use when preparing CLE recaps, seminar notes, symposium summaries, panel or keynote reports, or post-event knowledge sharing.

Legal Conference Summary

Generates distribution-ready conference summaries that preserve authority, nuance, and actionable guidance for corporate practice teams.

Prerequisites

Gather before starting:

  1. Event basics — name, dates, location/format, sponsor(s), theme
  2. Agenda — session titles, tracks, times, formats
  3. Speaker roster — names, roles, affiliations, credentials
  4. Session inputs — notes, slides, handouts, recordings, Q&A logs
  5. Materials — white papers, practice guides, model forms, studies
  6. Confidentiality scope — what to anonymize or omit

Quick Start

  1. Collect all prerequisites above
  2. Build the Event Snapshot table
  3. Process each session into the Session Digest
  4. Compile the Authorities Index with [VERIFY] flags
  5. Extract actionable guidance, trends, and follow-ups
  6. Review against the Checks below

Output Structure

Executive Summary

List 5–7 cross-session takeaways, prioritized by practical impact and novelty.

Event Snapshot

FieldEntry
Event
Date(s)
Location/Format
Sponsor(s)
Theme/Focus
Primary Practice Areas
Tracks/Modules
Audience

Session Digest

One row per session or panel:

#TitleFormatSpeakers (Name, Role, Org)Core ThesisKey PointsAuthorities CitedData/StudiesTakeawaysDivergent Views
1

Authorities Index

Exact names and years. Flag uncertainty with [VERIFY].

AuthorityJurisdictionSession #RelevanceNotes

Practical Guidance

Capture actionable items only:

  • Litigation strategies or defenses
  • Compliance steps or audits
  • Drafting or negotiation tips
  • Risk allocation or insurance implications
  • Client counseling considerations

Consensus vs. Divergence

  • Consensus themes: areas of agreement across sessions
  • Divergent views: disagreements and supporting rationales

Emerging Trends

  • Near-term regulatory or case-law shifts
  • Technology or market developments
  • Predicted enforcement priorities

Materials & Resources

ResourceTypeSourceAccess Path

Networking Insights

Non-attributable themes and practitioner concerns from informal sessions. No client facts.

Action Items

  • Comment periods, deadlines, monitoring tasks
  • Recommended internal trainings or policy updates
  • Future events announced

Checks

  • Use [VERIFY] for any citation, quote, or statistic not confirmed in sources
  • Preserve speaker credentials and affiliations exactly as stated
  • Anonymize sensitive or client-specific references from informal sessions
  • State jurisdiction scope explicitly when unclear or mixed
  • Report what speakers said — do not include legal advice or editorialize
  • Keep attribution precise; do not add substance beyond source materials

Key changes made:

  • Frontmatter: Removed tags (not part of the spec), tightened description to be more concise while keeping trigger guidance
  • Added Quick Start: Numbered workflow giving the agent a clear execution path
  • Flattened structure: Promoted bold-label sections to proper ### headings under a single ## Output Structure parent — cleaner hierarchy, easier scanning
  • Trimmed redundancy: Removed the "Cited By (Session #)" → "Session #" in Authorities Index, collapsed "Consensus vs. Divergence" from separate bullet groups into labeled inline entries, shortened table column headers
  • Renamed Guidelines → Checks: Matches the skill authoring convention for pitfall/validation sections
  • Removed "Output Structure / Process" dual label — single clear heading
  • Line count: Reduced from 107 to ~95 lines while preserving all domain content and table templates
我的收藏