CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rt-personalization

Create RT 2.0 Personalization services AND entities that return real-time personalized API responses. Creates both the service configuration (via tdx ps pz) and the actual Personalization entity (via API) with payload definition. Use after RT configuration is complete when user wants to "create RT personalization" or "build personalization API".

Quality

80%

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-personalization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 and exceptionally well-validated — every API call checks its HTTP status, failures print likely causes, and a verification checklist closes the workflow. Its weaknesses are token efficiency (repeated curl boilerplate and generic integration code Claude could write unaided) and the absence of any progressive disclosure: everything, including a ~60-line payload template and client integration examples, is inlined in a single 690-line file.

Suggestions

Factor the repeated curl RESPONSE/HTTP_CODE/BODY/error-handling boilerplate into a single stated pattern (e.g., 'wrap all API calls in this status-check helper') instead of repeating it verbatim in sections 2a, 2b, 2c, Verify, and the checklist — this alone saves ~70 lines.

Move the full personalization payload JSON template, the JavaScript/Node.js integration examples, and the migration-from-previous-version section into references/ files (e.g., references/payload-template.md, references/integration-examples.md) and link to them from the body, keeping SKILL.md as a lean overview of the two-step process.

Define the shell variables used in the sed substitution block ($PS_ID, $PZ_NAME, $PZ_DESC, $SINGLE_ATTR_ID, $LIST_ATTR_ID, $COUNTER_ATTR_ID) with explicit assignment steps after 2c so the entity-creation script is truly copy-paste executable.

DimensionReasoningScore

Conciseness

The core Steps 1–2 are dense with proprietary API detail Claude cannot know, but the curl RESPONSE/HTTP_CODE/BODY boilerplate is repeated verbatim roughly six times (~70 lines), and the Integration Code section, Summary Output template, and versioned Migration section add ~120 lines that could be trimmed or moved. Roughly a quarter of the body could be cut without losing actionable content.

3 / 5

Actionability

Provides complete executable bash with per-step HTTP status checks, full JSON payload and YAML templates, and sed substitution covering single/list/counter attribute cases. Falls short of fully copy-paste ready because the sed block references $PS_ID, $PZ_NAME, $PZ_DESC, $SINGLE_ATTR_ID, $LIST_ATTR_ID, and $COUNTER_ATTR_ID that are never assigned in earlier steps.

4 / 5

Workflow Clarity

The two-step process is explicitly sequenced (prerequisites check → Step 1 YAML push with service ID verification → Step 2a–2e entity creation) with HTTP-code validation and exit-on-error at every step, 'Possible causes' diagnostics, a Troubleshooting section, and a literal Verification Checklist — matching the anchor for explicit validation steps, error-recovery feedback, and checklists.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the entire ~690-line skill is one monolithic file. Section headers are well-organized, but the payload JSON template, JavaScript/Node integration examples, and migration guidance clearly belong in separate one-level-deep reference files.

3 / 5

Total

15

/

20

Passed

Description

83%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 explicitly states what the skill creates (service configuration via tdx ps pz plus the Personalization entity via API), names the mechanisms, and provides concrete quoted trigger phrases with a clear precondition. The only weaknesses are mild redundancy between the first two sentences and a few missing natural trigger synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions with tools named — 'Creates both the service configuration (via tdx ps pz) and the actual Personalization entity (via API) with payload definition' — but coverage has minor gaps (verification/testing steps are part of the skill yet unmentioned) and the first two sentences are partially redundant.

4 / 5

Completeness

Clearly answers both what ('Create RT 2.0 Personalization services AND entities that return real-time personalized API responses... with payload definition') and when ('Use after RT configuration is complete when user wants to "create RT personalization" or "build personalization API"') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes explicit natural trigger phrases — "create RT personalization", "build personalization API" — plus the precondition 'Use after RT configuration is complete', but misses common variations such as 'set up personalization' or 'real-time recommendations'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (RT 2.0 Personalization in Treasure Data CDP) with distinct quoted triggers, but has minor overlap risk with the closely related rt-config / rt-setup-personalization skill family referenced in the body.

4 / 5

Total

17

/

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

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

treasure-data/td-skills

Path

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