@synap-core/workspace-templates 0.6.3 → 0.7.0

package/src/meetings-knowledge.yaml

@@ -0,0 +1,204 @@
+# Meetings & Knowledge workspace template
+# A standalone capture layer for meetings: pull the transcript, summarize it,
+# and turn it into the things that actually matter afterward — notes, tasks,
+# and the people involved. Reuses the pod-wide person/task/note kinds so a
+# meeting's output lands where every other workspace already looks for it.
+
+meta:
+  slug: meetings-knowledge
+  name: Meetings & Knowledge
+  description: Import and summarize meetings — transcripts become notes, action items become tasks, and attendees become tracked people.
+  icon: video
+  color: "#8B5CF6"
+  tags: [meetings, notes, tasks, transcripts, calendar]
+  isPublic: true
+
+workspace:
+  name: Meetings & Knowledge
+  description: Import and summarize meetings — transcripts become notes, action items become tasks, and attendees become tracked people.
+  subtype: meetings-knowledge
+  visibility: pod_visible
+  capabilities:
+    - meetings.import
+    - meetings.summaries
+  sourceRoles:
+    meetings: provider
+
+profiles:
+  # ── Meeting (owned here) ─────────────────────────────────────────────────
+  - slug: meeting
+    displayName: Meeting
+    icon: video
+    color: violet
+    description: A meeting — its date, attendees, and what came out of it.
+    properties:
+      - slug: meetingDate
+        label: Date
+        valueType: date
+        inputType: date
+      - slug: platform
+        label: Platform
+        valueType: string
+        inputType: select
+        enumValues: [zoom, google-meet, teams, in-person, other]
+      - slug: attendees
+        label: Attendees
+        valueType: array
+        inputType: text
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [scheduled, completed, processed]
+        constraints: { defaultValue: scheduled }
+      - slug: summary
+        label: Summary
+        valueType: string
+        inputType: textarea
+      - slug: transcriptUrl
+        label: Transcript URL
+        valueType: string
+        inputType: url
+
+views:
+  - name: Meetings
+    slug: meetings
+    type: table
+    scopeProfileSlug: meeting
+    description: Every meeting, its platform, and whether it's been processed.
+    config:
+      columns: [title, meetingDate, platform, status]
+    defaultView: true
+  - name: Meetings Calendar
+    slug: meetings-calendar
+    type: calendar
+    scopeProfileSlug: meeting
+    description: Meetings on a calendar, keyed on their date.
+  - name: Action Items
+    slug: meeting-action-items
+    type: kanban
+    scopeProfileSlug: task
+    groupBy: status
+    description: Tasks generated from meetings, by status.
+    config:
+      groupBy: status
+
+entityLinks:
+  - sourceProfileSlug: meeting
+    targetProfileSlug: person
+    type: attended_by
+    label: Attended by
+  - sourceProfileSlug: meeting
+    targetProfileSlug: task
+    type: generated
+    label: Generated
+  - sourceProfileSlug: meeting
+    targetProfileSlug: note
+    type: summarized_in
+    label: Summarized in
+
+# Playbook — pulls the transcript (Fireflies) and calendar context (Google
+# Calendar), summarizes it, and writes the follow-through: a note, tasks per
+# action item, and any new attendees. Bound to the meeting kind so a captured
+# meeting can offer this as a session.
+playbooks:
+  - name: Import & Summarize Meeting
+    description: Pull a meeting's transcript, summarize it, and extract action items and attendees into tasks, notes, and people.
+    goalTemplate: >-
+      Import the meeting {meeting} — pull its transcript from Fireflies and use
+      Google Calendar for scheduling/attendee context. Produce: {outputTypes}.
+      Create a note with the summary, create a task for each action item, and
+      make sure attendees not already tracked are captured as person entities.
+      Update the meeting record's summary, transcriptUrl, and status.
+    subjectProfile:
+      profileSlug: meeting
+    params:
+      - { name: meeting, type: entity, label: Meeting, required: true }
+      - { name: outputTypes, type: text, label: Outputs, defaultValue: "a summary note, action-item tasks, and updated attendee records" }
+    executor: is-agent
+    grants:
+      - fireflies_import_last_meeting
+      - fireflies_search
+      - calendar_list
+      - entity.create
+    status: active
+
+# Transcript import via Fireflies, calendar/attendee context via Google
+# (nango-google). The user connects each once on install; a missing key fails
+# gracefully per-skill.
+integrations:
+  - templateKey: fireflies
+  - templateKey: nango-google
+
+onboarding:
+  goal: >
+    Get recent meetings into the pod so summaries, action items, and attendees
+    are captured instead of living only in someone's memory of the call.
+  framing: |
+    THE CHIEF OF STAFF: Act as a sharp chief of staff who turns meetings into
+    follow-through. A meeting with no summary and no action items didn't
+    happen as far as the rest of the org is concerned.
+  expertise:
+    starters:
+      - >
+        Every meeting worth logging needs a "so what" — at least one action item
+        or decision. If a founder describes a meeting with no outcome, ask what
+        changed because of it.
+      - >
+        Attendees are people, not names in a transcript — capture them as
+        tracked contacts so the next meeting with them has history.
+    blindSpots:
+      - >
+        Recurring meetings (standups, 1:1s) get skipped because they feel
+        routine — but their action items are exactly what falls through the
+        cracks. Don't let "it's just a standup" excuse skipping capture.
+    bar: >
+      A handful of recent meetings are logged with a real summary and at least
+      one action item each, so the Import & Summarize playbook has something
+      concrete to run against.
+  collect:
+    - profileSlug: meeting
+      what: Recent or upcoming meetings worth tracking.
+      cardinality: few
+      keyFields: [meetingDate, platform]
+  openingQuestions:
+    - "What meetings do you want tracked — recurring ones, or just the important ones?"
+    - "Where do your meetings live — Zoom, Google Meet, somewhere else?"
+    - "Do you already record/transcribe them, or should that start now?"
+  doneWhen: A few meetings captured with a date and platform, at least one with a summary.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: Meetings
+  defaultApp: null
+  pinnedApps: [dashboard, data]
+  sidebarItems:
+    - kind: view
+      viewName: Meetings
+      label: Meetings
+      icon: video
+    - kind: view
+      viewName: Meetings Calendar
+      label: Calendar
+      icon: calendar
+    - kind: view
+      viewName: Action Items
+      label: Action Items
+      icon: check-square
+    - kind: app
+      appId: data
+      label: Data
+      icon: database
+
+bento:
+  viewName: Meetings
+  blocks:
+    - kind: view
+      viewName: Meetings
+      pos: { x: 0, y: 0, w: 8, h: 5 }
+    - kind: view
+      viewName: Action Items
+      pos: { x: 8, y: 0, w: 4, h: 5 }

package/src/outreach-comms.yaml

@@ -0,0 +1,282 @@
+# Outreach & Comms workspace template
+# A standalone, channel-first outreach workspace: personalized LinkedIn and
+# email sequences run against people and companies you already track pod-wide.
+# Owns the outreach data (campaigns + individual touches) and the playbook
+# that drafts and sends the next message — not a CRM, not a content calendar.
+# Reuses the pod-wide `person`/`company` kinds so a contact worked here is the
+# same entity a CRM or Ecosystem workspace sees, not a workspace-local twin.
+
+meta:
+  slug: outreach-comms
+  name: Outreach & Comms
+  description: Personalized LinkedIn and email outreach — sequenced touches against real people and companies, drafted and sent by an agent.
+  icon: send
+  color: "#0EA5E9"
+  tags: [outreach, linkedin, email, comms, sequences]
+  isPublic: true
+
+workspace:
+  name: Outreach & Comms
+  description: Personalized LinkedIn and email outreach — sequenced touches against real people and companies, drafted and sent by an agent.
+  subtype: outreach-comms
+  visibility: pod_visible
+  capabilities:
+    - outreach.campaigns
+    - outreach.touches
+  sourceRoles:
+    outreach: provider
+
+profiles:
+  # ── Actors ────────────────────────────────────────────────────────────────
+  # The pod-wide person and company kinds — declared minimally so campaign and
+  # touch links resolve. Kept light on purpose: identity lives elsewhere.
+  - slug: person
+    displayName: Person
+    icon: user
+    color: amber
+    description: A person you are reaching out to — a prospect, partner, or contact.
+    properties:
+      - slug: email
+        label: Email
+        valueType: string
+        inputType: email
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  - slug: company
+    displayName: Company
+    icon: building-2
+    color: "#10B981"
+    description: A company you are reaching out to.
+    properties:
+      - slug: website
+        label: Website
+        valueType: string
+        inputType: url
+      - slug: industry
+        label: Industry
+        valueType: string
+        inputType: text
+
+  # ── Outreach data (owned here) ───────────────────────────────────────────
+  - slug: outreach-campaign
+    displayName: Outreach Campaign
+    icon: target
+    color: sky
+    description: A sequence of personalized touches aimed at a segment — the "why we're reaching out" and the offer.
+    properties:
+      - slug: channel
+        label: Channel
+        valueType: string
+        inputType: select
+        enumValues: [linkedin, email, both]
+        constraints: { defaultValue: linkedin }
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [draft, active, paused, completed]
+        constraints: { defaultValue: draft }
+      - slug: targetSegment
+        label: Target segment
+        valueType: string
+        inputType: text
+        placeholder: e.g. Series A-B B2B SaaS founders
+      - slug: valueProp
+        label: Value proposition
+        valueType: string
+        inputType: textarea
+      - slug: callToAction
+        label: Call to action
+        valueType: string
+        inputType: text
+      - slug: startDate
+        label: Start date
+        valueType: date
+        inputType: date
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  - slug: outreach-touch
+    displayName: Outreach Touch
+    icon: message-circle
+    color: blue
+    description: A single message sent (or drafted) to one person as part of a campaign.
+    properties:
+      - slug: channel
+        label: Channel
+        valueType: string
+        inputType: select
+        enumValues: [linkedin, email]
+      - slug: touchType
+        label: Touch type
+        valueType: string
+        inputType: select
+        enumValues: [connection_request, follow_up, intro_email, reply]
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [drafted, sent, opened, replied, bounced, no_response]
+        constraints: { defaultValue: drafted }
+      - slug: sentDate
+        label: Sent date
+        valueType: date
+        inputType: date
+      - slug: messageContent
+        label: Message content
+        valueType: string
+        inputType: textarea
+
+views:
+  - name: Campaigns
+    slug: outreach-campaigns
+    type: table
+    scopeProfileSlug: outreach-campaign
+    description: Every outreach sequence, its channel, and its status.
+    config:
+      columns: [title, channel, status, targetSegment, startDate]
+    defaultView: true
+  - name: Touches
+    slug: outreach-touches
+    type: kanban
+    scopeProfileSlug: outreach-touch
+    groupBy: status
+    description: Individual messages, grouped by where they stand — drafted through replied.
+    config:
+      groupBy: status
+      cardFields: [channel, touchType, sentDate]
+
+entityLinks:
+  - sourceProfileSlug: outreach-campaign
+    targetProfileSlug: person
+    type: targets
+    label: Targets
+  - sourceProfileSlug: outreach-campaign
+    targetProfileSlug: company
+    type: targets
+    label: Targets
+  - sourceProfileSlug: outreach-touch
+    targetProfileSlug: person
+    type: sent_to
+    label: Sent to
+  - sourceProfileSlug: outreach-touch
+    targetProfileSlug: outreach-campaign
+    type: part_of
+    label: Part of
+
+# Playbook — drafts and sends the next personalized touch for a target, using
+# whatever we already know about them so the message isn't generic. Bound to
+# the campaign kind so a captured/updated campaign can offer this as a session.
+playbooks:
+  - name: Personalized Outreach
+    description: Draft a personalized LinkedIn or email message to a target contact, send it, and log the touch.
+    goalTemplate: >-
+      Reach out to {target} on {channel} as part of the "{campaign}" campaign.
+      Research them first using what we already know (their company, role, and
+      any prior touches) so the message is specific, not generic. Campaign
+      context — value proposition and call to action: {campaignContext}. Draft
+      the message, send it via {channel}, then create an outreach-touch record
+      logging what was sent and update the target's contact record with the
+      outcome.
+    subjectProfile:
+      profileSlug: outreach-campaign
+    params:
+      - { name: target, type: entity, label: Target contact, required: true }
+      - { name: campaign, type: text, label: Campaign name, required: true }
+      - { name: channel, type: choice, label: Channel, defaultValue: linkedin }
+      - { name: campaignContext, type: text, label: Value prop + call to action }
+    executor: is-agent
+    grants:
+      - linkedin_send_invite
+      - unipile_send_message
+      - gmail_send
+      - entity.create
+    status: active
+
+# LinkedIn send/search via Unipile, email send via Gmail (nango-google). The
+# user connects each once on install; a missing key fails gracefully per-skill.
+integrations:
+  - templateKey: unipile-linkedin
+  - templateKey: nango-google
+
+onboarding:
+  goal: >
+    Stand up an outreach motion — who we're targeting, on which channel, with
+    what offer — so the agent can start drafting and sending real touches
+    instead of waiting for a blank campaign.
+  framing: |
+    THE OUTBOUND LEAD: Act as a sharp SDR/outbound lead. Push for a SPECIFIC
+    segment and a SPECIFIC offer, not "reach out to everyone about our product".
+    A campaign with no segment and no value prop is just a contact list.
+  expertise:
+    starters:
+      - >
+        Name the segment as a person, not a market — "Head of Growth at
+        seed-to-Series-A B2B SaaS", not "SaaS companies". The agent personalizes
+        against a person, not a category.
+      - >
+        Every campaign needs ONE call to action, stated plainly — a call, a demo,
+        a reply. If the founder gives a vague goal ("build awareness"), push for
+        the concrete next step a touch should provoke.
+    blindSpots:
+      - >
+        Founders default to email when LinkedIn converts better for cold B2B —
+        ask which channel the target segment actually lives on before defaulting.
+      - >
+        A campaign with no target contacts yet is fine to create, but flag it —
+        the first touch needs at least one real person or company to reach.
+    bar: >
+      At least one real campaign exists with a named segment, a stated value
+      prop and call to action, and — ideally — a first target contact ready for
+      the Personalized Outreach playbook to run against.
+  collect:
+    - profileSlug: outreach-campaign
+      what: The outreach sequences to run — channel, target segment, and offer.
+      cardinality: few
+      keyFields: [channel, targetSegment, valueProp, callToAction]
+    - profileSlug: person
+      what: The first contacts to target with this campaign.
+      cardinality: few
+      keyFields: [email]
+  openingQuestions:
+    - "Who are you trying to reach — what role, at what kind of company?"
+    - "LinkedIn, email, or both?"
+    - "What's the one thing you want them to do after reading your message?"
+  doneWhen: At least one campaign captured with a channel, segment, and value prop, plus one target contact.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: Campaigns
+  defaultApp: null
+  pinnedApps: [dashboard, data]
+  sidebarItems:
+    - kind: view
+      viewName: Campaigns
+      label: Campaigns
+      icon: target
+    - kind: view
+      viewName: Touches
+      label: Touches
+      icon: message-circle
+    - kind: app
+      appId: data
+      label: Data
+      icon: database
+
+bento:
+  viewName: Campaigns
+  blocks:
+    - kind: view
+      viewName: Campaigns
+      pos: { x: 0, y: 0, w: 8, h: 5 }
+    - kind: view
+      viewName: Touches
+      pos: { x: 8, y: 0, w: 4, h: 5 }