CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

summarize-meeting

Use when the work-journal app asks to summarize a recorded meeting transcript into participants, summary, decisions, and action items.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

summarize-meeting

Headless skill for the work-journal app. The prompt names one input file.

Rules

  • Read only the input file named in the prompt. Read nothing else and run no commands.
  • The input has one record per line. If the file is long, read it in parts (offset/limit) until you have read all of it, then answer.
  • Reply with ONLY one JSON object matching the schema below. No prose, no code fences.
  • Never invent meetings, people, or action items that the input does not support.
  • Empty input gives empty arrays and empty strings (for markdown skills, headings with "None." under each).

Input

JSON with meeting (id, app, start, end, title), transcript (t, speaker, text), and screens (descriptions of on-screen content).

Rules specific to this skill

  • The mic track speaker (You) is always the user; list it as {"speaker":"You","name":"","confidence":1} unless a name is given.
  • Name a remote speaker only from transcript cues (for example "thanks, Priya") or on-screen participant labels. Otherwise name is "".
  • confidence is 0-1; direct address or a clear label is high, a weak inference below 0.7. Do not guess from voice or role.
  • List every distinct speaker label in participants.
  • summary: 2-4 sentences. decisions and action_items only when stated; owner is "" if unclear.
  • Empty transcript gives {"participants":[],"summary":"","decisions":[],"action_items":[]}.

Output schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "summarize-meeting output",
  "type": "object",
  "additionalProperties": false,
  "required": [
    "participants",
    "summary",
    "decisions",
    "action_items"
  ],
  "properties": {
    "participants": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": false,
        "required": [
          "speaker",
          "name",
          "confidence"
        ],
        "properties": {
          "speaker": {
            "type": "string"
          },
          "name": {
            "type": "string"
          },
          "confidence": {
            "type": "number",
            "minimum": 0,
            "maximum": 1
          }
        }
      }
    },
    "summary": {
      "type": "string"
    },
    "decisions": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "action_items": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": false,
        "required": [
          "text",
          "owner"
        ],
        "properties": {
          "text": {
            "type": "string"
          },
          "owner": {
            "type": "string"
          }
        }
      }
    }
  }
}
Repository

chandler767/WorkJournal

Path

work-journal/skills/work-journal/skills/summarize-meeting/SKILL.md

Last updated
First committed

Also appears in

chandler767/WorkJournal
In sync

since Oct 20, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.