ワンクリックでManusで任意のスキルを実行

ctx-doctor

スター1

フォーク0

更新日2026年4月10日 01:35

Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

scottconverse

scottconverse/context-mode

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Context Mode Doctor

Run diagnostics and display results directly in the conversation.

Instructions

Call the ctx_doctor MCP tool directly. It runs all checks server-side and returns a markdown checklist.
Display the results verbatim — they are already formatted as a checklist with [x] PASS, [ ] FAIL, [-] WARN.
Fallback (only if MCP tool call fails): The MCP server likely isn't running. Derive the plugin root from this skill's base directory (go up 2 levels — remove /skills/ctx-doctor), then run the installer to repair:
```
node "<PLUGIN_ROOT>/install.js"
```
Display the install output to the user. If all 7 steps pass and the server probe shows 9/9 tools, tell the user to run /reload-plugins (CLI) or start a new conversation (Cowork/desktop) to load the repaired plugin. If the install itself fails, show the error — it will say what went wrong and how to fix it.

このリポジトリの他の Skills

同じリポジトリ

context-mode

scottconverse/context-mode

Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines. Subagent routing is handled automatically via PreToolUse hook.

2026-04-111

ctx-stats

scottconverse/context-mode

Show how much context window context-mode saved this session. Displays token consumption, context savings ratio, and per-tool breakdown. Read-only — shows stats only, no reset capability. To wipe the knowledge base entirely, use ctx_purge instead. Trigger: /context-mode:ctx-stats

2026-04-111

ctx-purge

scottconverse/context-mode

Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone. Trigger: /context-mode:ctx-purge

2026-04-101

name	ctx-doctor
description	Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor
user-invocable	true

Context Mode Doctor

Run diagnostics and display results directly in the conversation.

Instructions

Call the ctx_doctor MCP tool directly. It runs all checks server-side and returns a markdown checklist.
Display the results verbatim — they are already formatted as a checklist with [x] PASS, [ ] FAIL, [-] WARN.
Fallback (only if MCP tool call fails): The MCP server likely isn't running. Derive the plugin root from this skill's base directory (go up 2 levels — remove /skills/ctx-doctor), then run the installer to repair:
```
node "<PLUGIN_ROOT>/install.js"
```
Display the install output to the user. If all 7 steps pass and the server probe shows 9/9 tools, tell the user to run /reload-plugins (CLI) or start a new conversation (Cowork/desktop) to load the repaired plugin. If the install itself fails, show the error — it will say what went wrong and how to fix it.