btw command

The skill's stated purpose is to provide non-blocking, queued questions with notifications via multiple channels. The code implements a simple in-memory queue and console logging only (no notification channels, no persistence). The required capabilities (none) are appropriate, but the feature claims (multi-channel notifications, durable queue) are not implemented in handler.ts.

SKILL.md emphasizes non-blocking behavior ('agent continues working while waiting') and gives examples that imply background queuing. The implementation's run() awaits waitForAnswer, which blocks until an answer or timeout, so calling agent.run('btw', ...) will block the caller unless invoked without awaiting. SKILL.md also suggests notifying users through channels; the code only logs to console. This mismatch could lead to incorrect integration assumptions (e.g., relying on non-blocking semantics or persistence).

No install spec and only a single small TypeScript handler are included; nothing is downloaded or written during install. This is low-risk from an installation/execution standpoint.

The skill requests no environment variables, no credentials, and the code does not read env vars or config paths. That is proportional to its described local utility.

The skill does not request persistent presence (always:false) and runs locally. However, it stores questions only in memory — pending questions will be lost on process restart — which is not highlighted in the documentation and may be important for real-world use (especially for deployment/security prompts).