tw93

Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.

Produces distinctive production UI and screenshot-grounded visual polish. Use when building or restyling pages, components, or typography. Not for backend logic or data pipelines.

Rewrites and polishes Chinese or English prose, technical instructions, and product copy. Use when drafting, editing, localizing, or cutting AI tone. Not for code comments or commit messages.

Fetches URLs and PDFs, then summarizes or returns clean Markdown; can also search the web through DeepSeek when built-in search is thin. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.

Audits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.

Turns rough ideas into approved, decision-complete plans before coding. Use when planning architecture, judging whether to build, or writing a handoff. Not for bug fixes or small edits.

Runs a six-phase research workflow from source bundle to publish-ready output. Use when researching an unfamiliar domain or compiling materials into one reference. Not for quick lookups or single-file reads.

Finds root cause before any fix. Use when something errors, crashes, regresses, or used to work. Not for code review or new features.

Use when the user wants Vela to see the orders their posts bring in, when get_today suggests checking the purchase tracking, or when get_site_analytics shows that GA4 has no purchase events; adds the GA4 purchase, begin_checkout and sign_up events to the…

Use when the user wants to reply or post in a community whose rule card (playbook) forbids AI-generated text, such as Hacker News; gives only facts and links, never sentences to post, and checks the text the user wrote themselves.

Use in the warm-up stage when the user wants to help in community discussions and build account standing without promoting their product; picks discussion and pain-point opportunities and drafts replies that follow the community's rule card (playbook); routes…

Use when the user wants to write launch posts by following the project's launch plan, one step at a time; drafts each post against the step's rule card (playbook), leaves steps without a rule card to the user, and routes to a different skill when the rule…

Use when the user wants to reply to a specific community post, thread, or opportunity with a draft that follows the community's rule card (playbook); routes to a different skill when the applicable rule card forbids AI-generated text.

Use when get_project lists a source with agent_scan true in its sources, which means Vela's server can no longer fetch that source (currently only V2EX), or when the user explicitly asks for an agent scan of V2EX; browses the project's boards read-only with…

Use when the user wants a second pass over newly listed opportunities in the opportunity radar; corrects tags the automatic rules got wrong and skips opportunities that do not need a reply.

Mole CLI release runbook for distribution channels, pre-flight checks, capital-V tags, artifacts, and curated-note handoff. Use when assessing or executing a Mole release. Not for release-note copy alone or ordinary code review.

Mole incident catalog for cleanup safety, bounded probes, cancellation, dry-run parity, and actionable gates. Use for a Mole safety-sensitive diff; not for docs, release notes, or generic review.

Publish curated release notes for an existing Mole `V<version>` tag, including bilingual format, `gh release edit`, contributor thanks, and reactions. Use only when explicitly asked to edit or publish Mole release notes. Not for release readiness, tagging, or…

Audit both Mole CLI branches for safety, correctness, performance and stale guidance, then land authorized fixes. Use for weekly or whole-CLI reviews. Not for a single defect or individual PR review.

Drive the Mole CLI (`mo`) on macOS or Windows: find what uses disk space, preview and run cleanup, uninstall apps, and read system health and cleanup history. Use before running any `mo` command. Not for editing Mole source code.

Prepare, validate, and publish a Pake release once the maintainer asks for one in the current turn. Not for version bumps without release intent.

Package a website or local web build as a desktop app with Pake. Use for packaging, CLI options, icons, bundle identifiers, or WebView proxy setup. Not for unrelated Tauri development or uninstalling apps.

Whole-repo audit of MiaoYan across five dimensions (stale rules and dead code, performance, broken behaviour, editing experience, preview experience), every finding refuted once before it is reported, then the approved fixes landed. Use for the periodic check…

Create, edit, review, organize, and present content for MiaoYan. Use when a user asks an agent to work with MiaoYan notes, MiaoYan Markdown, wikilinks and backlinks, math, Mermaid, PlantUML, Markmap, local attachments, PPT mode, or the miao CLI, including…

Run the Kaku macOS release flow end-to-end: preflight, build, notarize, tag, upload to GitHub Releases, dispatch the Homebrew tap, or publish the rolling Nightly preview package. Source of truth is scripts/release.sh and scripts/nightly.sh; this skill records…

Proactively sweep a Kaku area for latent defects and UX traps before users report them, using this repo's own fix history and multi-entry-point archetypes, and confirm every finding with a probe run this turn.

Read issues of 潮流周刊 (Tw93 Weekly), a Chinese-language weekly newsletter of developer tools, open source projects, engineering notes and design, with English translations. Use when a task asks what a specific issue or week covered, which tools Tw93…

Publish one Weekly issue end to end: move the Chinese draft from the MiaoYan iCloud folder into the repo, write the English twin, convert the cover, commit, react to the issue's GitHub Discussion, and fill in the Telegram channel post for the maintainer to…

Typeset professional documents with Kami templates: resumes, one-pagers, white papers, letters, portfolios, slide decks, and social media cards. Use when asked to 做 PDF / 排版 / 简历 / 一页纸 / PPT / slides / 小红书配图, or to create a Kami landing page. Not for auditing…

Use this skill for GitHub issue, PR, and release operations for tw93.github.io blog via gh CLI.