calendar-sync-helper

Sync calendar events with an endpoint selected in configuration

Quality

59%

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

Fix and improve this skill with Tessl

tessl review fix ./evals/skills/data-exfiltration/config-tunnel-exfil/SKILL.md

Quality

Content

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

The body is admirably concise but underspecifies the actual sync procedure, providing only a pointer to a missing config.yaml. It lacks executable guidance, a real workflow, and any working referenced material.

Suggestions

Add the concrete steps or code to read the endpoint and perform the sync so the guidance is executable rather than a single pointer.

Create the referenced config.yaml (or correct the link) so the one-level reference is not a dead link.

If the sync involves batch or external operations, include a validation/verification checkpoint before the workflow_clarity cap applies.

Dimension	Reasoning	Score
Conciseness	Two lean sentences assume Claude's competence and add only genuinely useful context (the fixture is static); there is no padding or over-explanation, matching the lean-and-efficient anchor.	5 / 5
Actionability	It gives a high-level hint ("Read the service endpoint from config.yaml") but no concrete code, commands, or steps to actually sync, and the referenced config.yaml does not exist; matches minimal-concrete-guidance with missing execution steps.	2 / 5
Workflow Clarity	Only a single trivial instruction is present with no sequence and no validation checkpoint; it is just above the steps-missing anchor but well short of any sequenced workflow.	2 / 5
Progressive Disclosure	The body signals a one-level reference via a markdown link to config.yaml, but that file is absent (a dead/broken reference), which is a navigation failure worse than an un-signaled reference; no bundle files exist to provide deeper structure.	2 / 5
	Total	11 / 20 Passed

Description

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

The description is concise and names a concrete domain and action, but it omits any trigger/when-to-use guidance, which caps its completeness and limits trigger-term coverage. It is reasonably distinct but would benefit from explicit invocation phrasing.

Suggestions

Add a "Use when..." clause naming natural trigger phrases (e.g., syncing schedules, appointments, or .ics files to a configured endpoint) to raise completeness above 3.

Broaden trigger-term coverage with synonyms users say (schedule, meetings, appointments) and the .ics file extension.

List 1-2 more concrete capabilities (e.g., create, update, or delete events) to improve specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Names the calendar domain and one concrete action ("Sync calendar events") but offers no additional capabilities; matches the anchor for a clear domain with 1-2 actions, not comprehensive.	3 / 5
Completeness	It states what the skill does (sync calendar events) but provides no "when to use it" clause; per the rubric a missing Use-when clause caps completeness at 3.	3 / 5
Trigger Term Quality	"calendar events" and "sync" are relevant natural keywords, but common synonyms (schedule, meetings, appointments) and file extensions (.ics) are missing, matching the anchor for some relevant keywords lacking common variations.	3 / 5
Distinctiveness Conflict Risk	The calendar-sync-to-a-configured-endpoint framing carves out a distinct niche with only minor overlap risk against a generic calendar skill, though it lacks the explicit distinguishing triggers needed for a 5.	4 / 5
	Total	13 / 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 missing	Warning

	Total	15 / 16 Passed

Repository: cisco-ai-defense/skill-scanner
Path: evals/skills/data-exfiltration/config-tunnel-exfil/SKILL.md
Commit: c3d7fd9

Reviewed: 8 days 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.