overleaf-sync

Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to bridge their ARIS paper directory with an Overleaf project.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary skill document: lean, executable, and structured with explicit validation gates and conflict handling. It avoids teaching known concepts and keeps all guidance concrete and copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no explanation of what git/rsync/Overleaf are, and every section earns its place (constants, architecture, sub-commands, guards). Not below 3 because there is no padded concept explanation; not applicable above the scale max.	3 / 3
Actionability	Every sub-command ships copy-paste-ready executable shell (e.g. `git pull --ff-only`, the rsync excludes list) and concrete commit-message examples, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Pull/push/status have explicit validation checkpoints ("must show URL WITHOUT token", "Audit clean"), a confirmation gate before push, a per-hunk diff decision table, and a divergence/conflict-resolution protocol with error recovery — matching the top anchor.	3 / 3
Progressive Disclosure	A single well-organized SKILL.md overview with one-level references to bundled tools (overleaf_setup.sh, overleaf_audit.sh) and a "See Also" section; no nested 2+ level reference chains exist (no references/scripts/assets directories are present).	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-targeted description: it states the concrete capability, gives bilingual natural-language triggers, and explicitly covers both what the skill does and when to invoke it. It avoids fluff and over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: "Two-way sync", "ARIS audit/edit workflows stay on the local copy", and collaborators editing in the web UI, matching the anchor that lists several specific concrete actions.	3 / 3
Completeness	It clearly answers both "what" (two-way sync between a local paper directory and an Overleaf project) and "when" via an explicit "Use when..." clause, matching the top anchor.	3 / 3
Trigger Term Quality	The "Use when user says" clause enumerates natural bilingual triggers ("同步 overleaf", "overleaf sync", "push overleaf", "pull overleaf"), giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (Overleaf Git bridge for an ARIS paper directory) with distinct, named triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: wanshuiyin/Auto-claude-code-research-in-sleep
Path: skills/overleaf-sync/SKILL.md
Commit: c5f3d5b

Reviewed: 9 minutes ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.