agentleFS
MsNanMsNan/bishe-doc-skills/skills/thesis-writing/SKILL.md

thesis-writing

Skill0 starsChanged 21 days agoMITView on GitHub

计算机类本科毕业论文写作规范(章节结构、摘要与关键词、图表公式编号、参考文献 GB/T 7714-2015 著录格式、降低重复率的正确做法)。写或修改论文正文、摘要、参考文献时使用。

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. santifs/thesis-writing-skill★ 33same name
    2. Paloma966/dsh-paper★ 7same name
    3. kinhluan/skills★ 6same name
    4. ArghyaSarkar/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

Files
SKILL.md

论文写作规范

常见章节结构(以学校模板为准)

摘要/Abstract → 1 绪论(背景意义、现状、主要工作、论文结构)→ 2 相关技术 → 3 需求分析 → 4 系统设计 → 5 系统实现 → 6 系统测试 → 7 总结与展望 → 参考文献 → 致谢 → 附录。

摘要

  • 一段 300–500 字:做了什么系统 → 用了什么技术 → 实现了哪些功能 → 测试结果/效果。不写背景大道理,不写「本文首次」。
  • 关键词 3–5 个,分号分隔;英文摘要与中文对应,不要逐字机翻,用一般现在时/过去时描述。

写法

  • 每章开头一句说明本章内容,结尾一句小结或过渡。
  • 「相关技术」章只写本系统用到的技术及用在哪里,不要复制百科。
  • 图:图号图名在图下方(图 3-1);表:表号表名在表上方,三线表;公式右侧编号(3-1)。图表必须在正文中先引用再出现。
  • 术语前后一致:同一个东西不要一会儿叫「用户」一会儿叫「会员」。

参考文献(GB/T 7714-2015,顺序编码制)

正文按出现顺序标注上标 [1]。常用类型标识:期刊 [J]、专著 [M]、学位论文 [D]、会议 [C]、标准 [S]、电子资源 [EB/OL]。作者超过 3 位写前 3 位加「, 等」(英文加 ", et al.")。示例格式:

[1] 作者A, 作者B. 题名[J]. 刊名, 年, 卷(期): 起止页码.
[2] 作者. 书名[M]. 版本(第1版不写). 出版地: 出版者, 年: 页码.
[3] 作者. 题名[D]. 保存地: 保存单位, 年.
[4] 主要责任者. 题名[EB/OL]. (发布日期)[引用日期]. 网址.

只整理用户提供或能核实的文献,绝不编造作者、刊名、页码。 格式拿不准时让用户用知网/百度学术的「引用 → GB/T 7714」导出核对。

关于重复率

  • 正确做法:用自己的系统、自己的数据、自己的截图和测试结果来写;引用的内容标注出处;技术介绍用自己的话概括。
  • 不做:同义词替换、打乱语序、插入隐藏字符等「降重技巧」——这类做法可能违反学术规范。
  • 提醒用户遵守学校关于 AI 辅助写作的规定,最终文字由本人审阅改写。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.