84 lines
4.3 KiB
Markdown
84 lines
4.3 KiB
Markdown
---
|
|
name: zhihu-navigate
|
|
description: Use when the user wants to open, switch, or navigate to a Zhihu page, tab, menu, profile area, notification area, message area, or creator area through browser actions.
|
|
version: 0.1.0
|
|
author: sgclaw
|
|
tags:
|
|
- zhihu
|
|
- browser
|
|
- navigation
|
|
---
|
|
|
|
# Zhihu Navigate
|
|
|
|
Open or switch to known Zhihu destinations through browser navigation steps. Use this skill for page routing, menu opening, profile-area switching, and creator-center entry, not for article authoring or hotlist data extraction.
|
|
|
|
## When to Use
|
|
|
|
- The user asks to open a Zhihu page such as home, hot list, notifications, messages, search, creator center, or write article.
|
|
- The user asks to switch to a specific Zhihu tab, section, or profile sub-area.
|
|
- The user asks to open a Zhihu menu such as the avatar menu or notifications menu.
|
|
- The task is browser navigation inside Zhihu and the desired destination is one of the known catalog targets.
|
|
|
|
Do not use this skill for:
|
|
|
|
- writing or publishing Zhihu articles
|
|
- collecting hotlist data or producing reports
|
|
- arbitrary web browsing outside the known Zhihu catalog
|
|
|
|
## Workflow
|
|
|
|
1. Classify the request as one of these destination types:
|
|
- route: direct page URL
|
|
- component: clickable entry or tab
|
|
- flow: multi-step navigation such as open menu, then open a nested destination
|
|
2. Match the requested destination against the known catalog in [routes-and-targets.md](references/routes-and-targets.md).
|
|
3. Prefer the most explicit target name available in the request.
|
|
4. If the request maps to a known ambiguous alias, stop and ask for clarification instead of guessing.
|
|
5. Use semantic selectors first and revalidate brittle selectors using [selector-strategy.md](references/selector-strategy.md) before relying on them.
|
|
6. In the SuperRPA browser host, use the packaged browser-script tool `zhihu-navigate.open_creator_entry` before generic probing when the target is creator center or article entry.
|
|
7. After navigation, verify the destination using URL, domain, or visible text whenever the page exposes a stable signal.
|
|
8. If Zhihu redirects to login, captcha, or verification state, report that block explicitly instead of pretending the target page was reached.
|
|
9. Once the target page is verified, stop exploratory click probing and hand off to the next skill if collection or editing is required.
|
|
|
|
## SuperRPA Interface Contract
|
|
|
|
- Inside the sgClaw browser host, prefer `superrpa_browser` for Zhihu routing and DOM interactions. `browser_action` is only the compatibility alias.
|
|
- Always pass `expected_domain` as the bare hostname only, for example `www.zhihu.com`.
|
|
- All selectors must be valid CSS selectors because the host executes `document.querySelector(...)`.
|
|
- Never use XPath or jQuery-style pseudo-selectors such as `:contains(...)`.
|
|
- Prefer the packaged browser-script tool over ad-hoc probing for creator/article entry.
|
|
- Prefer direct route navigation to known canonical URLs before brittle click chains.
|
|
- Do not cycle through multiple weak selectors when a canonical route is available.
|
|
|
|
## Ambiguity Rules
|
|
|
|
- Treat `关注分栏` as ambiguous until the user says whether they mean home feed following or profile following.
|
|
- Treat `回答排序菜单` as ambiguous until the user says whether they mean question page sorting or answer page sorting.
|
|
- If two targets score equally, ask a direct clarification question instead of falling back to the first match.
|
|
|
|
## Output
|
|
|
|
Return a concise result with:
|
|
|
|
- requested destination
|
|
- resolved target key
|
|
- navigation type: route, component, or flow
|
|
- expected domain
|
|
- final URL when available
|
|
- verification result or uncertainty
|
|
- whether a login/verification redirect blocked the intended destination
|
|
|
|
## References
|
|
|
|
- Use [routes-and-targets.md](references/routes-and-targets.md) to identify the intended target and flow shape.
|
|
- Use [selector-strategy.md](references/selector-strategy.md) when a selector looks weak, overly generic, or DOM-version-dependent.
|
|
- Use the preserved source catalog in `assets/zhihu_navigation_pages.source.json` only when a reference file does not contain enough detail.
|
|
|
|
## Common Mistakes
|
|
|
|
- Confusing page navigation with article-writing actions.
|
|
- Treating menu opening and page opening as the same kind of operation.
|
|
- Ignoring alias collisions and silently picking one target.
|
|
- Trusting a generic selector without checking whether it still maps to the intended control.
|