Pome
Updated just nowruns daily

All components

Slack 0.1.0

0 of 51 API surfaces match the real Slack response.

SlackDegradedWrites not runMCP reads not runNo baseline
Baseline noneLast drift 17 Aug, resolved
3 Aug37 of 43 days matched · 2 unmeasuredToday

1 Responses

Whether this twin's answers match a captured real vendor response.

Read comparison
compared against a committed capture of the real vendor response
Baseline
no committed upstream capture has ever existed for this twin
Write round trip
did not run
MCP read leg
did not run

MCP slack_send_message Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/slack/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_schedule_message Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/slack/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_add_reaction Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/slack/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_create_conversation Not checked

this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/slack/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_search_public Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_search_public_and_private Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_search_channels Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_search_users Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_read_channel Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_read_thread Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_read_user_profile Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_list_channel_members Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_search_emojis Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

MCP slack_get_reactions Not checked

this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/slack/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST auth.test Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST conversations.list Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST conversations.info Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST conversations.create Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST conversations.archive Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST conversations.invite Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST conversations.join Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST conversations.leave Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST conversations.kick Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST conversations.members Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST conversations.history Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST conversations.replies Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST conversations.open Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST chat.postMessage Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST chat.update Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST chat.delete Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST chat.scheduleMessage Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST chat.deleteScheduledMessage Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST reactions.add Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST reactions.remove Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST reactions.get Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST users.list Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST users.info Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST users.lookupByEmail Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST users.profile.get Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST users.profile.set Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST pins.add Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST pins.remove Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST pins.list Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST search.messages Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST bookmarks.add Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST bookmarks.remove Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST bookmarks.list Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

REST conversations.setTopic Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST conversations.setPurpose Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST emoji.list Not checked

this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/slack/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early.

Run tsx tools/fidelity-watch/capture-slack-m1.ts and commit every fixture it writes. It says nothing about parity with real Slack, which only the L1 upstream lane can answer.

REST team.info Not checked

nothing has ever compared this surface against real Slack. It IS one of the 16 surfaces in the L1 upstream read lane, so a capture WOULD verify it — the committed upstream golden ships as an empty placeholder.

Run FIDELITY_SLACK_TOKEN=… bun run tools/fidelity-watch/capture-slack-upstream-golden.ts.

Every surface this twin publishes (51)

MCP · not captured 0 of 14 match

MCP slack_send_messageNot checked
MCP slack_schedule_messageNot checked
MCP slack_add_reactionNot checked
MCP slack_create_conversationNot checked
MCP slack_search_publicNot checked
MCP slack_search_public_and_privateNot checked
MCP slack_search_channelsNot checked
MCP slack_search_usersNot checked
MCP slack_read_channelNot checked
MCP slack_read_threadNot checked
MCP slack_read_user_profileNot checked
MCP slack_list_channel_membersNot checked
MCP slack_search_emojisNot checked
MCP slack_get_reactionsNot checked

REST · not captured 0 of 37 match

REST auth.testNot checked
REST conversations.listNot checked
REST conversations.infoNot checked
REST conversations.createNot checked
REST conversations.archiveNot checked
REST conversations.inviteNot checked
REST conversations.joinNot checked
REST conversations.leaveNot checked
REST conversations.kickNot checked
REST conversations.membersNot checked
REST conversations.historyNot checked
REST conversations.repliesNot checked
REST conversations.openNot checked
REST chat.postMessageNot checked
REST chat.updateNot checked
REST chat.deleteNot checked
REST chat.scheduleMessageNot checked
REST chat.deleteScheduledMessageNot checked
REST reactions.addNot checked
REST reactions.removeNot checked
REST reactions.getNot checked
REST users.listNot checked
REST users.infoNot checked
REST users.lookupByEmailNot checked
REST users.profile.getNot checked
REST users.profile.setNot checked
REST pins.addNot checked
REST pins.removeNot checked
REST pins.listNot checked
REST search.messagesNot checked
REST bookmarks.addNot checked
REST bookmarks.removeNot checked
REST bookmarks.listNot checked
REST conversations.setTopicNot checked
REST conversations.setPurposeNot checked
REST emoji.listNot checked
REST team.infoNot checked

2 Tool list

Whether this twin offers the same MCP tools the vendor's own server declares. A name-and-contract comparison with no response in it.

Slack twin18
Vendor tools/list19

18 shared names, on one scale.

Both declare it and the contracts agree 18

slack_send_message
slack_schedule_message
slack_add_reaction
slack_create_conversation
slack_create_canvas
slack_update_canvas
slack_search_public
slack_search_public_and_private
slack_search_channels
slack_search_users
slack_read_channel
slack_read_thread
slack_read_canvas
slack_read_user_profile
slack_list_channel_members
slack_read_file
slack_search_emojis
slack_get_reactions
Measured against digital-twins e035d34 · the run that produced it · FIDELITY.md · status.json