القائمة
Control running Syntropic137 executions; list, pause, resume, cancel, and check status of workflow executions
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/syntropic137/syntropic137-claude-plugin --skill syn-controlيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
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
Query Syntropic137 observability data; sessions, artifacts, token costs, tool timelines, and system-wide insights
عرض SKILL.md
| name | syn-control |
| description | Control running Syntropic137 executions; list, pause, resume, cancel, and check status of workflow executions |
| argument-hint | <list|status|pause|resume|cancel> [execution-id] [args] |
| model | sonnet |
Use this skill when you need to monitor or intervene in a running workflow execution. Check the execution status before taking any control action: the state tells you exactly what actions are available.
Use /syn-control when you want to: see what executions are running, pause an execution to review intermediate results, inject corrective context, resume after review, or cancel an execution that's going wrong.
For diagnosing a failed execution in depth, the execution-control skill has the full troubleshooting workflow. For understanding costs from a session, use /syn-insights.
Every execution is in one of these states. Actions are only valid in the matching state:
RUNNING → pause → PAUSED → resume → RUNNING
RUNNING → cancel → CANCELLED
PAUSED → cancel → CANCELLED
NOT_STARTED, COMPLETED, FAILED, INTERRUPTED are terminal or pre-start states; no control actions apply.
syn execution list # all executions
syn execution list --status running # filter: running, paused, failed, completed
syn control status <execution-id> # detailed phase breakdown
syn control pause <execution-id>
syn control pause <execution-id> --reason "reviewing phase 2 output"
syn control resume <execution-id>
syn control cancel <execution-id> --reason "wrong workflow"
API fallback (if syn CLI not available):
curl http://localhost:8137/api/v1/executions
curl http://localhost:8137/api/v1/executions?status=running
"I want to check what's running right now."
syn execution list --status running shows execution IDs, workflow names, and start times.
"A workflow is analyzing the wrong area and I want to redirect it without restarting."
syn control pause <id> (waits for the current tool call to finish)curl -X POST http://localhost:8137/api/v1/executions/<id>/inject -d '{"message": "Focus only on the auth module", "role": "user"}'syn control resume <id>"An execution has been running for 2 hours and looks stuck."
syn control status <id> to identify which phase is stuck/syn-insights tools <session-id> to check if a tool is hangingsyn control cancel <id> --reason "timeout investigation"If you don't have the ID:
syn execution list for recent executions with IDs/syn-insights sessions (sessions map 1:1 to execution phases)On API errors, run /syn-health. If syn CLI is not found: npx @syntropic137/setup cli. For deep troubleshooting of failed executions, see the execution-control skill.