← MeetlyCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Meetly
Snapshot Sep 30, 2026 · 23:02 UTC · version 2.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 506
}
],
"skill_md_contents": "---\nname: meetly-catch-up\ndescription: 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.\n---\n\n# Meetly Catch-up\n\nRetrieve only the meeting context needed for the request, preserve attribution,\nand turn it into a useful next step.\n\n1. Use `list_meetings` for recent or date-based requests. Use `search` when the\n user names a subject, participant, or phrase. Read a selected source with\n `fetch`; use `get_transcript` only for a bounded exact passage.\n2. Classify the primary meeting type: planning/decision, product discovery,\n engineering, learning, research/interview, customer conversation, or general\n notes.\n3. Lead with a compact summary of purpose, key points, decisions, commitments,\n and unresolved questions. Do not turn a suggestion into a decision or infer\n an owner, deadline, or speaker.\n4. Preserve synced speaker labels. Use `Unknown speaker` when attribution is\n absent. Distinguish transcript evidence from your inference.\n5. Recommend one best next artifact based on the meeting type and explain why in\n one sentence. Mention at most two alternatives:\n - product or engineering discussion: `$create-meetly-product-spec`\n - lecture or study session: `$create-meetly-learning-kit`\n - interview or open claims: `$create-meetly-research-brief`\n - relationships, systems, or dependencies: `$create-meetly-interactive-map`\n - planning, decisions, or customer calls: `$create-meetly-follow-up`\n6. End with one easy action, such as “Create the product spec?” If the user\n agrees, use the named skill without repeating retrieval or asking for facts\n already in the source.\n\nMeetly is read-only. Do not expose more private transcript text than the request\nneeds. If no meetings are synced, direct the user to Meetly Settings → Connect\nAI; MCP access requires Meetly Pro.\n"
}SHA-256: 9efd1d58ab1b081b58a47021a8275c5b0b07be6ca2110e4d7887f995a8d99bb1