content/skills/academic-skills/paper-interpretation-flow/SKILL.md
Paper workflow: read papers + cast cards in one go. Takes one or more arxiv links, paper URLs, PDFs, or paper names. For each paper, runs ljg-paper (generates org analysis) then ljg-card -l (generates long reading card PNG). Use when user says '论文流', 'paper flow', '读论文并做卡片', '论文卡片', or provides multiple papers wanting both analysis and cards.
npx skillsauth add bahayonghang/my-claude-code-settings paper-interpretation-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
一条命令完成:读论文 → 生成解读 → 铸成卡片。支持多篇并行。
| 参数 | 说明 |
|------|------|
| 无参数 | 对话中已提供的论文链接/文件 |
| -c | 卡片模具改用多卡模式(默认 -l 长图) |
| -i | 卡片模具改用信息图模式 |
从用户消息中提取所有论文来源(arxiv URL、PDF 路径、论文名称等)。
对每篇论文,启动一个 Agent subagent,每个 subagent 按顺序执行两步:
步骤 A — 读论文(paper-interpretation):
调用 Skill tool 执行 paper-interpretation,传入该论文的来源。等待完成,获得生成的 org 文件路径。
步骤 B — 铸卡片(card):
读取步骤 A 生成的 org 文件,调用 Skill tool 执行 card(默认 -l,或按用户指定的模具参数),以 org 文件内容为输入。等待完成,获得 PNG 文件路径。
所有论文处理完成后,汇总输出:
════ 论文流完成 ═══════════════════════
📄 {论文标题1}
📝 解读: {org 文件路径}
🖼️ 卡片: {PNG 文件路径}
📄 {论文标题2}
📝 解读: {org 文件路径}
🖼️ 卡片: {PNG 文件路径}
...
development
Implement safe, behavior-preserving code refactors after inspecting the existing project. Use when the user asks to refactor code, split large files or modules, extract functions or methods, reduce duplicated logic, rename confusing classes/functions/variables, improve code comments, remove unused or dead code, or says 重构代码, 拆分模块, 提取方法, 减少重复代码, 优化命名, 优化注释, 删除未调用代码. For broad refactor requests, plan safe slices and wait for approval; for narrow scoped requests, directly implement the smallest verifiable slice.
development
Use only when the user explicitly asks for swarm, subagents, parallel agents, dynamic workflow, multi-agent orchestration, 多智能体编排, or when the task truly needs coordinated research plus implementation plus review plus verification packets. Do not use for ordinary code review, planning-only work, single-line bugfixes, routine audits, or migrations unless orchestration is requested or at least two independent workflow dimensions are present.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
development
Plan-first brainstorming workflow that turns an idea into an approved Markdown implementation plan by default. Use when the user wants to brainstorm, design, scope, or plan a feature/spec before implementation. Spark explores project context, asks only blocking questions, writes the plan under the project root's .plannings/YYYY-MM-DD-feature-slug.md path, self-reviews it, and waits for user approval. Create an HTML or visual plan/spec only when the user explicitly asks for HTML, browser-viewable, or visual output; save the paired .html beside the Markdown plan.