You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
72 lines
4.1 KiB
72 lines
4.1 KiB
2 months ago
|
---
|
||
|
|
name: "clawpilot-chats-digest"
|
||
|
|
description: "Generate an on-demand digest of recent activity in the Clawpilot/Lobster Pound Teams spaces — the new MCAPS Lobster Pound channel (primary, going forward) plus the two original group chats (MCAPS Lobster Pound and 'ClawPilot: From Copilot to Agent') — surfacing major Clawpilot releases, novel usage patterns, and items worth a closer look for Daniel. Triggers: /clawpilot-chats-digest, 'clawpilot digest', 'clawpilot chats digest', 'what's new in the clawpilot chats', 'lobster pound digest'."
|
||
|
|
---
|
||
|
|
|
||
|
|
## Clawpilot Chats Digest Skill
|
||
|
|
|
||
|
|
Produces a scannable digest of recent activity across the Clawpilot/Lobster
|
||
|
|
Pound Teams spaces. Runs on demand (formerly the "Clawpilot Chats Daily Digest"
|
||
|
|
automation).
|
||
|
|
|
||
|
|
### Source spaces
|
||
|
|
|
||
|
|
The community is migrating from the original meeting group chats (which hit
|
||
|
|
Teams' people limit) to a dedicated **channel**. Read all three so nothing is
|
||
|
|
missed during the transition; the channel is the primary source going forward.
|
||
|
|
|
||
|
|
1. **MCAPS Lobster Pound — Channel** (primary): `19:vGhTXeZ7TqvSIz4Kz_dxn_c-ZKikC1ZobNY7h-jcK5o1@thread.tacv2`
|
||
|
|
- teamId/groupId: `ae25e647-d5e2-45e6-bbd8-8bb8c59d74f5`
|
||
|
|
- Web link: https://teams.microsoft.com/l/channel/19%3AvGhTXeZ7TqvSIz4Kz_dxn_c-ZKikC1ZobNY7h-jcK5o1%40thread.tacv2/Lobster%20Pound?groupId=ae25e647-d5e2-45e6-bbd8-8bb8c59d74f5&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47
|
||
|
|
2. **MCAPS Lobster Pound — Group chat** (legacy): `19:meeting_ZmUxNTBhOTgtOTgxMC00OThkLWJlNGMtOTM3NDA1YjM5MzNj@thread.v2`
|
||
|
|
3. **ClawPilot: From Copilot to Agent — Group chat** (legacy): `19:meeting_MmYzMzYyNjMtNjMzOC00M2RjLWIwNzAtY2ZmZjcxZjcwMjNh@thread.v2`
|
||
|
|
|
||
|
|
Note: `workiq_list_chat_messages` accepts the channel's `@thread.tacv2` ID in its
|
||
|
|
`chatId` parameter exactly like a group chat, and returns top-level channel
|
||
|
|
posts. (Threaded replies under a post may not all come back; if a post clearly
|
||
|
|
references discussion, note that the thread may have more.)
|
||
|
|
|
||
|
|
### Time window
|
||
|
|
|
||
|
|
Default to the **last 24 hours**. If the user specifies a different range
|
||
|
|
(e.g. "this week", "since Monday", "last 3 days"), honor that instead.
|
||
|
|
|
||
|
|
### Steps
|
||
|
|
|
||
|
|
1. For each ID above, call `workiq_list_chat_messages` with limit 50.
|
||
|
|
**Do NOT search for the chats — use the IDs directly** (this includes the
|
||
|
|
channel `@thread.tacv2` ID).
|
||
|
|
(Messages come back as HTML in an `<external_content>` wrapper — strip the
|
||
|
|
tags and skip `<systemEventMessage/>` entries when composing.)
|
||
|
|
2. Filter to messages within the requested window (default: since 24 hours ago, PT).
|
||
|
|
3. Compose a digest with these sections:
|
||
|
|
- **Major Releases & Changes** — announcements of new Clawpilot features,
|
||
|
|
releases, breaking changes, or rollouts.
|
||
|
|
- **Interesting Usage Patterns** — novel/creative ways people are using
|
||
|
|
Clawpilot (skills, automations, workflows, MCP tricks, prompts,
|
||
|
|
integrations). Prioritize things useful to Daniel given his work
|
||
|
|
(Obsidian vault automations, EOD summaries, OMR Reliability Tooling,
|
||
|
|
TradeTrail, Teams/meeting archival, expense reports, etc.).
|
||
|
|
- **Worth a Closer Look** — 2–5 specific items Daniel should consider trying
|
||
|
|
or following up on, each with a one-line "why this matters to you" note.
|
||
|
|
- **Other Notable Discussion** — brief bullets for anything else worth
|
||
|
|
knowing (bugs, gotchas, requests, debates).
|
||
|
|
4. For each item, cite source: space name + author + short quote/paraphrase.
|
||
|
|
Skip pure noise (greetings, off-topic chatter, reactions only). If a space had
|
||
|
|
no relevant activity, say so in one line.
|
||
|
|
|
||
|
|
### Output
|
||
|
|
|
||
|
|
Present the digest directly in the chat as markdown (headings + bullets,
|
||
|
|
scannable, under 2 minutes to read). Only send it via `m_send_teams_message`
|
||
|
|
or `workiq_send_chat_message` if the user explicitly asks for it to be delivered
|
||
|
|
to Teams.
|
||
|
|
|
||
|
|
### Error handling
|
||
|
|
|
||
|
|
If any ID returns an error (e.g. chat/channel deleted or renamed), fall back to
|
||
|
|
`workiq_search_chats` by the space name and note it in the digest so Daniel can
|
||
|
|
update the ID in this skill. The two `@thread.v2` group chats are legacy and may
|
||
|
|
eventually go quiet or be archived — that's expected; just note "no recent
|
||
|
|
activity" rather than treating it as an error.
|