CtrlK
BlogDocsLog inGet started
Tessl Logo

dm-limits-and-best-practices

Reference skill for CDF Data Modeling API best practices. Covers concurrency limits (avoiding 429s), pagination patterns for instances.list and instances.query, batching write operations, search vs filter guidance, and the QueuedTaskRunner (Semaphore) utility for controlling concurrent requests. Triggers: DMS limits, 429 error, rate limit, pagination, cursor, nextCursor, batching, semaphore, QueuedTaskRunner, cdfTaskRunner, instances.search, instances.list, instances.query, instances.upsert, concurrency, deadlock.

79

1.69x
Quality

Does it follow best practices?

Impact

95%

1.69x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable reference with concrete, executable patterns and a useful pitfalls section, weakened by redundancy across pagination examples and a monolithic single-file structure with no progressive disclosure.

Suggestions

Move the full QueuedTaskRunner source and verbose API patterns into a references/ file (e.g. SEMAPHORE.md) and keep SKILL.md as an overview with one-level-deep links, improving progressive_disclosure.

Remove the redundant "Pagination + QueuedTaskRunner Combined" example or fold it into the existing pagination examples to tighten conciseness.

Add an explicit verify/retry checkpoint to the batched upsert and delete workflows (e.g. confirm counts or retry on 429) to raise workflow_clarity above 2.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but it repeats patterns: instances.list pagination appears in both the Pagination section and the "Pagination + QueuedTaskRunner Combined" section, and the final Summary Checklist restates guidance already in the body.

2 / 3

Actionability

Provides fully executable TypeScript (e.g. the chunk utility, batched upsert/delete, pagination loops), concrete limit values (1000), and a decision-guide table — copy-paste ready.

3 / 3

Workflow Clarity

Steps for pagination, batching, and deletes are clearly sequenced, but batch/destructive operations lack explicit validate-then-retry checkpoints, which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Sections are well-organized, but the file is a ~600-line monolith with the full QueuedTaskRunner source and API patterns all inline and no bundle files to split detail into — content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

100%

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, third-person, and explicitly pairs capabilities with a comprehensive trigger clause. It is a strong, low-conflict description for a reference skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "concurrency limits (avoiding 429s), pagination patterns for instances.list and instances.query, batching write operations, search vs filter guidance, and the QueuedTaskRunner (Semaphore) utility", matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers both what (the covered capabilities) and when (the explicit "Triggers:" clause), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

An explicit "Triggers:" clause lists natural terms a user would say — "429 error, rate limit, pagination, cursor, nextCursor, batching, semaphore, QueuedTaskRunner, cdfTaskRunner, instances.search" — giving broad coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (CDF Data Modeling API limits/concurrency) with distinct, domain-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (617 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
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.