learn 是做什么的？
运行一个六阶段研究流程，将不熟悉的领域、源码包或收集的材料转化为可直接发布的输出。适用于用户以任何语言请求研究、学习、深度探索、编译资料、综合不熟悉材料或将源码包转化为连贯参考文档的场景。不适用于快速查询或单文件阅读。
运行一个六阶段研究流程，将不熟悉的领域、源码包或收集的材料转化为可直接发布的输出。适用于用户以任何语言请求研究、学习、深度探索、编译资料、综合不熟悉材料或将源码包转化为连贯参考文档的场景。不适用于快速查询或单文件阅读。
该技能实现了一个结构化的六阶段研究流程，旨在帮助开发者和AI代理用户系统性地处理不熟悉的领域、源码库或收集的材料。它通过六个明确的阶段（如理解需求、收集信息、分析、综合、撰写和格式化）将原始输入转化为高质量、可发布的参考文档或报告。对于需要深入研究复杂主题、从源码包快速生成文档或综合多个来源信息的用户特别有用。该技能支持多种平台和工具，包括Claude Code、Cursor和Codex等，并基于其SKILL.md文档中的原则工作，确保输出一致且专业。适用于研究、学习、深度探索和材料编译等任务，但不应作为快速查询或单文件读取的替代方案。
npx skills add https://github.com/tw93/waza/tree/main/skills/learnInstalled? Explore more 研究与数据分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
运行一个六阶段研究流程，将不熟悉的领域、源码包或收集的材料转化为可直接发布的输出。适用于用户以任何语言请求研究、学习、深度探索、编译资料、综合不熟悉材料或将源码包转化为连贯参考文档的场景。不适用于快速查询或单文件阅读。
This repo contains 7 individual skills — each has its own dedicated page.
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask review/看看代码/合并前/看看issue/PR/release/push or to implement an approved plan, with safety gates for dirty and untracked worktrees. Not for exploring ideas, debugging root causes, or prose review.
Produces distinctive, production-grade UI for pages, components, visual interfaces, typography, and screenshot-driven polish. Use when users ask in any language for UI, page, component, frontend, typography, screenshot-grounded visual polish, or complaints that a screen looks unclear, ugly, inconsistent, or visually wrong. Not for backend logic or data pipelines.
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask 检查claude/检查codex/检查pi/配置检查/健康度 or report agents ignoring instructions, missing validation, or code becoming hard to maintain. Not for debugging code or reviewing PRs.
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask 看这个链接/读一下/read this/check this URL. Not for local text files already in the repo.
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.
Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, polish release notes, remove AI-like wording, or prepare launch and social copy. Not for code comments, commit messages, or inline docs.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.