CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rt-config

Configure RT 2.0 (Real-Time Personalization) for parent segments including event tables, key events, RT attributes, and ID stitching using tdx ps rt commands or API

Quality

77%

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 ./realtime-skills/rt-config/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable with executable commands, complete configuration examples, and a sensible quick-start workflow that validates before pushing. Weaknesses are duplicated content (the ID stitching block repeated), an implicit rather than explicit error-recovery loop, and broken references to docs files that are missing from the bundle.

Suggestions

Create the referenced docs/setup-workflow.md and docs/troubleshooting.md files (or remove the 'Detailed Guides' section) — the links currently point to files that do not exist in the bundle.

Remove the duplicate ID stitching YAML block (keep it in one place, e.g., the ID Stitching section, and reference it from the Configuration Structure example).

Make the validation feedback loop explicit in Quick Start, e.g., 'If validate reports errors, fix them and re-run tdx ps rt validate before pushing' and add a post-push verification step (tdx ps view <id> --json).

Move the full API update payloads and industry Common Patterns to reference files to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

Largely code-dense with minimal prose and no explanation of concepts Claude already knows, matching 'efficient; minor instances that could be trimmed'. Not 5 because the ID stitching YAML block appears nearly verbatim twice (Configuration Structure and ID Stitching sections) and attribute examples repeat across sections.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: concrete tdx commands ('tdx ps rt validate rt_config.yaml', 'tdx api ... --method POST --data ...'), a complete YAML configuration template, and specific common-case patterns (e-commerce, media).

5 / 5

Workflow Clarity

Quick Start gives a clear sequence (check status → init → validate → push) with an explicit validation checkpoint, and a Common Errors table supports recovery. Not 5 because the validate→fix→re-validate feedback loop is implicit rather than an explicit loop, despite this being a batch configuration-push operation.

4 / 5

Progressive Disclosure

The 'Detailed Guides' section references ./docs/setup-workflow.md and ./docs/troubleshooting.md, but no docs/ directory exists in the bundle, so the references are broken; the 365-line body also inlines bulk detail (full API payloads, industry patterns) that belongs in separate files. Not 4 because broken reference links are more than a minor organization gap.

3 / 5

Total

16

/

20

Passed

Description

66%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 domain-distinct, clearly naming the four configuration components and the two tooling paths (CLI vs API). Its main weakness is the absence of any 'Use when...' trigger guidance, which both caps completeness and slightly blurs when this skill should fire versus sibling RT skills.

Suggestions

Add an explicit trigger clause, e.g., 'Use when configuring real-time personalization for a parent segment, setting up RT attributes or key events, or stitching identities across event tables.'

Add natural synonym terms users might say, such as 'real-time attributes', 'Treasure Data CDP', and 'real-time events', to improve trigger term coverage.

Sharpen the distinction from sibling skills (rt-triggers, rt-personalization) by noting this skill covers configuration/setup only, not triggers or personalization services.

DimensionReasoningScore

Specificity

Enumerates concrete components — 'event tables, key events, RT attributes, and ID stitching using tdx ps rt commands or API' — matching the several-specific-actions anchor. Not 5 because it uses a single action verb ('Configure') rather than multiple distinct concrete actions; not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Has a clear 'what' (configure RT 2.0 for parent segments with enumerated components and tooling) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage within the domain: 'RT 2.0', 'Real-Time Personalization', 'parent segments', 'ID stitching', 'tdx ps rt commands'. Not 5 because common variations are missing (e.g., 'real-time attributes', 'Treasure Data', 'CDP'); not 3 because coverage is clearly more than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche ('RT 2.0... parent segments... tdx ps rt') with mostly distinct triggers. Not 5 because the phrase 'Real-Time Personalization' creates minor overlap risk with the sibling rt-personalization skill referenced in the body.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

treasure-data/td-skills

Path

realtime-skills/rt-config/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.