JasonxzWen/harness-hub.

agent-interaction-audit

Load when the user asks for private agent interaction audits from local Codex/Claude Code traces, task profiles, tool-call decisions, collaboration bottlenecks, prompt/rule or automation-log audits, closeout retrospectives, or evidence-backed Skill/project-rule/Eval/SOP/OKF improvements.

agent-reach

Load when a task needs read-only internet research or content retrieval through an already installed Agent Reach CLI; diagnose available backends first, never install, upgrade, authenticate, configure, or copy credentials on the user's behalf.

animation-vocabulary

Load when a user describes a Web animation or motion effect without knowing its name and needs the precise term or close alternatives; use only for naming, not design, implementation, or review.

apple-design

Load when a frontend task needs Apple-platform design guidance or physical, gesture-driven, velocity-aware, interruptible interaction; skip generic visual styling and use review-animations for report-only motion review.

beautiful-feishu-whiteboard

Load when creating or restyling a polished editable Feishu or Lark whiteboard, infographic, diagram, poster, or visual explainer; do not load for generic SVGs, static images, or other whiteboard platforms.

clone-website

Load when the user explicitly asks to clone, reverse-engineer, or rebuild a website they own or are authorized to reproduce; do not load for generic redesign, inspiration, scraping, phishing, impersonation, or copying third-party brands.

codebase-to-course

Load when a user wants a source-backed interactive HTML course that explains how a codebase works; do not load for chat tutoring, repository review, articles, slide decks, or general browser artifacts.

context-guidance

Fixture skill used to represent an additional standard skill context surface.

decision-ui

Load when Codex 即将要求用户在 2-3 个互斥方案中做真实决定、准备询问阻塞性澄清问题或需要确认高影响取舍；将选择转换为宿主原生可点击 UI，并在工具不可用时诚实文本回退。不要用于低风险实现细节、只有一个合理答案的问题、普通信息采集或不需要用户决策的完成汇报。

design-taste-frontend

Load when a task needs anti-template frontend visual direction, design-read calibration, or pre-flight critique for landing pages, portfolios, marketing pages, or redesigns; do not load for dashboards, data tables, multi-step product UI, routine frontend logic, HTML reports, slide decks, or generic code explanation.

effective-interact

Load when agent pauses to report relatively complex information needing Chinese-first clear complex communication, alignment, multi-option choice, status/incident, long-task fact ledgers, implementation plans, reviews, maps, explainers, evidence, risks, validation, handoff; choose plain text/Markdown/visual Markdown/HTML by decision cost; do not load merely because answer is long; skip trivial chat/bundled apps.

package-release-sniffer

Load when tracking newly published package or model-package releases across package registries and release feeds for AI/developer-tool monitoring; do not load for ordinary docs lookup, broad GitHub trend scanning, or implementing package clients.

ponytail

Load when coding work should be deliberately minimal: YAGNI, reuse existing code, prefer stdlib/native/already-installed dependencies, shortest correct diff, no unrequested abstractions, or over-engineering review; do not load for non-coding concise reports, general summaries, or communication artifact density.

product-ui-review

Load when an existing Web product, especially a dashboard, dense-data view, or multi-step app, needs a deep evidence-backed experience review; report findings only, and use design-taste-frontend for marketing-page direction, code-review for source diffs, web-design-guidelines for checklist compliance, or frontend-design for implementation.

quick-learn

Load when a task needs an explicit source-backed learning project, study plan, syllabus, book/technical topic coaching, teach-back, quizzes, or staged review; do not load for routine implementation, one-off facts, or article writing.

review-animations

Load when existing animation or motion code, a motion diff, or a rendered interaction needs an evidence-backed craft review; report findings only and use code-review for general source review.

source-post

Load when turning an external article, blog, release note, interview, or report into a source-backed public post with Chinese fidelity, media references, an effective-interact summary layer, and project-iteration review; do not load for ordinary summaries, full copyrighted reposts, or production site design.

stop-slop

Load when the user asks to draft, edit, or review English prose for AI-writing tells; do not load for code explanation, Chinese output, technical specs, or routine status reports.

to-tickets

Load when an accepted specification must be decomposed into dependency-aware, project-owned implementation slices without creating a new tracker or publishing remote issues by default.

verification

Load when claiming completion requires the repository's actual deterministic build, type, lint, test, diff, smoke, and artifact gates; use diagnose while a failure's root cause is unknown.