V2EX
Browse, search, read, and interact with V2EX — the creative workers' community.
Skill Directory
<SKILL_DIR> is the directory containing this SKILL.md file. Determine it ONCE at the start and reuse it.
Setup (run FIRST — every time, before any operation)
You MUST complete this setup before running any script. Do NOT skip this step.
sig status v2ex 2>&1
Check the JSON output fields configured and valid:
configured: false → run Provider Setup below. Do NOT proceed without completing it.valid: false (but configured: true) → run sig login v2ex, then re-check.valid: true → detect proxy (see below), then execute the user's request.
Provider Setup
- Read
<SKILL_DIR>/references/provider-config.yaml
- Append the provider block to
~/.sig/config.yaml under providers:
- Ask the user: "Do you need a proxy to access this site?" — if yes, add
networkProxy: <url> under the provider in config.yaml
- Run
sig login v2ex (with --network-proxy <url> if proxy was specified)
- Verify: run
sig status v2ex again — must show valid: true before proceeding
Proxy Detection (after provider is valid)
grep -A15 "^\s*v2ex:" ~/.sig/config.yaml | grep networkProxy | awk '{print $2}'
If this outputs a URL, prefix ALL python3 commands with HTTPS_PROXY=<url> HTTP_PROXY=<url>.
If using socks5, convert to socks5h for python (e.g. socks5://... → socks5h://...).
If empty, no proxy needed.
Running Scripts
All scripts require setup to be completed first (see above).
Read operations — use sig run to inject cookie (enables authenticated features):
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_hot.py --cookie "$SIG_V2EX_COOKIE"'
Write operations — require sig run (cookie is mandatory):
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_reply.py --cookie "$SIG_V2EX_COOKIE" --topic-id 12345 --content "Nice post!"'
Env var: SIG_V2EX_COOKIE
On auth error (401/403): run sig login v2ex automatically (no user prompt), then retry.
Scripts Reference
All scripts are in this skill's scripts/ directory. Run via Bash tool.
Read Operations
| Script | Purpose | Auth |
|---|
v2ex_hot.py | Hot topics of the day | Optional |
v2ex_latest.py | Latest topics | Optional |
v2ex_topic.py | Topic detail + replies | Optional |
v2ex_node.py | Node info + topics, list nodes | Optional |
v2ex_member.py | Member profile + topics | Optional |
v2ex_search.py | Full-text search via SOV2EX | None |
v2ex_notifications.py | User notifications | Required |
v2ex_profile.py | Authenticated user profile/balance | Required |
Write Operations
| Script | Purpose | Auth |
|---|
v2ex_create.py | Create a new topic | Required |
v2ex_reply.py | Reply to a topic | Required |
v2ex_thank.py | Thank a topic or reply | Required |
v2ex_favorite.py | Favorite/unfavorite topic or node | Required |
v2ex_follow.py | Follow/unfollow/block/unblock | Required |
v2ex_daily.py | Daily sign-in reward | Required |
v2ex_append.py | Append supplement to own topic | Required |
v2ex_hot.py
--cookie COOKIE V2EX session cookie (optional)
v2ex_latest.py
--cookie COOKIE V2EX session cookie (optional)
v2ex_topic.py
--cookie COOKIE V2EX session cookie (optional)
--id ID Topic ID (required)
--page N Reply page number (default: 1)
v2ex_node.py
--cookie COOKIE V2EX session cookie (optional)
--name NAME Node name (e.g., "python", "apple")
--page N Page number for topic listing (default: 1)
--list-all List all available nodes (flag)
v2ex_member.py
--cookie COOKIE V2EX session cookie (optional)
--username NAME Member username (required)
--include-topics Also fetch member's recent topics (flag)
v2ex_search.py
--query TEXT Search query (required)
--size N Max results (default: 20)
--sort FIELD Sort by: "sumup" (relevance, default) or "created"
--node NAME Filter by node name (optional)
--username NAME Filter by author (optional)
v2ex_notifications.py
--cookie COOKIE V2EX session cookie (required)
--page N Page number (default: 1)
v2ex_profile.py
--cookie COOKIE V2EX session cookie (required)
v2ex_create.py
--cookie COOKIE V2EX session cookie (required)
--node NAME Target node name (required, e.g., "python")
--title TEXT Topic title (required)
--content TEXT Topic body content (required)
--syntax SYNTAX Content syntax: "default" or "markdown" (default: "default")
v2ex_reply.py
--cookie COOKIE V2EX session cookie (required)
--topic-id ID Topic ID to reply to (required)
--content TEXT Reply content (required)
v2ex_thank.py
--cookie COOKIE V2EX session cookie (required)
--type TYPE "topic" or "reply" (required)
--id ID Topic ID or Reply ID (required)
v2ex_favorite.py
--cookie COOKIE V2EX session cookie (required)
--type TYPE "topic" or "node" (required)
--id ID Topic ID or Node ID (required)
--undo Unfavorite instead (flag)
v2ex_follow.py
--cookie COOKIE V2EX session cookie (required)
--action ACTION "follow", "unfollow", "block", or "unblock" (required)
--id ID Member numeric ID (required)
v2ex_daily.py
--cookie COOKIE V2EX session cookie (required)
v2ex_append.py
--cookie COOKIE V2EX session cookie (required)
--topic-id ID Topic ID to append to (required)
--content TEXT Supplement content (required)
Safety
Always show the user the content (title, body, node) and get explicit confirmation before calling v2ex_create.py, v2ex_reply.py, or v2ex_append.py. These actions post publicly and cannot be easily undone.
v2ex_thank.py costs coins and is irreversible — confirm with the user first.
Key Concepts
Nodes — V2EX organizes topics into nodes (like subreddits). Examples: python, apple, jobs, create, programmer, shanghai. Use v2ex_node.py --list-all to see all.
Once token — V2EX uses a CSRF token called once for all write operations. The client extracts it automatically from HTML pages before each mutation.
Topic IDs — Numeric IDs (e.g., 12345). Found in URLs like v2ex.com/t/12345. Get from hot/latest/search results, then use with v2ex_topic.py.
Member IDs vs usernames — Profiles use usernames, but follow/block actions require numeric member IDs. v2ex_member.py returns both.
Daily check-in — V2EX awards coins for daily sign-in. Use v2ex_daily.py to redeem.
Search — Uses the SOV2EX third-party search engine (sov2ex.com) which indexes V2EX content for full-text search.
Error Handling
| Error | Cause | Fix |
|---|
| 403 Forbidden | Session expired / no cookie | Auto-run sig login (no user prompt needed), retry |
| 302 Redirect | Not logged in | Check cookie is valid |
ONCE_NOT_FOUND | Failed to extract CSRF token | Session expired — auto-run sig login, retry |
RATE_LIMITED | Too many requests | Wait and retry |
SEARCH_ERROR | SOV2EX service unavailable | Try again later |
Workflow Examples
Browse hot topics
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_hot.py --cookie "$SIG_V2EX_COOKIE"'
Read a specific topic and its replies
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_topic.py --cookie "$SIG_V2EX_COOKIE" --id 12345 --page 1'
Search for topics
python3 <SKILL_DIR>/scripts/v2ex_search.py --query "Docker 部署" --size 10
Create a new topic
- Show title/body/node to user and get confirmation
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_create.py --cookie "$SIG_V2EX_COOKIE" --node python --title "Question about asyncio" --content "How do I..."'
Reply to a topic
- Read the topic first:
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_topic.py --cookie "$SIG_V2EX_COOKIE" --id 12345'
- Show reply to user and get confirmation
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_reply.py --cookie "$SIG_V2EX_COOKIE" --topic-id 12345 --content "I think you should..."'
Check notifications
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_notifications.py --cookie "$SIG_V2EX_COOKIE"'
Daily check-in
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_daily.py --cookie "$SIG_V2EX_COOKIE"'
Follow a member
- Look up member:
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_member.py --cookie "$SIG_V2EX_COOKIE" --username livid'
- Follow:
sig run v2ex -- bash -c 'python3 <SKILL_DIR>/scripts/v2ex_follow.py --cookie "$SIG_V2EX_COOKIE" --action follow --id 1'