doko-page-reader
Read and extract content from web pages through a locally connected Chrome browser using Dokobot local bridge only. Use when an agent needs JavaScript-rendered pages, logged-in browser content, or pages that block headless scrapers and should be handled entirely through the user's local browser.
What this skill does
# Dokobot Local
Use Dokobot only through the local bridge and the user's Chrome session.
## Prerequisites
- Ensure `dokobot` CLI is installed.
- Ensure Chrome is open with the Dokobot extension enabled.
- Ensure the local bridge is installed with `dokobot install-bridge`.
- Prefer local browser reading when the page needs JavaScript, an authenticated browser session, or a real browser to bypass bot friction.
## Core workflow
1. Read the page in local mode:
```bash
dokobot read '<URL>' --local
```
2. If the read fails because no local browser is available, tell the user to open Chrome, enable the Dokobot extension, and verify the local bridge is installed.
3. For long pages, collect more screens or extend timeout:
```bash
dokobot read '<URL>' --local --screens 5 --timeout 120
```
4. When the response includes a `sessionId` and more scrolling is needed, continue the same session:
```bash
dokobot read '<URL>' --local --session-id <SESSION_ID> --screens 5
```
5. Close the session when finished:
```bash
dokobot doko close <SESSION_ID> --local
```
## Commands
### Read a page
Use:
```bash
dokobot read '<URL>' --local [--screens N] [--timeout S] [--format text|chunks] [--reuse-tab]
```
Notes:
- Always include `--local`.
- Use `--screens N` to scroll and capture more content.
- Use `--timeout S` for slow pages.
- Use `--format chunks` only when segmented content is needed.
- Use `--reuse-tab` to avoid opening a new tab for the same URL.
Default text response shape:
```typescript
{
text?: string
sessionId: string
canContinue: unknown
}
```
Chunked response shape:
```typescript
{
text?: string
chunks: Array<{
id: string
sourceIds: Array<string>
text: string
bounds: [number, number, number, number]
zIndex?: number
containerId?: string
}>
sessionId: string
canContinue: unknown
}
```
## Operating rules
- Treat this skill as local-only.
- Keep the command surface minimal: use only `read --local` and `doko close --local`.
- Analyze and summarize content after receiving the raw page text; keep Dokobot focused on extraction.
- Close sessions explicitly when you are done.
- Keep concurrent reads modest; up to 5 parallel reads is a reasonable ceiling.
## Troubleshooting
- `No registered devices.` or similar local-connection failures: Ask the user to open Chrome, enable the Dokobot extension, and confirm the local bridge is installed.
- `503`: Treat it as no local extension/device available and check the local setup.
- `504`: Retry with a larger timeout or fewer screens.
- `422`: Treat it as a cancelled or failed local read and retry if appropriate.
## Security
- Keep usage local to the user's browser session.
- Treat `read` as read-only extraction.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.