菜单
In-browser annotation overlay for HTML, Markdown, and plain-text documents. Use when a user wants to annotate a document, run a structured review pass with severities (typo / edit / rewrite), or apply review comments back into source files via Claude Code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Compute Claude Code token usage by model for any date range from local session transcripts. Use this whenever the user asks how many tokens they used, their Claude Code / Claude subscription usage, usage for a month or week or day, a "usage report", per-model token breakdown, or "how much did I spend/use" over some period — including phrasings like "first week of June", "last 7 days", "June 2026", or "yesterday". This is the right tool on the subscription plan, where console.anthropic.com does NOT show usage. Trigger even when the user just names a period and the word "usage" without saying "tokens".
WalkInto.in virtual tour platform and helpdesk — authenticate, view profile, manage 360 tours, search the knowledge base, and run the support ticket lifecycle. Use this skill whenever the user mentions 'walkinto', a WalkInto account, virtual/360 tours, panorama uploads, tour analytics, OR the WalkInto helpdesk: support tickets, customer questions, knowledge-base/KB articles, replying to or triaging tickets, ticket status/priority/tags, or 'who am I on walkinto'.
Evaluate whether the lean-ctx MCP is saving more context tokens than it costs, for the current project, using that project's Claude Code session transcripts. Measures ctx_read with a per-call counterfactual vs native Read, compares ctx_shell against native Bash observationally, nets out the per-session instruction+schema tax, and reports a token ledger. Use when asked to eval lean-ctx, measure context-compression savings, audit token usage of an MCP, or decide if lean-ctx earns its seat.
Inspect a project and recommend developer tooling (LSP, AST, test runners, debuggers, linters) that would make Claude Code most effective. Provides exact install commands and a verify mode to confirm each tool works.
Use when a model emits multiple tool calls in a single turn and the harness must execute them in parallel safely, or when subagents/forks run concurrently and share state. Apply when designing the concurrency model for tool dispatch. Covers parallel tool execution, ordering guarantees, cancellation propagation, race detection on shared resources (filesystem, db), partial-failure semantics, and result aggregation.
Use when an agent harness needs user- or admin-configurable interception points — before/after tool calls, on prompt submit, on stop, on session start. Apply when designing the event/hook architecture that lets operators inject policy, logging, or transformation without modifying core harness code. Covers event taxonomy, blocking vs non-blocking hooks, hook contract (stdin/stdout/exit-code), failure modes, and security implications.
| name | doc-review |
| description | In-browser annotation overlay for HTML, Markdown, and plain-text documents. Use when a user wants to annotate a document, run a structured review pass with severities (typo / edit / rewrite), or apply review comments back into source files via Claude Code. |
This skill is a delegator. When invoked, immediately route to the right slash command based on user intent:
@README.md or a path to .html / .md /
.markdown / .txt / .rst) AND user wants to start or resume an
annotation session → invoke /doc-review:review-doc <file> (pass through
any --port N)..review.json →
invoke /doc-review:apply-review [<json-path>]./doc-review:review-doc-stop./doc-review:apply-review-tick manually.Do NOT print the documentation below as the response. Print at most a one-line confirmation of what command you are routing to, then invoke it.
Workflow summary:
typo, edit, or rewrite./loop tick command, picks it up within ~60 seconds and
edits the source file in place.Commands:
/doc-review:review-doc <file> [--port N]/doc-review:review-doc-stop/doc-review:apply-review [<path-to-review.json>]/doc-review:apply-review-tick --port <N> --session-id <id> (loop-only)Storage layout:
<project-root>/.doc-review/<slug>.review.json,
.../<slug>.queue.json, .../.servers/<slug>.json.$HOME/.cache/doc-review/sessions/<session_id>.json.Project root detected by walking up from the doc for .git/, .doc-review/,
package.json, pyproject.toml, Cargo.toml, go.mod, .hg/, or .svn/.
Override with --project-root.