From mcpserver-grok
Synchronize MCP Server session logs for Grok when asked to "sync logs", "repair MCP session logs", or "logging summary".
How this skill is triggered — by the user, by Claude, or both
Slash command
/mcpserver-grok:sync-logsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the local Grok bridge path: `lib/mcp.claude.status.sh`, `lib/repl-invoke.sh` or `lib/repl-invoke.ps1`, `lib/marker-resolver.*`, and `lib/final-response.sh`. Do not use raw REST for normal MCP mutations.
Use the local Grok bridge path: lib/mcp.claude.status.sh, lib/repl-invoke.sh or lib/repl-invoke.ps1, lib/marker-resolver.*, and lib/final-response.sh. Do not use raw REST for normal MCP mutations.
Run a status check first. Ensure session/turn handling is open with workflow.sessionlog.openSession or workflow.sessionlog.beginTurn, append reasoning with workflow.sessionlog.appendDialog, and append durable actions with workflow.sessionlog.appendActions.
Discover background sessions from local cache/session state before closing. Report a compact factual summary with session ids, turn ids, actions, commits, validation, defects, and blockers.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub sharpninja/mcpserver-grok-plugin --plugin mcpserver-grok