mycroft
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent for ebook Q&A, but it relies on an external CLI, an OpenAI API key, external embedding/summary calls, and a persistent local book index.
Before installing, confirm that the npm CLI package is the one you intend to trust, use an appropriate OpenAI API key, avoid indexing sensitive ebooks unless external processing is acceptable, and be careful with `--force` deletion commands.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing or running the CLI means trusting code that is not included in these submitted artifacts.
The skill points to an external npm CLI package while the submitted artifact set contains only instructions, so the user is relying on the provenance of that external package.
"package":"@fs/mycroft","bins":["mycroft"]
Install the CLI only from the expected project or package source, and review its package details before use.
Using the skill can consume OpenAI API credits and process user-selected book content through that account.
The skill requires an OpenAI credential for its core embedding and Q&A functions, which is expected but gives the CLI access to the user's OpenAI account and billing.
`book ask` and `book search` require embeddings and an `OPENAI_API_KEY`.
Use a dedicated or restricted API key if possible, monitor usage, and avoid ingesting sensitive material unless OpenAI processing is acceptable.
Book text or derived chunks may be sent to OpenAI for embedding, summary, chat, or Q&A features.
The documentation discloses external provider processing for embeddings and summaries, which is aligned with the purpose but means book-derived content may leave the local machine.
Use `--batch` to run embeddings and summaries via the OpenAI Batch API at 50% cost; results may take up to 24 hours.
Only process books whose content you are comfortable sending to the configured provider, and review provider retention and privacy settings.
Book-derived data may remain available locally across sessions until the user removes it.
The skill intentionally creates a persistent local vector index from ingested books, which can be reused for later search, chat, and Q&A.
Use `mycroft` to ingest EPUBs and ebooks, build a local vector index, and ask questions about a book.
Use the delete command for books you no longer want indexed, and be cautious when indexing private or proprietary ebooks.
A mistaken scripted command or agent action could delete a book entry or its index without asking again.
The documentation includes a no-confirmation deletion mode. It is disclosed and user-directed, but it can remove indexed book data without an interactive prompt.
Delete book: `mycroft book delete <id> --force` ... For scripted runs, avoid interactive flags like `--manual` or omit confirmations with `--force`.
Avoid `--force` unless deletion is explicitly intended, and require confirmation before allowing an agent to run delete commands.