Run this helper free — no credit card
Every helper is free for 30 days. Answer 3 questions and get the full result in 2 minutes.
Start free →skdformat
Transform thesis chaos into compliance-ready LaTeX instantly
❌ ShanghaiTech thesis writers struggle with complex LaTeX formatting, structural compliance, and institutional requirements across covers, abstracts, references, and blind-review builds.
✅ Users produce fully compliant, print-ready ShanghaiTech dissertations with correct formatting, structure, and LaTeX implementation using shtthesis templates.
- ✓Create compliant thesis covers and abstract pages automatically
- ✓Validate structure against official ShanghaiTech format requirements
- ✓Generate blind-review and print-ready document builds
- ✓Audit existing LaTeX projects for formatting violations
- ✓Implement shtthesis templates with proper chapter organization
👁 2 views · 📦 0 installs
Free to install — no account needed
Copy the command below and paste into your agent.
Instant access • No coding needed • No account needed
What you get in 5 minutes
- Full skill code ready to install
- Works with 4 AI agents
- Lifetime updates included
Run this helper
Answer a few questions and let this helper do the work.
▸Advanced: use with your AI agent
Description
--- name: skdformat description: ShanghaiTech graduate thesis formatting, structure checking, and LaTeX implementation with shtthesis. Use when creating, linting, fixing, or migrating a ShanghaiTech thesis or dissertation, especially for LaTeX projects that need compliant covers, abstracts, table of contents, chapter structure, references, appendices, blind-review builds, or print-ready output. --- # skdformat ## Overview Use this skill to create or audit ShanghaiTech thesis documents. Treat the bundled reference as the source of truth, and treat `shtthesis` as the preferred LaTeX implementation layer rather than a replacement for the rules. Read [references/shanghaitech-thesis-format.md](references/shanghaitech-thesis-format.md) for exact requirements. For a new self-contained LaTeX project, also read [references/thesis-starter.tex](references/thesis-starter.tex), [references/build-thesis-example.ps1](references/build-thesis-example.ps1), and [references/shtthesis-user-guide.txt](references/shtthesis-user-guide.txt) as needed. ## Workflow 1. Determine the task mode: - create a new thesis skeleton - lint an existing Word or LaTeX thesis - fix concrete formatting violations - migrate existing content into a compliant thesis structure 2. Apply precedence in this order: - school rules - bundled reference - `shtthesis` defaults only when they do not conflict 3. Read only the relevant reference sections: - content and required sections: `## 3` and `## 4` - citation rules: `## 5` and `### 7.8` - page layout and typography: `## 6` - LaTeX template behavior: `## 7` - implementation checklist: `## 8` - starter project skeleton: `references/thesis-starter.tex` - example dual-build wrapper: `references/build-thesis-example.ps1` - raw shtthesis guide text: `references/shtthesis-user-guide.txt` 4. Produce concrete outputs: - file edits or code - rule-based findings with exact file references - missing items and the required fixes - build commands and assumptions ## LaTeX Defaults Prefer `shtthesis` for ShanghaiTech graduate theses. Use these defaults unless the existing project already has a justified alternative: - `\documentclass[master]{shtthesis}` or `\documentclass[doctor]{shtthesis}` - compile with `latexmk -pdfxe` - use `latexmk -pdflua` if cross-platform PDF compatibility becomes a problem - do not use `pdfLaTeX` - keep `reference.bib` and `shanghaitech-emblem.pdf` in the project root - set thesis metadata only through `\shtsetup{...}` - use the standard structure: ```latex \maketitle \frontmatter \begin{abstract}...\end{abstract} \begin{abstract*}...\end{abstract*} \makeindices \mainmatter % chapters \makebiblio \appendix % appendices \backmatter % acknowledgement / resume / publications ``` - use `anonymous` for blind-review output - use `print` for print-ready output - do not enable `comfort` by default for graduate theses - if strict bilingual figure/table captions are required, load `bicaption` with `list=off` Use this minimal metadata pattern when creating a new project: ```latex \shtsetup{ degree-name = {...}, degree-name* = {...}, title = {...}, title* = {...}, keywords = {...}, keywords* = {...}, author = {...}, author* = {...}, institution = {...}, institution* = {...}, supervisor = {...}, supervisor* = {...}, supervisor-institution = {...}, discipline-level-1 = {...}, discipline-level-1* = {...}, date = {...}, date* = {...}, bib-resource = {reference.bib}, } ``` ## Linting Checklist When checking an existing thesis, verify at minimum: - required sections exist and appear in the correct order - Chinese and English cover metadata are consistent - abstracts are both present and semantically aligned - front matter pagination and right-page starts are correct - heading depth and numbering follow the school rules - figure, table, and equation numbering is chapter-based - reference style and citation commands match the required scheme - appendix and backmatter ordering is correct - anonymous and formal builds do not leak author information If the project already contains build wrappers or automation, preserve them unless they clearly violate the rules. ## Reporting When the user asks for a review or formatting check: - report violations before summaries - cite exact file paths and line references when possible - distinguish between hard rule violations and template-specific recommendations - prefer minimal fixes that preserve the author’s writing and project structure ## Related Resources Read [references/shanghaitech-thesis-format.md](references/shanghaitech-thesis-format.md) when exact wording, page layout values, citation details, or `shtthesis` command behavior is needed.
Security Status
Scanned
Passed automated security checks
Related AI Tools
More Grow Business tools you might like
codex-collab
FreeUse when the user asks to invoke, delegate to, or collaborate with Codex on any task. Also use PROACTIVELY when an independent, non-Claude perspective from Codex would add value — second opinions on code, plans, architecture, or design decisions.
Run freeRails Upgrade Analyzer
FreeAnalyze Rails application upgrade path. Checks current version, finds latest release, fetches upgrade notes and diffs, then performs selective upgrade preserving local customizations.
Run freeAsta MCP — Academic Paper Search
FreeDomain expertise for Ai2 Asta MCP tools (Semantic Scholar corpus). Intent-to-tool routing, safe defaults, workflow patterns, and pitfall warnings for academic paper search, citation traversal, and author discovery.
Run freeHand Drawn Diagrams
FreeCreate hand-drawn Excalidraw diagrams, flows, explainers, wireframes, and page mockups. Default to monochrome sketch output; allow restrained color only for page mockups when the user explicitly wants webpage-like fidelity.
Run freeMove Code Quality Checker
FreeAnalyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working
Run freeClaude Memory Kit
Free"Persistent memory system for Claude Code. Your agent remembers everything across sessions and projects. Two-layer architecture: hot cache (MEMORY.md) + knowledge wiki. Safety hooks prevent context loss. /close-day captures your day in one command. Z
Run free