Skip to content
Agentmart
Submit a tool

endly-go-diagnostics

Diagnose stalled Endly Go orchestration with gops stacks, operation events, and targeted state inspection before fixing the underlying code.

Skill by viant

IndexedApache-2.0★ 269
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/viant-endly-go-diagnostics

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Diagnose stalled Endly Go orchestration with gops stacks, operation events, and targeted state inspection before fixing the underlying code.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/endly-go-diagnostics

What's inside

Skill name
endly-go-diagnostics
Description
Diagnose stalled Endly Go orchestration with gops stacks, operation events, and targeted state inspection before fixing the underlying code.
License
Apache-2.0
Instructions
21 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

Start the MCP process with `endly mcp -diagnostics` to enable gops. Identify that
exact Endly PID with gops/process inspection; do not signal unrelated processes.
Use `gops stack <pid>` to save goroutine stacks, then inspect the operation's
executeWorkflow/executeAction stack and the goroutine it is waiting for. If the
state has not progressed, capture a second stack after independent work to distinguish
a stable block from normal I/O. `gops stats` and `gops memstats` can distinguish
resource pressure from a mutex/channel wait. Avoid CPU/heap profiling unless needed.

Correlate the frames with MCP operation events and paused state. A dsunit.prepare
channel send can mean its dataset worker is waiting on database or BigQuery I/O;
inspect the worker before calling it a deadlock. A pending step/next command can
mean the action is still executing: poll debug status and pausedAt before issuing
continue. Never treat an RPC timeout as the operation's terminal status.

Fix the smallest demonstrated cause and add a regression test for observable
behavior. Preserve the asynchronous operation/session model and external test
fixtures. Use cancellation through MCP first, and ensure shutdown uses a bounded
context. Retain concise stack findings and code locations without dumping secrets
or large raw logs into the conversation.

From viant/endly, Apache-2.0.

More from viant/endly

Signals

Stars
269
Forks
39
Open issues
0
Last commit (this folder)
Sep 30, 2026 (28 days ago)
Last release
Oct 21, 2026 (7 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
Repository
github.com/viant/endly
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from viant

Cite this page

endly-go-diagnostics skill. Agent Mart. https://agentmart.dev/skills/viant-endly-go-diagnostics (last updated 2026-10-24)