CtrlK
BlogDocsLog inGet started
Tessl Logo

data-loading

Discover connected data sources, add new data connectors through a user-confirmed form, inspect table metadata, and run bounded read-only probes when the current workspace data is insufficient.

68

Quality

83%

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.

The content is lean, actionable, and well-structured with two clear sequenced workflows and explicit grounding rules. The main gap is the absence of an explicit validation/retry feedback loop for the batch-style proposal step.

Suggestions

Add an explicit validate->fix->retry feedback loop around propose_data_operation (e.g., what to do when the server rejects a plan or provenance check fails), which would lift workflow_clarity toward 5.

Tighten the 'Proposing loading options' prose slightly — the multi-sentence style guidance ('Write it as you'd say it to a colleague') could be condensed without losing the actionable rule.

If the skill grows, consider splitting the detailed grounding rules or connector/proposal guidance into a referenced file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and operational; its explanatory prose (workspace materialization semantics, read-only guarantees) is non-obvious domain knowledge rather than generic concept padding, with only minor trim opportunities.

4 / 5

Actionability

Concrete tool-call instructions are given throughout ('Call list_connectors first', 'you MUST call propose_connection', 'Use describe_data before relying on columns') with specific conditions, though they are tool-invocation guidance rather than literal copy-paste code.

4 / 5

Workflow Clarity

Two clearly numbered sequences (Adding a connector, Discovery sequence) with a reconciliation checkpoint and explicit gating, but no explicit validate->fix->retry feedback loop for the batch-like propose_data_operation step.

4 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and no nested references; appropriately self-contained, though at ~80 lines it slightly exceeds the under-50 simple-skill threshold that would warrant a 5.

4 / 5

Total

16

/

20

Passed

Description

92%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, well-triggered, and clearly bounded, with concrete actions and an explicit when-to-use clause including a negative boundary. Minor room to add a few more natural trigger synonyms, but overall strong.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Discover connected data sources, add new data connectors through a user-confirmed form, inspect table metadata, and run bounded read-only probes' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

A clear 'what' (four concrete actions) is paired with an explicit when_to_use clause giving concrete trigger phrases, plus a 'Not for...' negative boundary — explicitly answering both what and when.

5 / 5

Trigger Term Quality

The when_to_use field supplies natural phrases ('connect a database, warehouse, or cloud source', 'what connected data is available') with good synonym coverage, though a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is tightly scoped ('connected data sources', 'data connectors', 'bounded read-only probes') and the explicit 'Not for analyzing tables already listed in the workspace context' boundary minimizes conflict with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
microsoft/data-formulator
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.