host-test
Inspect host-test capture logs for hooks, MCP, conversation, session, or lineage. Use when debugging what a host sent this probe.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- name
- host-test
- description
- Inspect host-test capture logs for hooks, MCP, conversation, session, or lineage. Use when debugging what a host sent this probe.
03 SKILL.md 正文
Host test probe
This plugin records every hook event the host dispatches to it, plus every call to its own MCP servers, into one NDJSON log and a durable state summary. Nothing it records is sent anywhere; the log stays on this machine.
Inspect or probe
For a log or identity question, call the host-test MCP server's dump tool
and report the relevant observed ids and log path. Existing records may answer
the question without a live probe. The dump call itself is recorded;
distinguish absent evidence from an unsupported host capability.
For a requested live probe, generate only the evidence needed:
- Run a harmless shell command such as
pwdfor tool-hook evidence. - Create a small scratch file for file-edit-hook evidence.
- If
host-test-rawexposesprobe, call it with your role (rootorsubagent) as the note. - For parent/subagent lineage, ask a subagent to run the shell and available probe calls, then dump the resulting records. A log-only request does not require spawning an agent.
Dump the resulting records and report the relevant ids verbatim, without editing the log. Do not include unrelated payloads in the response.
Never delete or rewrite the log by hand; the reset tool is the only way to
clear it, and only when the user asks for a fresh probe.
04 同仓库更多 Skills
vendored-assets
Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
test-development
Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
performance-analysis
Performance analysis. Use for runtime throughput or latency benchmarks, TypeScript compiler cost, performance regressions, comparison harnesses, or thresholds.
package-development
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
migration-guidance
Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration/v3-to-v4.md.
jsdocs
Public API JSDoc. Use when authoring or reviewing Effect API documentation, refining a module's documentation, or fixing documentation related diagnostics.