CtrlK
BlogDocsLog inGet started
Tessl Logo

contact-sync

Sync a person to Apple Contacts. Searches by name/email, creates if missing, updates if info is incomplete. Designed to be called by the dispatcher after email interactions (drafting replies, processing emails) or on demand. Triggers: EN: "sync contact", "add to contacts", "save contact", "update contact", "is this person in my contacts". IT: "sincronizza contatto", "aggiungi ai contatti", "salva contatto", "aggiorna contatto". FR: "synchroniser le contact", "ajouter aux contacts", "sauvegarder le contact". ES: "sincronizar contacto", "agregar a contactos", "guardar contacto". DE: "Kontakt synchronisieren", "zu Kontakten hinzufuegen", "Kontakt speichern". PT: "sincronizar contato", "adicionar aos contatos", "salvar contato".

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 focused, actionable instruction skill with a clear sequenced workflow, concrete MCP tooling, and disciplined brevity. Adding an explicit post-update verification step and tightening a few explanatory paragraphs would push it higher.

Suggestions

Add an explicit validation checkpoint after Step 4 (e.g., re-fetch the contact to confirm the update applied) to raise workflow_clarity toward 5.

Show one full example tool invocation with concrete argument values (not just field lists) to make the guidance fully copy-paste ready.

Tighten the update_contact semantics paragraph and the email-integration examples to trim tokens without losing clarity.

DimensionReasoningScore

Conciseness

Lean and well-organized with no padding explaining concepts Claude already knows (no "what is Apple Contacts" filler); each section earns its place, though a few explanatory notes like the update_contact semantics paragraph could be trimmed slightly, fitting the 4 anchor above the 3.

4 / 5

Actionability

Provides concrete MCP tool names (search_contacts, get_contact, create_contact, update_contact) with specific field lists, name-mapping rules, and copy-ready output examples covering common cases; falls just short of 5 because exact tool-call argument shapes are described rather than shown as full invocations.

4 / 5

Workflow Clarity

Clear four-step sequence (Collect, Search, Create, Compare & Update) with explicit decision branches (no/one/multiple results) and a guard against overwriting non-empty fields; missing an explicit verify-after-update checkpoint keeps it at 4 rather than 5, and the destructive-overwrite guard avoids the 3 cap.

4 / 5

Progressive Disclosure

Single well-structured SKILL.md with clearly labeled sections and no nested references; no bundle files are present or needed, but at ~155 lines it exceeds the simple under-50-line exception, so it sits at the 4 "good structure" anchor rather than 5.

4 / 5

Total

16

/

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, third-person description that clearly states capability, invocation context, and comprehensive multilingual triggers. Minor specificity gap around merge/dedup semantics keeps it just short of perfect on that single dimension.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Searches by name/email, creates if missing, updates if info is incomplete" — covering the search/create/update lifecycle, but stops short of fully comprehensive coverage (no mention of merge/dedup behaviors), fitting the "several specific actions; minor gaps" anchor rather than the 5.

4 / 5

Completeness

Explicitly answers both what ("Sync a person to Apple Contacts... creates if missing, updates if info is incomplete") and when ("Designed to be called by the dispatcher after email interactions... or on demand" plus concrete trigger phrases), matching the 5 anchor and clearly above the 4 where 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Extensive natural trigger phrases across six languages ("sync contact", "add to contacts", "save contact", "update contact", "is this person in my contacts") with synonyms, matching the comprehensive-coverage anchor; the multilingual spread exceeds the 4 anchor's "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Apple Contacts) with distinct contact-specific triggers, minimal overlap risk with other skills; fits the "clear niche with distinct triggers; minimal conflict risk" anchor.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gnekt/My-Brain-Is-Full-Crew
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.