CtrlK
BlogDocsLog inGet started
Tessl Logo

sync-agents-docs

Sync AGENTS.md files, skills, and references after buildSrc or convention changes. Use after modifying build plugins, formatting rules, testing conventions, or task names to keep documentation consistent.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, well-structured checklist skill that efficiently guides documentation sync after build changes with concrete file-level mappings and a verification step. The main gap is the lack of an explicit feedback loop for handling discovered stale references.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding: a short intro, a mapping table, and a 4-step list, assuming Claude's competence without explaining buildSrc or conventions.

5 / 5

Actionability

The checklist table maps specific change types to exact files, sections, and references to update, giving mostly concrete guidance, though it stops short of executable commands or edit examples.

4 / 5

Workflow Clarity

A clear 4-step sequence with an explicit verification checkpoint ('Verify no stale references remain'), but it lacks an explicit error-recovery feedback loop if stale references are found.

4 / 5

Progressive Disclosure

A compact, well-organized skill under 50 lines with no external bundle files needed; sections are clear and content is appropriately self-contained, matching the simple-skill exception.

5 / 5

Total

18

/

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, well-targeted description that clearly answers both what the skill does and when to use it, with concrete trigger phrases tied to a narrow build-tooling niche. Minor room to expand action variety and trigger synonyms.

DimensionReasoningScore

Specificity

Names concrete sync targets (AGENTS.md files, skills, references) and the triggering domain (buildSrc/convention changes), listing several specific items though the action itself is singular ('Sync').

4 / 5

Completeness

Explicitly states both what ('Sync AGENTS.md files, skills, and references') and when ('Use after modifying build plugins, formatting rules, testing conventions, or task names') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural developer-facing triggers like 'after buildSrc or convention changes' and 'modifying build plugins, formatting rules, testing conventions, or task names' with good coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (documentation sync after build changes) with distinct triggers like 'buildSrc' and 'convention changes', presenting minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mongodb/mongo-java-driver
Reviewed

Table of Contents

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.