Token导航 LogoToken导航

Agent Skill · 研究检索

latex-revision-tracker(乳胶修订跟踪器)

latex-revision-tracker 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

latex-revision-tracker 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 16,860。

总安装 6,939周安装 278GitHub Stars 公开资料未说明下载 2,246核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:latex-revision-tracker(乳胶修订跟踪器)
来源仓库:https://github.com/larry-of-cosmotim/latex-revision-tracker
安装命令:
openclaw skills install latex-revision-tracker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install latex-revision-tracker

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于跟踪、管理和修改大型 LaTeX 学术论文的系统工作流程,具有版本控制、内容集成和质量保证。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install latex-revision-tracker;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

latex-revision-tracker 怎么安装?

在终端执行 openclaw skills install latex-revision-tracker。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

latex-revision-tracker 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

latex-revision-tracker 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

latex-revision-tracker 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

latex-revision-tracker 用的人多吗?

公开数据是累计安装 6,939 次,近一周安装 278 次,下载 2,246 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

latex-revision-tracker 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
latex-revision-tracker

乳胶修订跟踪器 · 本页

6,939—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
latex-revision-tracker
description
Systematic workflow for tracking, managing, and revising large LaTeX academic papers with version control, content integration, and quality assurance.
version
1.0.0
homepage
https://github.com/Larry-of-cosmotim/latex-revision-tracker
metadata
openclaw
emoji
📐

LaTeX Revision Tracker Skill

Overview

This skill provides a comprehensive workflow for managing revisions to large LaTeX academic papers (10+ pages, multiple sections, complex bibliographies). It emphasizes systematic version control, careful content integration, and quality assurance throughout the revision process.

When to Use

Use this skill when:

  • Revising large academic papers or dissertations in LaTeX
  • Integrating new content (figures, data, analysis) into existing manuscripts
  • Collaborating on multi-author academic documents
  • Preparing papers for journal submission with multiple revision rounds
  • Managing complex manuscripts with extensive bibliographies and cross-references

Core Workflow

1. Version Control Setup

File Naming Convention:

manuscript_v1_initial.tex
manuscript_v2_reviewer_response.tex  
manuscript_v3_final_submission.tex

Change Documentation: Create version_changes.md for each revision:

# V2 TO V3 CHANGES SUMMARY

## CHANGES MADE:
### ✅ NEW SECTION ADDED:
- **Section 4.2**: Glass Limit Analysis  
- **Location**: After thermal conductivity discussion
- **Content**: 3 paragraphs + 1 figure

### ✅ NEW FIGURE:
- **cahill_plot.pdf** - Publication-ready (300 DPI)
- **Reference**: Figure~\
ef{fig:cahill_plot}
- **Caption**: [Complete caption text]

### ✅ CONTENT MODIFICATIONS:
- Updated abstract (lines 25-35)
- Revised conclusion (Section 6, paragraph 2)
- Added 12 new citations

## INTEGRATION DETAILS:
- **Placement**: After existing analysis, before discussion
- **Line numbers**: Approximately 450-480
- **Compilation status**: ✅ Success / ❌ Unicode issues

2. Content Integration Strategy

Pre-Integration Checklist:

  • [ ] New content reviewed for accuracy and style
  • [ ] Figures prepared in publication quality (PDF/EPS preferred)
  • [ ] All citations properly formatted and verified
  • [ ] Mathematical notation consistent with existing document
  • [ ] Cross-references planned (\label{} and \ ef{} commands)

Integration Process:

1. Backup current working version
2. Identify integration point in document structure
3. Plan figure/table placement and numbering
4. Insert content with proper sectioning
5. Update cross-references throughout document
6. Compile and resolve errors iteratively

3. LaTeX-Specific Quality Control

Compilation Workflow:

# For bibliography updates (full workflow)
pdflatex manuscript.tex
bibtex manuscript
pdflatex manuscript.tex
pdflatex manuscript.tex

# For minor changes (quick check)
pdflatex manuscript.tex
pdflatex manuscript.tex

Common Issues and Solutions:

Unicode Characters:

% Problem: Special characters (κ, α, β) in text
% Solution: Use math mode or proper packages
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}

% In text: $\kappa$ not κ
% In equations: \begin{equation} \kappa = ... \end{equation}

Reference Resolution:

% Ensure labels come after what they reference
\section{Results}
\label{sec:results}  % ✅ After section

\begin{figure}
\includegraphics{plot.pdf}
\caption{Important results}
\label{fig:results}  % ✅ After caption
\end{figure}

Float Management:

% For flexible placement
\begin{figure}[htbp]

% To force exact position (use sparingly)
\usepackage{float}
\begin{figure}[H]

% For wide figures in two-column format
\begin{figure*}[t]

4. Academic Content Integration

Section-Specific Integration Guidelines:

Abstract Updates:

  • Maintain 150-250 word limit
  • Update contribution statements to reflect new content
  • Ensure keywords remain accurate

Introduction Modifications:

  • Integrate new motivation naturally
  • Update contribution list if needed
  • Maintain logical flow from general to specific

Related Work Additions:

  • Group new citations thematically
  • Compare explicitly with existing approaches
  • Maintain chronological awareness

Results Section Integration:

  • Number figures/tables consecutively
  • Reference all new content in text
  • Maintain consistent data presentation style

Discussion/Conclusion Updates:

  • Integrate implications of new findings
  • Update limitations section if applicable
  • Revise future work based on new insights

5. Bibliography Management

Citation Integration Process:

  1. Add new entries to .bib file
  2. Use consistent citation keys (author2024keyword)
  3. Verify all required fields (author, title, year, venue)
  4. Check for duplicate entries
  5. Run bibtex to update references
  6. Resolve any citation warnings

Citation Style Consistency:

% In-text citations
Recent work has shown \cite{smith2024analysis}...
Multiple studies \cite{jones2023,brown2024,wilson2024} have...
As demonstrated by Smith et al.~\cite{smith2024analysis}...

% Reference formatting (depends on journal style)
% IEEE: [1] A. Smith, "Title," Journal, vol. 1, pp. 1-10, 2024.
% ACM: [1] Smith, A. 2024. Title. Journal 1, 1 (2024), 1-10.

6. Quality Assurance Process

Pre-Submission Checklist:

  • [ ] Document compiles without errors or warnings
  • [ ] All figures appear correctly and are referenced in text
  • [ ] All tables are properly formatted and referenced
  • [ ] Bibliography is complete and properly formatted
  • [ ] Cross-references resolve correctly
  • [ ] Page layout is consistent with journal requirements
  • [ ] Mathematical notation is consistent throughout
  • [ ] Acronyms defined on first use
  • [ ] Line spacing and margins correct for submission

Collaboration Workflow:

1. Author A makes changes → commits with detailed message
2. Author B reviews changes → suggests modifications
3. Changes documented in version log
4. Final integration by designated "manuscript manager"
5. All co-authors review final version before submission

7. Error Resolution Strategies

Common LaTeX Errors:

Missing References:

LaTeX Warning: Reference `fig:unknown' undefined
Solution: Check \label{} and \
ef{} spelling, compile twice

Overfull/Underfull Boxes:

Overfull \hbox (15.0pt too wide)
Solution: Rephrase text, add hyphenation hints (\-), or use \sloppy

Float Issues:

Too many unprocessed floats
Solution: Add \clearpage or adjust float placement options

Bibliography Errors:

Citation `unknown2024' undefined
Solution: Check .bib file, run bibtex, compile again

8. Performance Optimization

For Large Documents (50+ pages):

  • Use \includeonly{} to compile specific chapters
  • Split large documents with \input{} or \include{}
  • Use \graphicspath{} for organized figure directories
  • Consider latexmk for automated compilation management

Memory Management:

% For documents with many figures
\usepackage{graphicx}
\DeclareGraphicsExtensions{.pdf,.eps,.png,.jpg}

% For complex bibliographies
\usepackage[backend=bibtex,style=ieee]{biblatex}

Advanced Features

1. Diff Tracking

CRITICAL: Diff files inherit ALL citation dependencies from the source documents. You MUST run the full bibliography workflow — a single pdflatex pass will ALWAYS produce citation errors ([?] markers) in diff files. This is the most common mistake.

Full diff workflow (mandatory — no shortcuts):

# Step 1: Generate the diff .tex
latexdiff manuscript_v1.tex manuscript_v2.tex > diff_v1_v2.tex

# Step 2: Copy bibliography files to the same directory
# The diff file needs access to the SAME .bib files and .bst style
cp manuscript.bib .    # if not already present

# Step 3: Full compilation (ALL steps required)
pdflatex diff_v1_v2.tex      # First pass — generates .aux with citation keys
bibtex diff_v1_v2            # Resolves citations from .bib file
pdflatex diff_v1_v2.tex      # Second pass — incorporates bibliography
pdflatex diff_v1_v2.tex      # Third pass — resolves all cross-references

Never do this:

# WRONG — will produce [?] for every citation
pdflatex diff_v1_v2.tex   # single pass = broken citations

Troubleshooting citation errors in diff files:

  • [?] markers → you skipped bibtex. Run the full 4-step workflow above.
  • I couldn't open file name.bib → copy the .bib file to the diff directory.
  • I couldn't open style file name.bst → copy the .bst file too.
  • Still broken → check that \bibliography{} and \bibliographystyle{} paths are correct in the source .tex files before running latexdiff.

Post-diff cleanup: After the diff PDF is verified, remove all intermediate files. Only the final PDF should remain.

# Clean up all auxiliary and intermediate files
rm -f diff_v1_v2.tex diff_v1_v2.aux diff_v1_v2.log diff_v1_v2.out \
      diff_v1_v2.bbl diff_v1_v2.blg diff_v1_v2.toc diff_v1_v2.lof \
      diff_v1_v2.lot diff_v1_v2.synctex.gz diff_v1_v2.fls \
      diff_v1_v2.fdb_latexmk diff_v1_v2.nav diff_v1_v2.snm
# Keep only: diff_v1_v2.pdf

Rule: Always clean up after generating a diff PDF. The diff .tex file is a throwaway — it's auto-generated and can be recreated anytime from the two source versions. Never keep it around to clutter the workspace.

2. Automated Quality Checks

# Check for common LaTeX issues
lacheck manuscript.tex

# Count words (approximate)
texcount manuscript.tex

# Validate bibliography
bibtex manuscript 2>&1 | grep -i warning

3. Collaborative Tools

# Git integration for version control
git add manuscript_v3.tex version_changes.md
git commit -m "Add glass limit analysis section, update abstract"
git tag v3.0-submission

# Overleaf sync for real-time collaboration
git push overleaf master

Templates

Change Log Template

# VERSION X.Y CHANGES

## SUMMARY
Brief description of major changes

## NEW CONTENT
- Section/subsection additions
- Figure/table additions  
- New citations (count)

## MODIFICATIONS
- Sections revised
- Figures updated
- Text corrections

## TECHNICAL NOTES
- Compilation status
- Package updates needed
- Known issues

## REVIEW STATUS
- [ ] Content reviewed by Author A
- [ ] Figures checked by Author B  
- [ ] Bibliography verified
- [ ] Final compilation successful

Integration Checklist Template

## PRE-INTEGRATION
- [ ] Content accuracy verified
- [ ] Style guide compliance checked
- [ ] Citations properly formatted
- [ ] Figures publication-ready

## INTEGRATION
- [ ] Placement planned
- [ ] Cross-references updated
- [ ] Numbering scheme maintained
- [ ] LaTeX syntax verified

## POST-INTEGRATION
- [ ] Document compiles successfully
- [ ] All references resolve
- [ ] Visual layout acceptable
- [ ] Change log updated

Best Practices

  1. Always backup before major changes
  2. Document everything in change logs
  3. Test compilation early and often
  4. Use consistent naming for files and labels
  5. Review systematically with checklists
  6. Collaborate deliberately with clear ownership
  7. Plan integration before making changes
  8. Maintain quality throughout the process

Common Pitfalls

  • Skipping documentation: Change logs save time later
  • Inconsistent compilation: Always run full workflow for bibliography
  • Poor float placement: Plan figure integration carefully
  • Missing backups: One corrupted file can lose days of work
  • Rushed integration: Quality issues compound in large documents
  • Ignoring warnings: Small issues become large problems

Tools and Resources

Essential Tools:

  • LaTeX distribution (TeX Live, MiKTeX)
  • PDF viewer with refresh capability (SumatraPDF, Skim)
  • Text editor with LaTeX support (TeXstudio, VS Code with LaTeX Workshop)
  • Reference manager (Mendeley, Zotero, BibTeX)

Quality Assurance:

  • latexdiff for visual change tracking
  • lacheck for syntax validation
  • texcount for word counting
  • Git for version control

This skill provides the systematic approach needed to manage complex LaTeX academic papers while maintaining quality and avoiding common pitfalls that plague large document revision processes.

平台分布

OpenClaw

75.45%
按下载量换算1,695

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills