القائمة
Query Syntropic137 observability data; sessions, artifacts, token costs, tool timelines, and system-wide insights
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/syntropic137/syntropic137-claude-plugin --skill syn-insightsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Search, install, and manage Syntropic137 workflow plugins from marketplace registries; browse available workflows, review before installing, manage registry sources
Query Syntropic137 agent sessions, tool timelines, token metrics, cost breakdowns, and interpret observability data; why was a session expensive, why did it fail
Control running Syntropic137 executions; list, pause, resume, cancel, and check status of workflow executions
| name | syn-insights |
| description | Query Syntropic137 observability data; sessions, artifacts, token costs, tool timelines, and system-wide insights |
| argument-hint | <overview|sessions|artifacts|costs|tools|tokens> [args] |
| model | sonnet |
Use this skill when you need to answer two questions: "Why was this execution expensive?" and "Why did this session fail?" These are the questions observability data exists to answer.
Use /syn-insights when you want to: browse sessions and their costs, inspect what artifacts an execution produced, trace which tools a session called and in what order, or check platform-wide cost summaries.
For the conceptual model behind sessions, cost projections, and the two-lane architecture, the observability skill has the full explanation. For controlling a running execution, use /syn-control.
A session = one Claude CLI invocation in one workspace. A 3-phase workflow creates 3 sessions.
syn sessions list # all sessions
syn sessions list --workflow <workflow-id> # filter by workflow
syn sessions list --status running # filter by status
syn sessions list <session-id> # session detail with operations log
API: GET http://localhost:8137/api/v1/sessions (supports ?workflow_id=<id>&status=<status>)
syn artifacts list
syn artifacts list --workflow <workflow-id>
syn artifacts show <artifact-id>
syn artifacts content <artifact-id> --raw
syn costs summary # platform-wide summary
syn costs session <session-id> # cost breakdown for one session
syn costs execution <execution-id> # cost aggregated across all phases
The breakdown includes cost_by_model and cost_by_tool; these tell you whether opus usage or expensive tool calls (like Bash) drove the cost.
The most useful debug view, showing every tool call in order with timing and success/failure:
syn observe tools <session-id>
syn observe tools <session-id> --limit 200
Look for TOOL_BLOCKED entries (the agent was denied a tool) and long duration_ms values (slow file reads, hanging bash commands).
Per-session token breakdown including cache hit/miss:
syn observe tokens <session-id>
Low cache_read_tokens relative to input volume means the agent is re-reading large files every turn, which is expensive and slow.
"This execution cost $12. What happened?"
syn costs execution <id> to find which phase was most expensivesyn costs session <session-id> for the expensive phase: check cost_by_model and cost_by_toolsyn observe tokens <session-id> to check cache hit ratio"The workflow produced no artifacts. What did the agent do?"
syn sessions list --workflow <id> to find the session IDssyn observe tools <session-id> to trace every tool call; look for errors or blocked tools"I want to see all sessions from the last run."
syn sessions list --workflow <workflow-id> lists all sessions in order, most recent first.
Cross-org health + cost summary: syn insights overview
This hits GET /api/v1/organizations/overview and shows total executions, costs, and system health status.
On API errors, run /syn-health. For the full observability model (two-lane architecture, event pipeline, cost model), see the observability skill.