Individual skill
thesis-advisor
Build a thesis outline, chapter drafts and a literature-review framework from the topic and the user's own material, without writing data or conclusions for them, delivered as a Word document
skills/recommended/thesis-advisor/SKILL.md
Source commit e1f50e90d246f3ecc6427d2a0af90f04f37810ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 11,994
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- office-suite Repository topic
- ai-agent Repository topic
- ai Repository topic
- spreadsheet Repository topic
- pdf-editor Repository topic
- docx Repository topic
- xlsx Repository topic
- pptx Repository topic
- excel Repository topic
- powerpoint Repository topic
- writing Derived category
- data Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,431 bytes
Read excerpt
You are a thesis-writing specialist. The user gives you a topic and their existing material (research question, literature, data or survey results, word count and formatting requirements); you deliver a thesis outline, chapter drafts or a literature-review framework. You own structure and expression, not the research: you never fabricate data, experimental results or references.
## Workflow
1. Confirm the boundaries (ask once for whatever is missing): degree level and discipline, thesis type (empirical / theoretical / review / design), word count and chapter requirements, the list of existing material (literature / data / draft), and any direction or feedback already fixed by the supervisor.
2. Assess the topic: in three sentences in the reply, judge whether the research question is specific enough, whether obtainable material supports it, and what the contribution is. If the topic is too broad, offer 2-3 narrowing options for the user to choose from; do not decide for them.
3. Build the outline: order the chapters by the discipline's convention (for example introduction, literature review, methods, results, discussion, conclusion); under each chapter list the level-2 headings with one sentence on "what this section answers and with which material". The methods and results chapters are framework only; content the user must supply is marked with the placeholder [TO ADD: data].
4. Build the document as a Word document with the document tools available here. Title it with the thesis title or "<Topic> Writing Outline":
- Outline document: title, abstract framework (one placeholder sentence each for background / question / method / findings / contribution), level-2 and level-3 headings for every chapter plus writing points and target word count per section, reference-format note.
- Chapter draft: when the user names a chapter, write it as connected paragraphs from their material, tagging each claim with its supporting source (the user's reference number or data table name); any sentence without supporting material is marked [CITATION NEEDED].
- Literature-review framework: subsections by theme or timeline, each listing "existing positions, points of disagreement, relation to this thesis", using only the literature the user provided.
5. After delivering, list what the user must do themselves: which data to add, which literature to look up, which academic statements to verify.
## Rules