القائمة
用于毕业论文或毕业设计写作优化。当用户需要修改中文摘要、英文 abstract、章节开头、小节引入段或章节过渡语，并希望提升逻辑性、承接关系、信息顺序与学术表达时使用。
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Evaluates a preliminary research idea against a five-dimension framework (Higher, Faster, Stronger, Cheaper, Broader) plus idea-lifecycle and student-capability matching, paradigm-shift probing, and a fatal-flaws audit. Returns a reviewer-style verdict. Use when the user has a draft research idea and asks whether it is worth pursuing, asks to 'evaluate this idea', 'score this idea', 'assess feasibility', 'novelty check', 'is this a good research direction', or before committing to a paper scope.
Drafts a 6-paragraph Introduction outline for a technical paper from a structured Flowchart: background and running example, existing limitations, problem essence and goal, key challenges, solution overview, contributions. Positions the paper as Technique or New Problem/Setting and aligns contributions with challenges. Use when the user asks to 'draft the Introduction', 'outline the Introduction', 'intro logic needs clarifying', 'help structure the paper story', or before writing any Introduction prose.
Runs a pre-submission review of a technical paper across five dimensions: macro logic, writing details, English grammar, LaTeX formatting, and figure quality. Uses a reviewer-style severity taxonomy (CRITICAL / MAJOR / MINOR) and flags banned AI-tone vocabulary and em-dash misuse. Use when the user asks to 'review this paper', 'audit before submission', 'check the draft', 'find issues', 'proofread', or within one week of a submission deadline.
用 Laurent Vanbever 近年论文中反复出现的研究推理方式做论文助手工作。适用于 networking、routing、measurement、systems、security、network-ML、benchmark、observability 等任务中的 idea 验证、gap analysis、问题重构、证据审计、reviewer 风险预判与最小验证设计。重点不是模仿文风，而是按该学者的对象构造、证据许可、异议排序和拒绝模式来分析。
Analyze networking, routing, measurement, systems, security, and network-ML tasks using Laurent Vanbever's recurring research reasoning. Use when the task needs tight scoping, proxy skepticism, interpretable intermediate representations, operator-facing evaluation, benchmark critique, or explicit refusal of category errors rather than surface-level stylistic imitation.
Guides AI-assisted research across three sub-flows, Vibe Coding, Vibe Figure, and Vibe Writing, with behavioural rules that keep the user in charge of academic judgment while delegating mechanical work to AI. Recommends the right tool (Cursor, Claude Code, Codex, Figma, Gemini) for the current stage. Use when the user asks 'how to use AI for research', 'Vibe Coding tips', 'AI-assisted writing workflow', 'which AI tool for this', or starts an AI-assisted work session.
| name | thesis-abstract-and-chapter-opening-editor |
| description | 用于毕业论文或毕业设计写作优化。当用户需要修改中文摘要、英文 abstract、章节开头、小节引入段或章节过渡语，并希望提升逻辑性、承接关系、信息顺序与学术表达时使用。 |
你的任务不是只做表面润色，而是优先修复文本的逻辑链条，让段落更像正式论文而不是学生作业式说明。
当用户要求你处理以下内容时，使用本技能：
abstract先判断用户给的是哪一类内容：
abstract不同类型使用不同的逻辑骨架。
优先检查这些常见问题：
abstract 逐句直译，主谓不稳，信息重复优先使用下面的顺序：
如果用户原文缺少结果，不要虚构结果，可以保守写成“完成了实现与验证”或“为后续部署提供依据”。
优先使用下面的顺序：
章节开头必须让读者知道“为什么现在讲这个”“这一章会讲什么”。
改写时强制执行：
默认按以下顺序输出：
用 2 到 4 条指出当前文本最影响阅读的结构问题。
直接给出可替换的完整版本。
简要说明你如何补足了承接、问题定义、章节目标或信息顺序。
如果用户明确说“直接帮我改”，可以省略长分析，先给改写版本，再补一句简短说明。
abstract，避免中式长句和机械直译