Tessl • The management layer for AI agent skills

SkillPublic

sync-notes

Synchronize CS-Notes Git changes and material projections when the user says 同步笔记, sync笔记, or pull CS-Notes and push. Preserve unpublished intakes and require material-specific human completion evidence before archival.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

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

A dense, highly operational workflow that validates risky git and material-authority operations at every phase and assumes Claude's competence without padding. The main costs of its extreme compression are readability within steps 4 and 7 and a few placeholder commands rather than copy-paste-ready ones.

Suggestions

Break the monolithic paragraphs of steps 4 and 7 into labeled sub-bullets (e.g., 'authority 对账', 'fork 权限核对', 'PR 创建', 'PR 更新') so the conditional branches inside each step are scannable.

Replace the '…' placeholders in the material_source.py complete/reconcile command examples with one concrete argument example each so they are copy-paste ready.

Consider moving the Material Lifecycle reconciliation rules of step 4 into a references/ file (e.g., MATERIALS.md) and keeping a short pointer plus the commands inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Extremely lean: no explanations of concepts Claude already knows and every clause is an operational rule. Not 5 because a few clauses could be consolidated — push-permission caveats repeat across steps 6–7 and step 7 packs several scenarios into run-on sentences.	4 / 5
Actionability	Concrete executable commands throughout (material_reconcile.py, material_queue.py --check, unittest discover, git diff --check, PR flags --repo/--base/--head). Not 5 because 'complete --evidence … --phase prepare' uses ellipsis placeholders and the step-3 merge strategy is described rather than given as exact commands.	4 / 5
Workflow Clarity	A clear numbered 1–8 sequence with explicit validation (three check commands in step 5), a failure-mode checklist in step 6, and feedback loops (prepare/apply plan review, read-back on ambiguous sends, post-push PR head verification) covering the destructive push/merge operations. All checkpoints are present, so anchor 4's 'minor validation gaps' does not apply.	5 / 5
Progressive Disclosure	Well-organized single-file layout (指令 table, numbered 同步路径) with the one external link clearly signaled one level deep. Not 5 because steps 4 and 7 are monolithic nested paragraphs whose reconciliation and fork/PR rules would navigate better as sub-bullets or a reference file.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 description: concrete capabilities, explicit third-person phrasing, and an explicit trigger clause with exact user utterances in both Chinese and English. The only weakness is modest coverage — the check-only and PR variants exist in the body but are not surfaced in the description.

Dimension	Reasoning	Score
Specificity	Names the CS-Notes domain and several concrete actions ('Synchronize CS-Notes Git changes and material projections', 'Preserve unpublished intakes', 'require material-specific human completion evidence before archival'). Not 5 because the check-only and PR-creation variants documented in the body are absent, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (sync git changes and material projections, preserve intakes, gate archival on evidence) and 'when' (concrete quoted trigger phrases), matching the anchor-5 structure; the 'when' is fully explicit so anchor 4 does not apply.	5 / 5
Trigger Term Quality	'when the user says 同步笔记, sync笔记, or pull CS-Notes and push' lists exact natural user utterances with mixed-language synonyms. Not 5 because common variations such as '同步' alone, 'sync notes', or 'push CS-Notes' are missing; clearly above anchor 3's partial keyword coverage.	4 / 5
Distinctiveness Conflict Risk	A clear CS-Notes-specific niche with distinct Chinese/English trigger phrases; minimal overlap or conflict risk with generic git or note-taking skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: huangruiteng/CS-Notes
Path: .codex/skills/sync-notes/SKILL.md
Revision: eb07ad1

Reviewed: 6 days ago

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.

sync-notes

Table of Contents

Is this your skill?