Update to Flowlines
Snapshot Oct 24, 2026 · 13:14 UTC · version 0.4.1
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Payment or plan references changed
Full description — Now says: report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder),...
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Sep 30, 2026 · 23:10 UTC
report.
Oct 24, 2026 · 13:14 UTC
report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor).
Skill instructions
Sep 30, 2026 · 23:10 UTC
report. - Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example "Find out why the billing agent fails on refund requests". - **A user.** `get_user_activity` for the timeline, outco...
Oct 24, 2026 · 13:14 UTC
report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor). ## Tool discipline - The Flowlin...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,15 +1,23 @@ --- name: flowlines-investigate-session -description: Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report. +description: Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor). --- # Flowlines session investigation Go from a symptom to a verifiable cause with the smallest exposure of end-user content. Aggregates first, then the session, then only the turns that matter. +## Tool discipline + +- The Flowlines MCP server is the only data source for this skill. Do not open the Flowlines app, drive a browser, use computer-use, or search the web to find data, unless the user explicitly asks you to. +- When the server cannot answer part of the question, say so in the answer and list it in `unmet_needs` of `report_outcome`. If the information lives in the Flowlines app, tell the user where to look; do not go there yourself. +- Match the effort to the question. For a plain question, make the minimum calls (`get_workspace`, `get_context`, then the one or two tools that answer it), answer, and `report_outcome`. Run the full procedure below only when the user asks for an investigation or evidence for a report, and skip `save_note` and evidence sessions unless the procedure runs in full or the user asks for them. +- If authentication is required, or a generic MCP error (such as `-32603`) repeats on one read-only check, use `flowlines-doctor` when available for connection recovery before further data calls. Client diagnostics and native sign-in are allowed for this repair. After verification, resume the original request with the same namespace, range, and `user_intent`. +- If `flowlines-doctor` is unavailable, use only the failing client's connection status and native reconnect action. Reconnect once only when that client reports an authentication problem; leave browser consent to the user, then verify with one read-only call. If the action is unavailable, give the user the reconnect step in their client and wait for completion. For an unexplained generic error or failed verification, stop data calls, give the user the error and a pointer to Flowlines support. Do not access Flowlines infrastructure or present unavailable data as empty. + ## Conventions for every Flowlines tool call -- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example "Find out why the billing agent fails on refund requests". +- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example "Find out why the billing MCP server fails on refund requests". - Start with `get_workspace` once, then `get_context` for the namespace. Read pinned notes first: the problem may already be a known artifact. - Flowlines data is real production conversations. Quote the minimum, mask names, emails, phone numbers, addresses, identifiers, and payment details, and never copy a transcript into a note, ticket, or report. - End with `report_outcome` as the last tool call. @@ -19,9 +27,9 @@ Pick the entry that matches what the user has: - **A signal.** `list_signals` to find it, then `get_signal` for evidence and affected sessions and users. -- **A user.** `get_user_activity` for the timeline, outcomes, agents, intents, signals, and representative sessions. Prefer this over listing that user's sessions. +- **A user.** `get_user_activity` for the timeline, outcomes, MCP servers, intents, signals, and representative sessions. Prefer this over listing that user's sessions. - **A session id.** `get_session` directly. -- **A description.** `search` with `types` narrowed to `session` or `turn`, a time window, and the agent, then `fetch` the locators worth opening. +- **A description.** `search` with `types` narrowed to `session` or `turn`, a time window, and the MCP server, then `fetch` the locators worth opening. - **A pattern.** `aggregate_sessions` grouped by `intent`, `agent`, or `day` with `failure_rate` and `failure_count`, ordered by the metric, to find where the problem concentrates before opening anything. ## Steps @@ -30,9 +38,9 @@ 2. Choose at most five representative sessions: the earliest, the most recent, and the ones the signal or user activity points at. `list_sessions` with `outcome`, `user_feedback`, `intent_family`, `from`, and `to` narrows the pick. 3. `get_session` for each. Read the analysis and the turn tree before any content: the session summary, outcome, and findings often name the failing turn. 4. `get_turn` only for the turns the analysis points at. Compare the user's request, the tool calls, and the assistant reply on that turn. Look for the usual causes: wrong intent classification, a tool error surfaced as a normal reply, missing context, a policy refusal, a loop, or a truncated response. -5. Check whether the cause is upstream of the agent: an ingestion gap (turns missing, timestamps out of order), an unmapped user identity, or an evaluator artifact. Pinned notes and `list_agent_attributes` help here. +5. Check whether the cause is in telemetry or analysis: an ingestion gap (turns missing, timestamps out of order), an unmapped user identity, or an evaluator artifact. Pinned notes and `list_agent_attributes` help here. 6. Confirm the cause on a second session before calling it a cause. One session is an anecdote. -7. Estimate blast radius with one more `aggregate_sessions` filtered to the intent or agent, and check `list_signals` for a signal that already tracks it. +7. Estimate blast radius with one more `aggregate_sessions` filtered to the intent or MCP server, and check `list_signals` for a signal that already tracks it. 8. If the finding is durable and verified, `save_note` with the finding, the evidence in aggregate terms, and how future analysis should account for it. Never include personal data in the note. 9. `report_outcome`. @@ -40,10 +48,10 @@ ``` Symptom: what was reported, in one line -Scope: sessions, users, agents, first and last occurrence, trend +Scope: sessions, users, MCP servers, first and last occurrence, trend Cause: the mechanism, with the turn-level evidence (masked, minimal quotes) Confirmed on: session ids used as evidence -Blast radius: share of sessions for the intent or agent in the window +Blast radius: share of sessions for the intent or MCP server in the window Related signals and notes Recommended fix or next check Open questions (also sent as unmet_needs)
Full technical diff · 2 changed fields
changed /description
"Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report."
"Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor)."
changed /skill_md_contents
"---\nname: flowlines-investigate-session\ndescription: Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report.\n---\n\n# Flowlines session investigation\n\nGo from a symptom to a verifiable cause with the smallest exposure of end-user content. Aggregates first, then the session, then only the turns that matter.\n\n## Conventions for every Flowlines tool call\n\n- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example \"Find out why the billing agent fails on refund requests\".\n- Start with `get_workspace` once, then `get_context` for the namespace. Read pinned notes first: the problem may already be a known artifact.\n- Flowlines data is real production conversations. Quote the minimum, mask names, emails, phone numbers, addresses, identifiers, and payment details, and never copy a transcript into a note, ticket, or report.\n- End with `report_outcome` as the last tool call.\n\n## Starting points\n\nPick the entry that matches what the user has:\n\n- **A signal.** `list_signals` to find it, then `get_signal` for evidence and affected sessions and users.\n- **A user.** `get_user_activity` for the timeline, outcomes, agents, intents, signals, and representative sessions. Prefer this over listing that user's sessions.\n- **A session id.** `get_session` directly.\n- **A description.** `search` with `types` narrowed to `session` or `turn`, a time window, and the agent, then `fetch` the locators worth opening.\n- **A pattern.** `aggregate_sessions` grouped by `intent`, `agent`, or `day` with `failure_rate` and `failure_count`, ordered by the metric, to find where the problem concentrates before opening anything.\n\n## Steps\n\n1. Scope the problem with aggregates. Establish how many sessions, users, and days are affected and whether it is growing. `get_metric_definition` for any rate you quote.\n2. Choose at most five representative sessions: the earliest, the most recent, and the ones the signal or user activity points at. `list_sessions` with `outcome`, `user_feedback`, `intent_family`, `from`, and `to` narrows the pick.\n3. `get_session` for each. Read the analysis and the turn tree before any content: the session summary, outcome, and findings often name the failing turn.\n4. `get_turn` only for the turns the analysis points at. Compare the user's request, the tool calls, and the assistant reply on that turn. Look for the usual causes: wrong intent classification, a tool error surfaced as a normal reply, missing context, a policy refusal, a loop, or a truncated response.\n5. Check whether the cause is upstream of the agent: an ingestion gap (turns missing, timestamps out of order), an unmapped user identity, or an evaluator artifact. Pinned notes and `list_agent_attributes` help here.\n6. Confirm the cause on a second session before calling it a cause. One session is an anecdote.\n7. Estimate blast radius with one more `aggregate_sessions` filtered to the intent or agent, and check `list_signals` for a signal that already tracks it.\n8. If the finding is durable and verified, `save_note` with the finding, the evidence in aggregate terms, and how future analysis should account for it. Never include personal data in the note.\n9. `report_outcome`.\n\n## Output shape\n\n```\nSymptom: what was reported, in one line\nScope: sessions, users, agents, first and last occurrence, trend\nCause: the mechanism, with the turn-level evidence (masked, minimal quotes)\nConfirmed on: session ids used as evidence\nBlast radius: share of sessions for the intent or agent in the window\nRelated signals and notes\nRecommended fix or next check\nOpen questions (also sent as unmet_needs)\n```\n\n## Handling content\n\n- Reference sessions and turns by id and index, not by pasting them.\n- When a quote is unavoidable, keep it to the fragment that proves the point and replace identifiers with placeholders such as `<email>`.\n- Do not reproduce prompts, system instructions, or tool payloads in full.\n- If the user asks for a full transcript, point them to the session in the Flowlines app rather than reproducing it here.\n"
"---\nname: flowlines-investigate-session\ndescription: Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor).\n---\n\n# Flowlines session investigation\n\nGo from a symptom to a verifiable cause with the smallest exposure of end-user content. Aggregates first, then the session, then only the turns that matter.\n\n## Tool discipline\n\n- The Flowlines MCP server is the only data source for this skill. Do not open the Flowlines app, drive a browser, use computer-use, or search the web to find data, unless the user explicitly asks you to.\n- When the server cannot answer part of the question, say so in the answer and list it in `unmet_needs` of `report_outcome`. If the information lives in the Flowlines app, tell the user where to look; do not go there yourself.\n- Match the effort to the question. For a plain question, make the minimum calls (`get_workspace`, `get_context`, then the one or two tools that answer it), answer, and `report_outcome`. Run the full procedure below only when the user asks for an investigation or evidence for a report, and skip `save_note` and evidence sessions unless the procedure runs in full or the user asks for them.\n- If authentication is required, or a generic MCP error (such as `-32603`) repeats on one read-only check, use `flowlines-doctor` when available for connection recovery before further data calls. Client diagnostics and native sign-in are allowed for this repair. After verification, resume the original request with the same namespace, range, and `user_intent`.\n- If `flowlines-doctor` is unavailable, use only the failing client's connection status and native reconnect action. Reconnect once only when that client reports an authentication problem; leave browser consent to the user, then verify with one read-only call. If the action is unavailable, give the user the reconnect step in their client and wait for completion. For an unexplained generic error or failed verification, stop data calls, give the user the error and a pointer to Flowlines support. Do not access Flowlines infrastructure or present unavailable data as empty.\n\n## Conventions for every Flowlines tool call\n\n- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example \"Find out why the billing MCP server fails on refund requests\".\n- Start with `get_workspace` once, then `get_context` for the namespace. Read pinned notes first: the problem may already be a known artifact.\n- Flowlines data is real production conversations. Quote the minimum, mask names, emails, phone numbers, addresses, identifiers, and payment details, and never copy a transcript into a note, ticket, or report.\n- End with `report_outcome` as the last tool call.\n\n## Starting points\n\nPick the entry that matches what the user has:\n\n- **A signal.** `list_signals` to find it, then `get_signal` for evidence and affected sessions and users.\n- **A user.** `get_user_activity` for the timeline, outcomes, MCP servers, intents, signals, and representative sessions. Prefer this over listing that user's sessions.\n- **A session id.** `get_session` directly.\n- **A description.** `search` with `types` narrowed to `session` or `turn`, a time window, and the MCP server, then `fetch` the locators worth opening.\n- **A pattern.** `aggregate_sessions` grouped by `intent`, `agent`, or `day` with `failure_rate` and `failure_count`, ordered by the metric, to find where the problem concentrates before opening anything.\n\n## Steps\n\n1. Scope the problem with aggregates. Establish how many sessions, users, and days are affected and whether it is growing. `get_metric_definition` for any rate you quote.\n2. Choose at most five representative sessions: the earliest, the most recent, and the ones the signal or user activity points at. `list_sessions` with `outcome`, `user_feedback`, `intent_family`, `from`, and `to` narrows the pick.\n3. `get_session` for each. Read the analysis and the turn tree before any content: the session summary, outcome, and findings often name the failing turn.\n4. `get_turn` only for the turns the analysis points at. Compare the user's request, the tool calls, and the assistant reply on that turn. Look for the usual causes: wrong intent classification, a tool error surfaced as a normal reply, missing context, a policy refusal, a loop, or a truncated response.\n5. Check whether the cause is in telemetry or analysis: an ingestion gap (turns missing, timestamps out of order), an unmapped user identity, or an evaluator artifact. Pinned notes and `list_agent_attributes` help here.\n6. Confirm the cause on a second session before calling it a cause. One session is an anecdote.\n7. Estimate blast radius with one more `aggregate_sessions` filtered to the intent or MCP server, and check `list_signals` for a signal that already tracks it.\n8. If the finding is durable and verified, `save_note` with the finding, the evidence in aggregate terms, and how future analysis should account for it. Never include personal data in the note.\n9. `report_outcome`.\n\n## Output shape\n\n```\nSymptom: what was reported, in one line\nScope: sessions, users, MCP servers, first and last occurrence, trend\nCause: the mechanism, with the turn-level evidence (masked, minimal quotes)\nConfirmed on: session ids used as evidence\nBlast radius: share of sessions for the intent or MCP server in the window\nRelated signals and notes\nRecommended fix or next check\nOpen questions (also sent as unmet_needs)\n```\n\n## Handling content\n\n- Reference sessions and turns by id and index, not by pasting them.\n- When a quote is unavoidable, keep it to the fragment that proves the point and replace identifiers with placeholders such as `<email>`.\n- Do not reproduce prompts, system instructions, or tool payloads in full.\n- If the user asks for a full transcript, point them to the session in the Flowlines app rather than reproducing it here.\n"
Full snapshot data
{
"description": "Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 230
}
],
"name": "flowlines-investigate-session",
"skill_md_contents": "---\nname: flowlines-investigate-session\ndescription: Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor).\n---\n\n# Flowlines session investigation\n\nGo from a symptom to a verifiable cause with the smallest exposure of end-user content. Aggregates first, then the session, then only the turns that matter.\n\n## Tool discipline\n\n- The Flowlines MCP server is the only data source for this skill. Do not open the Flowlines app, drive a browser, use computer-use, or search the web to find data, unless the user explicitly asks you to.\n- When the server cannot answer part of the question, say so in the answer and list it in `unmet_needs` of `report_outcome`. If the information lives in the Flowlines app, tell the user where to look; do not go there yourself.\n- Match the effort to the question. For a plain question, make the minimum calls (`get_workspace`, `get_context`, then the one or two tools that answer it), answer, and `report_outcome`. Run the full procedure below only when the user asks for an investigation or evidence for a report, and skip `save_note` and evidence sessions unless the procedure runs in full or the user asks for them.\n- If authentication is required, or a generic MCP error (such as `-32603`) repeats on one read-only check, use `flowlines-doctor` when available for connection recovery before further data calls. Client diagnostics and native sign-in are allowed for this repair. After verification, resume the original request with the same namespace, range, and `user_intent`.\n- If `flowlines-doctor` is unavailable, use only the failing client's connection status and native reconnect action. Reconnect once only when that client reports an authentication problem; leave browser consent to the user, then verify with one read-only call. If the action is unavailable, give the user the reconnect step in their client and wait for completion. For an unexplained generic error or failed verification, stop data calls, give the user the error and a pointer to Flowlines support. Do not access Flowlines infrastructure or present unavailable data as empty.\n\n## Conventions for every Flowlines tool call\n\n- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example \"Find out why the billing MCP server fails on refund requests\".\n- Start with `get_workspace` once, then `get_context` for the namespace. Read pinned notes first: the problem may already be a known artifact.\n- Flowlines data is real production conversations. Quote the minimum, mask names, emails, phone numbers, addresses, identifiers, and payment details, and never copy a transcript into a note, ticket, or report.\n- End with `report_outcome` as the last tool call.\n\n## Starting points\n\nPick the entry that matches what the user has:\n\n- **A signal.** `list_signals` to find it, then `get_signal` for evidence and affected sessions and users.\n- **A user.** `get_user_activity` for the timeline, outcomes, MCP servers, intents, signals, and representative sessions. Prefer this over listing that user's sessions.\n- **A session id.** `get_session` directly.\n- **A description.** `search` with `types` narrowed to `session` or `turn`, a time window, and the MCP server, then `fetch` the locators worth opening.\n- **A pattern.** `aggregate_sessions` grouped by `intent`, `agent`, or `day` with `failure_rate` and `failure_count`, ordered by the metric, to find where the problem concentrates before opening anything.\n\n## Steps\n\n1. Scope the problem with aggregates. Establish how many sessions, users, and days are affected and whether it is growing. `get_metric_definition` for any rate you quote.\n2. Choose at most five representative sessions: the earliest, the most recent, and the ones the signal or user activity points at. `list_sessions` with `outcome`, `user_feedback`, `intent_family`, `from`, and `to` narrows the pick.\n3. `get_session` for each. Read the analysis and the turn tree before any content: the session summary, outcome, and findings often name the failing turn.\n4. `get_turn` only for the turns the analysis points at. Compare the user's request, the tool calls, and the assistant reply on that turn. Look for the usual causes: wrong intent classification, a tool error surfaced as a normal reply, missing context, a policy refusal, a loop, or a truncated response.\n5. Check whether the cause is in telemetry or analysis: an ingestion gap (turns missing, timestamps out of order), an unmapped user identity, or an evaluator artifact. Pinned notes and `list_agent_attributes` help here.\n6. Confirm the cause on a second session before calling it a cause. One session is an anecdote.\n7. Estimate blast radius with one more `aggregate_sessions` filtered to the intent or MCP server, and check `list_signals` for a signal that already tracks it.\n8. If the finding is durable and verified, `save_note` with the finding, the evidence in aggregate terms, and how future analysis should account for it. Never include personal data in the note.\n9. `report_outcome`.\n\n## Output shape\n\n```\nSymptom: what was reported, in one line\nScope: sessions, users, MCP servers, first and last occurrence, trend\nCause: the mechanism, with the turn-level evidence (masked, minimal quotes)\nConfirmed on: session ids used as evidence\nBlast radius: share of sessions for the intent or MCP server in the window\nRelated signals and notes\nRecommended fix or next check\nOpen questions (also sent as unmet_needs)\n```\n\n## Handling content\n\n- Reference sessions and turns by id and index, not by pasting them.\n- When a quote is unavoidable, keep it to the fragment that proves the point and replace identifiers with placeholders such as `<email>`.\n- Do not reproduce prompts, system instructions, or tool payloads in full.\n- If the user asks for a full transcript, point them to the session in the Flowlines app rather than reproducing it here.\n"
}SHA-256 of public snapshot: 72825995e97426eea2fa246366c10d425b534657f9c6044be12f2bd1782d604f