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.

80

Quality

100%

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

100%Weight 40%Scale 1-3

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

The body is a lean, well-structured drift-sync workflow with concrete commands, a file-by-file checklist, and a re-run verification loop. It is actionable and clearly sequenced without resorting to nested external references.

DimensionReasoningScore

Conciseness

Uses compact tables for file inventory and the maintenance map; avoids explaining concepts Claude already knows; prose is functional rather than padded, so most tokens earn their place.

3 / 3

Actionability

Provides executable commands ('ls -1 .agents/skills/', 'ls -1 crates/') plus a concrete file-by-file drift checklist naming exact files and fields to verify, giving specific actionable guidance.

3 / 3

Workflow Clarity

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

3 / 3

Progressive Disclosure

Self-contained with no bundle files and no nested references; content is well-sectioned into clearly navigable steps and tables, which suffices for a single-file skill.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, third-person, and covers both capabilities and explicit run-when triggers with natural keyword variations. It is a strong, low-conflict description.

DimensionReasoningScore

Specificity

Names multiple concrete targets and actions ('Detect and fix drift', 'skill inventories, workflow chains, architecture tables, issue/PR templates, and cross-references'), matching the multi-specific-action anchor.

3 / 3

Completeness

Explicitly answers both what (detect/fix drift across named infra files) and when ('Run after adding, removing, or renaming skills or components'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Lists natural trigger phrases a user would actually say ('sync agent infra', 'sync skills', 'update agent docs', 'check agent consistency'), giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (agent-first infrastructure drift) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
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.