CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

real-time-sync

Decide whether a page needs external changes before refresh, then use the opt-in shared SSE and polling transport safely.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./community-templates/account-expert/.agents/skills/real-time-sync/SKILL.md

The canonical home for this skill is real-time-sync in BuilderIO/agent-native

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.

The body is an efficient, actionable decision guide: a sharp opt-in rule with positive and negative cases, executable TSX examples, and project-specific transport and counter behavior that Claude could not reconstruct on its own. Its weaknesses are minor — a missing code example for changeResource routing, parallel rather than sequenced implementation guidance, and all content inline in a single file.

DimensionReasoningScore

Conciseness

The body is dense with project-specific facts Claude cannot know (poll backoff 1→2→5 min, the 2.5 s collab boost with its 3-minute lapse, source-counter semantics, endpoint behavior per host) and explains no general concepts. A few long sentences — e.g. the changeResource paragraph and the collab poll-boost paragraph — could be tightened, so it matches anchor 4 (efficient, minor trims possible) rather than 5.

4 / 5

Actionability

It provides copy-paste-ready TSX for useDbSync() and useChangeVersions()/useQuery(), an exact changeResource: (input, result) => ({ resourceType, resourceId }) signature, named endpoints, and named helper functions. It falls just short of anchor 5 because the changeResource event-routing case — one of the common cases — is described in prose without a complete code example, and the examples assume project internals a reader must already have.

4 / 5

Workflow Clarity

The decision workflow is crisp: a two-condition numbered rule, explicit opt-in cases, explicit keep-off counter-cases, then concrete implementation. No validation cap applies since this is not a destructive or batch operation. It is not 5 because the implementation half (hook → changeResource → query freshness → counters) is presented as parallel sections rather than a sequenced procedure with checkpoints.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, and no bundle files exist — everything is appropriately inline for a single-file skill. At ~135 lines it exceeds the under-50-line simple-skill case, and material such as the source-counter table and the collab poll-boost details could plausibly live in a reference file, matching anchor 4 (good structure, minor organization gaps) rather than 5 (well-signaled one-level-deep reference split).

4 / 5

Total

16

/

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 specific and appropriately third-person, with a clear niche and low conflict risk, but it lacks an explicit "Use when..." trigger clause and the natural vocabulary users would employ. It names only two of the skill's several capabilities, leaving both completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when a page must show changes made by other users, background jobs, or other tabs before the next refresh — e.g. collaborative editors, inboxes, watched jobs — not for local agent edits or read-mostly pages."

Include natural user vocabulary alongside the technical terms: "real-time updates", "live data", "auto-refresh", "cross-tab sync", "collaborative editing" — not just "SSE" and "polling transport".

Broaden the "what" to cover the skill's actual scope: the opt-in decision rule, the shared transport, and query freshness via source counters — not just "use the transport safely".

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("Decide whether a page needs external changes before refresh" and "use the opt-in shared SSE and polling transport safely"), but coverage is not comprehensive — query freshness, source counters, and invalidation behavior are absent. It is not level 4 because it does not list several specific actions with only minor gaps, and clearly above level 2 since the actions are concrete rather than generic.

3 / 5

Completeness

The "what" is stated clearly (use the opt-in shared SSE and polling transport safely), but the "when" is only weakly implied through "Decide whether a page needs external changes" — there is no explicit "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the "when" is not explicitly present.

3 / 5

Trigger Term Quality

Relevant keywords like "page", "refresh", "external changes", "SSE", and "polling" are present, but the natural phrases users would actually say ("real-time updates", "live data", "auto-refresh", "sync") are missing, and "SSE" leans technical. It matches anchor 3 (some relevant keywords, missing common variations) rather than 4, which requires good natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

The opt-in shared SSE and polling transport is a clear niche with mostly distinct triggers, carrying only minor overlap risk with closely related realtime/state-sync skills. It is not 5 because the description lacks distinct trigger phrases that would fully separate it from generic "sync" or "state management" skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

BuilderIO/agent-native

Path

community-templates/account-expert/.agents/skills/real-time-sync/SKILL.md

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.