CtrlK
BlogDocsLog inGet started
Tessl Logo

sync-agent-infra

Detect and fix drift across agent-first infrastructure files. Ensures skill inventories, workflow chains, architecture tables, issue/PR templates, and cross-references stay consistent when skills, crates, or workflows change. Run after adding, removing, or renaming skills or components. Trigger keywords - sync agent infra, sync skills, update agent docs, check agent consistency, agent infra drift, sync contributing, sync agents.

73

Quality

91%

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

88%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 well-structured, actionable instruction skill with a clear sequenced workflow and an explicit verification loop. The main improvement opportunity is moving the long maintenance map and label taxonomy into reference files to improve progressive disclosure and conciseness.

Suggestions

Move the Skill Maintenance Map table and the canonical label set into a reference file (e.g. references/maintenance-map.md) referenced one level deep from the body, tightening conciseness and improving progressive disclosure.

Trim or consolidate the repeated label/agent-request semantics that appear in both the Labels section and the Issue Lifecycle and Skill Cross-References sections to avoid restating the same gating rules.

Consider a short validation checklist at the end of Step 2 summarizing the pass criteria across all file categories, so the re-run verification in Step 4 has a single explicit gate.

DimensionReasoningScore

Conciseness

Dense and efficient, assuming Claude's competence with no padding about what skills/crates/PRs are; however the label taxonomy list and the maintenance map are long reference-like material that could be trimmed or externalized.

4 / 5

Actionability

Provides concrete executable commands ('ls -1 skills/', 'npx -y skills add . --list') and explicit per-file checklist criteria with structured report and fix templates and placeholders.

5 / 5

Workflow Clarity

Clear five-step sequence (Inventory, Check, Report, Fix, Summarize) with an explicit feedback loop ('After fixing, re-run Step 2 to verify consistency') covering batch file edits.

5 / 5

Progressive Disclosure

Well-organized with clear sections and self-contained tables and no nested references, but a large amount of reference-like material (maintenance map, label taxonomy) is inlined rather than split into bundle files.

4 / 5

Total

18

/

20

Passed

Description

95%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, specific description that clearly conveys both purpose and triggering conditions with natural synonyms and low conflict risk. The only minor gap is a relatively narrow set of distinct action verbs.

DimensionReasoningScore

Specificity

Names the domain and lists concrete objects kept consistent ('skill inventories, workflow chains, architecture tables, issue/PR templates, and cross-references') with detect/fix actions, but the verb set is limited rather than a broad list of distinct actions, so it falls just short of comprehensive.

4 / 5

Completeness

Explicitly answers both what ('Detect and fix drift across agent-first infrastructure files') and when ('Run after adding, removing, or renaming skills or components') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases with synonyms ('sync agent infra, sync skills, update agent docs, check agent consistency, agent infra drift, sync contributing, sync agents') that a user would plausibly say.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (agent-first infrastructure consistency) with trigger keywords specific to this purpose, minimizing overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
NVIDIA/OpenShell
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.