Meetly

View saved version →

---
name: create-meetly-follow-up
description: Create grounded meeting minutes, a decision log, action plan, status update, or follow-up message from an authorized Meetly planning, review, customer, or team meeting.
---

# Create a Meetly Follow-up

Find the meeting with `list_meetings` or `search`, then read it with `fetch`.
Use `get_transcript` only for bounded exact wording.

Choose the requested deliverable, or the lightest one that moves the work
forward. Separate decisions, proposals, action items, risks, and unanswered
questions. An action item needs an explicit task; include owner and deadline
only when the source supplies them. Formal minutes must not invent motions,
votes, attendance, or approvals.

For a follow-up email or status update, write for the intended audience and
include only necessary private detail. For a decision log, record the decision,
rationale, alternatives, dissent, and follow-up verification. For an action
plan, organize by outcome rather than transcript order.

Preserve speaker labels and include concise evidence for consequential claims.
Mark uncertain or inferred items for confirmation. Create the artifact with the
host's native writing capabilities; Meetly remains a read-only evidence source.

Referenced files: 1

View saved version →

---
name: create-meetly-interactive-map
description: Create an interactive visual map from relationships, arguments, concepts, systems, or dependencies discussed in an authorized Meetly meeting or lecture.
---

# Create a Meetly Interactive Map

Retrieve the source with `search` and `fetch`. Identify the map's central
question, the smallest useful set of nodes, and meaningful typed relationships.
Use speaker-tagged evidence to separate facts, proposals, decisions, risks, and
open questions.

Choose the visual grammar that best fits the source: concept map for learning,
system map for components and dependencies, argument map for claims and
evidence, or decision map for options and trade-offs. Avoid a decorative cloud
of transcript phrases.

When the host can create files or interactive artifacts, produce one
self-contained accessible HTML file with embedded CSS and JavaScript. It must:

- work without external libraries, fonts, trackers, or network requests;
- support keyboard navigation, visible focus, zoom/pan or an equivalent usable
  overview, and reduced-motion preferences;
- expose evidence on selection without dumping the whole transcript;
- remain readable in a static fallback and on narrow screens;
- escape meeting text before inserting it into HTML.

Otherwise, return a clearly structured map in the best native visual format the
host supports. Create it directly; do not call a Meetly HTML, prepare, render,
mind-map, or visualization tool.

Referenced files: 1

View saved version →

---
name: create-meetly-learning-kit
description: Create evidence-grounded notes, a study guide, flashcards, or a quiz from an authorized Meetly lecture, seminar, interview, or study session.
---

# Create a Meetly Learning Kit

Retrieve the source with `search` and `fetch`; use bounded `get_transcript`
pages only when exact detail is needed. Identify the central question, concepts,
dependencies, examples, misconceptions, and open questions.

Create the format the user requests. When they leave the format open, provide a
compact kit with learning goals, logically ordered notes, key terms, a recap,
and a short retrieval-practice quiz. For quizzes, vary question types, hide the
answer until the learner attempts it when the host supports interaction, and
give an evidence-backed explanation for every answer.

Prefer a coherent teaching sequence over transcript order. Preserve speakers and
timestamps in concise evidence citations. Never invent a speaker or fill a
material gap from general knowledge without labeling it as outside the meeting.
If the recording is incomplete or contradictory, say so.

Create the result directly with the host's native document or interactive
artifact capabilities. Do not call Meetly prepare or render tools.

Referenced files: 1

View saved version →

---
name: create-meetly-product-spec
description: Create an evidence-grounded product brief, PRD, or engineering specification from an authorized Meetly product, customer, design, or technical discussion.
---

# Create a Meetly Product Spec

Use `search` and `fetch` to retrieve the relevant meeting evidence. Use
`get_transcript` only when exact wording or a bounded missing passage matters.

Choose the lightest artifact that fits the user's goal:

- Product brief for discovery and alignment.
- PRD for agreed product behavior and measurable outcomes.
- Engineering specification for implementation decisions and interfaces.

Reorganize the discussion for the team that must decide or build, rather than
following transcript order. Cover context, problem, users, goals, non-goals,
requirements, success measures, constraints, decisions, rejected options, risks,
and open questions as applicable. Engineering specs should also cover system
context, data and interface changes, edge cases, security/privacy, rollout,
observability, and testing.

Requirements must be testable. Preserve speaker labels and attach concise quotes
or timestamped evidence to material claims. Mark host inference explicitly.
Never invent approvals, dates, owners, or technical constraints; surface
contradictions and missing decisions.

Create the document directly with the host's native document or coding
capabilities. Do not look for a Meetly prepare, render, HTML, or document tool.

Referenced files: 1

View saved version →

---
name: create-meetly-research-brief
description: Turn questions, hypotheses, or claims from an authorized Meetly interview or discussion into a sourced research brief that distinguishes meeting evidence from external evidence.
---

# Create a Meetly Research Brief

Use `search` and `fetch` to recover the discussion and its open claims. Extract
the research question, hypotheses, assumptions, evidence already offered,
disagreements, and decisions the research must inform.

Research unresolved claims with current primary sources when browsing is
available. Prefer official data, standards, original research, and first-party
documentation. For each important conclusion, distinguish:

- what meeting participants said;
- what external sources establish;
- your synthesis or recommendation.

Return an executive answer, evidence by question, conflicts or uncertainty,
implications for the decision, and a short next-step recommendation. Cite both
Meetly evidence and external sources close to the claims they support. Do not
upgrade a participant hypothesis into fact or hide contrary evidence.

Create the brief directly with the host's native research and document
capabilities. Meetly supplies private context; it does not browse or generate
the brief.

Referenced files: 1

View saved version →

---
name: meetly-catch-up
description: Summarize or answer from authorized Meetly meetings, especially when the user asks what happened, what was discussed, or what to do next without naming a specific artifact.
---

# Meetly Catch-up

Retrieve only the meeting context needed for the request, preserve attribution,
and turn it into a useful next step.

1. Use `list_meetings` for recent or date-based requests. Use `search` when the
   user names a subject, participant, or phrase. Read a selected source with
   `fetch`; use `get_transcript` only for a bounded exact passage.
2. Classify the primary meeting type: planning/decision, product discovery,
   engineering, learning, research/interview, customer conversation, or general
   notes.
3. Lead with a compact summary of purpose, key points, decisions, commitments,
   and unresolved questions. Do not turn a suggestion into a decision or infer
   an owner, deadline, or speaker.
4. Preserve synced speaker labels. Use `Unknown speaker` when attribution is
   absent. Distinguish transcript evidence from your inference.
5. Recommend one best next artifact based on the meeting type and explain why in
   one sentence. Mention at most two alternatives:
   - product or engineering discussion: `$create-meetly-product-spec`
   - lecture or study session: `$create-meetly-learning-kit`
   - interview or open claims: `$create-meetly-research-brief`
   - relationships, systems, or dependencies: `$create-meetly-interactive-map`
   - planning, decisions, or customer calls: `$create-meetly-follow-up`
6. End with one easy action, such as “Create the product spec?” If the user
   agrees, use the named skill without repeating retrieval or asking for facts
   already in the source.

Meetly is read-only. Do not expose more private transcript text than the request
needs. If no meetings are synced, direct the user to Meetly Settings → Connect
AI; MCP access requires Meetly Pro.

Referenced files: 1