miaodi/report-iteration-overleaf
skills/report-iteration-overleaf/SKILL.md
Use when iterating on a course report, reviewing previous submissions, improving LaTeX structure and analysis, or preparing sources for Overleaf upload or Git sync.
business
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add miaodi/llm_config report-iteration-overleafInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:57 PM22.0s1 file scanned
SKILL.md
- name:
- report-iteration-overleaf
- description:
- Use when iterating on a course report, reviewing previous submissions, improving LaTeX structure and analysis, or preparing sources for Overleaf upload or Git sync.
Report Iteration And Overleaf Skill
Purpose
Iterate on a course report by reviewing previous reports, improving the structure and analysis, and preparing updated LaTeX sources for Overleaf workflows.
When To Use
Use when a project includes a prior report, when the next report should build on an earlier submission, or when the final output needs to be pushed back to Overleaf.
Priorities
- Understand what the previous report did well and where it was weak.
- Preserve useful structure while improving technical clarity and analysis quality.
- Keep the LaTeX project organized and easy to maintain.
- Work with the actual Overleaf source workflow available: local files, ZIP import/export, or Git integration.
Workflow
- Read the previous report and identify reusable structure, recurring notation, figure conventions, and analysis gaps.
- Separate what should be reused from what should be replaced or strengthened.
- Align the new report with the current assignment requirements and latest experiment results.
- Update sections, figures, captions, and conclusions so they reflect the new work rather than lightly edited old text.
- Keep the LaTeX source organized with clear figure paths, section files, and reproducible plot generation where practical.
- If Overleaf source is available locally, edit that source directly.
- If Overleaf Git integration is available, use the Git-backed workflow carefully and preserve the project structure.
- If only ZIP import/export is available, prepare a clean uploadable project directory.
Review Checklist
- What is worth reusing from the previous report?
- What analysis was weak, incomplete, or overly vague?
- Do the new plots and tables answer the actual project questions?
- Are captions and figure references informative?
- Is the LaTeX project clean enough to upload or sync back to Overleaf?
- Is the Overleaf workflow path actually available, or does it still need user input?
Constraints
- Do not copy old conclusions forward without re-validating them against the current experiments.
- Do not assume direct Overleaf access unless the project files or Git integration details are provided.
- Do not produce cosmetic report updates without improving the technical argument.
- Prefer concise, meaningful section and figure revisions over wholesale rewriting without purpose.
Output
Provide:
- what to reuse from the previous report
- what to change in the current report
- report structure recommendations
- figure and caption recommendations
- the practical path to update or upload the Overleaf project
Related Skills
miaodi/computational-learning-notes
development
VerifiedTrustedCommunity
Use when creating C++ learning notes or minimal experiments for low-level computational, numerical, CPU/GPU, compiler, and hardware concepts such as false sharing, floating point, registers, caches, SIMD, atomics, numerical stability, and benchmarking pitfalls.
SKILL.mdUpdated Jun 2, 2026
miaodi/latex-project-build
development
VerifiedTrustedCommunity
Use when configuring, diagnosing, or compiling LaTeX projects, especially multi-file reports, theses, books, chapter-based projects, Overleaf exports, latexmk/arara/Makefile workflows, bibliography/index/glossary passes, or projects that require pdflatex, xelatex, lualatex, latex->dvips, biber, or bibtex.
SKILL.mdUpdated May 28, 2026
miaodi/graph-algorithms
development
VerifiedTrustedCommunity
Use when working with graph traversals (BFS, DFS, level-order), minimum spanning trees, strongly connected components, topological sort, graph coloring, bipartite detection, elimination trees, level-set extraction, parallel graph algorithms, task-tree parallelism, sparse graph representations, and exploiting graph structure for parallel sparse computations.
SKILL.mdUpdated May 21, 2026
miaodi/git-workflow
testing
VerifiedTrustedCommunity
Use when planning or executing Git branch workflows, especially merge/rebase across branches, conflict resolution, safe history rewriting, and recovery from mistakes.
SKILL.mdUpdated May 21, 2026