CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dm-limits-and-best-practices

CDF Data Modeling limits: concurrency (429s), pagination, batching, search vs filter, QueuedTaskRunner, and the cap on LLM calls over query results (5 default, 50 max, cached). Triggers: DMS limits, 429, pagination, nextCursor, cdfTaskRunner, instances.query, chat completions over query results.

68

1.75x
Quality

79%

Does it follow best practices?

Impact

98%

1.75x

1 of 3 eval scenarios. Add 2 more for a full score.

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dm-limits-and-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable reference content with complete, executable TypeScript patterns for concurrency, pagination, batching, and search-vs-filter decisions. It is weakened by redundancy (the pagination pattern repeated three times), the absence of any validation/retry feedback loops for its batch write operations, and a monolithic single-file structure that inlines material that belongs in reference files.

Suggestions

Extract the QueuedTaskRunner source code and the extended pagination/query examples into a references/ file (e.g., references/semaphore.md, references/pagination.md), keeping SKILL.md as a lean overview with well-signaled one-level-deep pointers.

Add validation and retry guidance for batch operations: a 429 backoff/retry pattern around cdfTaskRunner-scheduled calls and a verification step (e.g., re-query counts) after batched upsert/delete to confirm writes landed.

De-duplicate the instances.list do-while pagination loop, which appears in three places (Pagination, Pagination + QueuedTaskRunner, and Common Pitfall #2) — keep one canonical example and cross-reference it from the pitfalls section.

DimensionReasoningScore

Conciseness

The body is mostly dense, code-first material, but at ~620 lines it includes clear redundancy — the instances.list do-while pagination loop appears three times (dedicated section, Pagination + QueuedTaskRunner section, and Pitfall #2) and the 115-line QueuedTaskRunner source is inlined — matching anchor 3's "mostly efficient but could be tightened" rather than the leaner anchor 4.

3 / 5

Actionability

Guidance is fully executable: a complete chunk utility, the full QueuedTaskRunner implementation, working pagination loops for both list and query, a search-vs-filter decision table, and batched upsert/delete patterns cover the common cases copy-paste ready, matching anchor 5. The few "/* ... */" placeholders are for project-specific view definitions, which is justified flexibility.

5 / 5

Workflow Clarity

Sections are clearly sequenced with a summary checklist, but the skill guides batch and destructive operations (batched upsert, batched delete) with no validation or verification steps — no retry/backoff on 429 despite it being the core topic, and no confirmation that writes landed — so the rubric's cap for batch operations without validation applies (anchor 3, not 4).

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers (above anchor 2's "minimal structure"), but there are no bundle files at all: roughly 400 lines of API reference patterns and the full utility source are inlined in SKILL.md where a references/ file would be appropriate, matching anchor 3's "content that should be separate is inline".

3 / 5

Total

14

/

20

Passed

Description

88%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 description: it states concrete capabilities with exact limits and provides an explicit trigger clause covering the domain's key API surface. Its only weaknesses are a few missing natural trigger synonyms (rate limit, retry, semaphore) and slight generic-term overlap risk with sibling CDF skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete capabilities — "concurrency (429s), pagination, batching, search vs filter, QueuedTaskRunner, and the cap on LLM calls over query results (5 default, 50 max, cached)" — including exact numeric limits, giving comprehensive coverage of the skill's scope with no meaningful gaps (anchor 5, not 4).

5 / 5

Completeness

The opening sentence concretely answers "what" and the explicit "Triggers: ..." clause answers "when" with concrete trigger phrases, matching anchor 5's requirement for clearly answering both what AND when.

5 / 5

Trigger Term Quality

"Triggers: DMS limits, 429, pagination, nextCursor, cdfTaskRunner, instances.query, chat completions over query results" gives good keyword coverage that fits anchor 4, but common natural variations such as "rate limit", "retry", "semaphore", or "batch" are absent, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"CDF Data Modeling limits" with distinctive tokens like nextCursor, cdfTaskRunner, and DMS defines a clear niche (above anchor 3), but generic terms like "pagination" and "429" carry minor overlap risk with closely related skills such as the referenced dm-graph-traversal, keeping it just below anchor 5.

4 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (624 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

13

/

16

Passed

Repository

cognitedata/builder-skills

Path

skills/dm-limits-and-best-practices/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.