Slima

List the books in your Slima library. Results are paginated; if the response says more books exist, call again with the next `page` before concluding a book is not there.

Editorial comment threads on this book, open and resolved. Read these before starting work on a book you have been handed — they are where an editor has already said what is wrong, and producing an independent list without reading them usually contradicts a decision someone already made.

List the available Slima guides: titles and one-line summaries of when to load each. Guides teach how to operate Slima — file structure, version control, team knowledge bases, the relationship-map format. Load one with `load_guide` when you are about to do the thing it covers.

The author's margin notes on this book — book-level and chapter-level, including foreshadowing pairs.

List available virtual reader personas for beta reading feedback

What the team has established over time: recurring characters, naming conventions, continuity spanning books, decisions already argued through. Treat these as settled. If one contradicts a book's text, say so rather than picking a side.

The team's coaching rules — its house style — each marked mandatory or advisory. Read these BEFORE writing for a team book, not after a draft is rejected. Mandatory rules are not suggestions: prose that ignores one gets re-edited by a person, which is worse than not writing it.

The team's own writing procedures. Some are marked `confidential: true` and come back WITHOUT a source path; their file contents are withheld from this connection. That is deliberate, and it does not stop the skill working — the server applies it on the team's behalf. Do not try to reconstruct one, reproduce it verbatim, or reach its contents by another route: those routes are closed and audited. Read the `team-knowledge-base` guide before working in a team knowledge base.

List the teams this account belongs to — publishers, studios, writing groups. A team book carries house rules and shared knowledge that change how you should write for it. If a book belongs to a team, read `list_team_rules` before writing.

List Slima's writing skills — the craft procedures the in-app coach follows for tasks like developing a character, revising a scene, or diagnosing pacing. Use these when the task is about the WRITING. Use `list_guides` when the task is about operating Slima.

Load one Slima guide in full. Read `book-structure` before creating files, `version-control-basics` before a large rewrite, `team-knowledge-base` when working in a publisher's team, `beta-reader` before spending the author's credits on a report. `list_guides` has the current set.

Load one writing skill in full — a step-by-step procedure plus the questions a coach would ask. Follow it rather than summarising it at the author.

Read the content of any file in a book by its path. For `.map` relationship graphs, prefer `view_relationship_map` — this tool returns their raw JSON (node ids and pixel coordinates), which is hard to reason about.

Reopen a comment thread that was resolved but should not have been.

Mark a comment thread addressed. Say what you did when you resolve one. A silent resolve tells the editor nothing about whether you understood the note.

Search for content across all files in a book. **Script Studio behavior:** By default, structured files (`*.character`, `*.scene`, `*.storyline`, `*.note`, `*.location`, and `*.json` under `.script_studio/`) are **excluded** from search results — their raw JSON is noisy and not useful for full-text search. Pass `include_structured: true` to search those files too. Writing Studio books are unaffected by this filter.

Find passages by MEANING rather than by the words used. `search_content` finds the word an author typed; this finds the passage they meant — "where does the mother's resentment surface?" returns the scene even when neither word appears in it. On a team knowledge base it is the difference between browsing and asking. Costs a small embedding charge, unlike literal search. Returns §N paragraph anchors so you can quote them back precisely.

See a `.map` character-relationship graph as a picture plus a readable summary. Use this instead of `read_file` for `.map` files: their raw JSON is node ids and pixel coordinates. The summary lists every character, every relationship ("A —childhood friends→ B") and any faction groups, so it is useful even in clients that do not display images. To change one, use `update_relationship_map` (one field at a time). A `.map` is the relationship graph (關係圖), not a geographic map — that is `.geomap`.

Description is built at runtime.