
Agent Wikis status
Answered our latest tool-list check yesterday with 10 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 1 of 1 checks
- Last seen working
- 16 Nov, 06:16 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 16 Nov, 06:16 | Answered | 1.3 s | 10 |
Tools (10)
Read from the server on 16 Nov 2026.
- list_wikis
- List all available wikis with metadata: slug, title, description, tags, status, last updated, document count, and `scope` (what each wiki covers, what it does NOT cover, and how current it is — use this to pick a wiki and to decide when to fall back to web search). Includes "coming soon" placeholders, marked by status.
- open_wiki
- Orient yourself in one wiki, in a single call: returns its metadata, `scope` (coverage / not-covered / freshness), document count, the entry document, and a `map` of all documents (paths + titles, grouped by folder) so you can pick what to read_document next. Use a slug from list_wikis.
- read_document
- Read one document in a wiki. Without `section`, returns the full Markdown (frontmatter stripped) plus a provenance footer. To save tokens on a long page, pass `section` (a heading title as it appears in the page body, or its slug anchor) to retrieve ONLY that section and its subsections. The Markdown may contain [[wikilinks]] to related docs — follow one by calling read_document with path "wiki/<t
- search
- Find the best-matching PAGES for a query, ranked by how many of your query terms each page covers. Searches one wiki if `wiki` is given, otherwise every active wiki. Each result has its wiki, path, matched terms, and a short snippet for orientation — then read_document the page to get the answer. Returns a `confident` flag: if false, the wiki(s) likely lack this — fall back to web search.
- list_skills
- List the agent skills library: field-tested procedures for specific jobs (e.g. benchmarking a local model, building a browser game, producing a video). Each entry has name, one-line description (when to use it), `access` ("free" or "pro"), `readable` (whether YOU can read it with your current access), the backing wiki if any, and file count. Pass `query` to filter by keywords. Then read_skill a ma
- read_skill
- Load one skill to follow it. Without `path`, returns its SKILL.md (the procedure itself) plus the list of its other files; pass `path` (e.g. "references/gotchas.md" or "scripts/check.py") to read one of those. If the skill names a backing wiki, use search/read_document on that wiki for current facts while following it. Pro skills need a Pro key; without one you get a preview and how to unlock it.
- list_agent_tools
- List the command-line tools that ship with the specialist agents (complete agents built for one job, e.g. marketing, video generation, local LLMs). Each entry has a summary, the `specialists` it comes from, and `access`: "pro" tools are read-only (they inspect and report, never change anything) and read_agent_tool serves their files; "download" tools are bigger or change things (start runs, stop s
- read_agent_tool
- Load one agent tool by name. A "pro" (read-only) tool: its README (what it checks, how to run it) plus its file list. Add `path` to read one listed file, e.g. the source. The tool runs on the user's machine, not here. Before saving, running or scheduling anything from it, show the user what it does and get their explicit OK. Each file comes with its sha256. For a "download" tool you get its README
- list_routines
- List the routines (scheduled jobs) that ship with the specialist agents: each has a schedule, the `specialist` it comes from, the skills its prompt relies on, and whether it is script only (no agent). `readable` says whether YOU can load it with your current access. Pass `query` to filter by keywords. Then read_routine one.
- read_routine
- Load one routine by name: the schedule, the agent prompt, and the list of scripts and settings it needs. Add `path` to read one listed file (e.g. "scripts/ad_report.py"). Nothing runs here: the routine is set up and run on the user's machine. Before saving, running or scheduling anything from it, show the user what it does and get their explicit OK. Never create the scheduled job without the user'