activations

Query activation logs to check for errors and view volume

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./realtime-skills/activations/SKILL.md

Quality

Content

57%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 gives concrete, usable database/SQL guidance but is padded by an unnecessary intro and a verbose schema listing. Workflow steps are implicit and lack validation checkpoints for a database-query skill, and the schema could be split into a reference file.

Suggestions

Add an explicit numbered workflow (ask for the parent segment ID, construct the database name, query the activations table) with a validation step confirming results before reporting to the user.

Provide one complete copy-paste-ready example query assembling the database name, table, and TD_INTERVAL filter so the guidance is fully executable.

Trim the opening background sentence and move the full column schema to a references/ file, keeping only the key columns and their meanings inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes unnecessary explanation such as the opening 'Treasure Data's real time services include digital marketing activations...' and a verbose index/name/queryname/type schema listing with separators that could be tightened. Not a 4 because the intro padding and awkward schema format add tokens that do not earn their place; not a 2 because the bulk is still reasonably focused.	3 / 5
Actionability	Provides concrete executable guidance: database name format 'cdp_audience_394649_rt', table name 'activations', and a concrete SQL snippet 'TD_INTERVAL(time, '-1d/now')' plus column definitions and an error example. Not a 5 because no full end-to-end assembled example query is given; not a 3 because the SQL and identifiers are real and usable, not pseudocode.	4 / 5
Workflow Clarity	The implicit sequence (ask for parent segment ID, build the database name, query the activations table with a time filter) is present but not explicitly enumerated, and there are no validation checkpoints; database operations cap this at 3 per the rubric. Not a 4 because validation/feedback loops are absent; not a 2 because a recognizable sequence and preconditions are stated.	3 / 5
Progressive Disclosure	Has section structure (Requirements, Database, Activations table, Schema, Query tips) but the full column schema listing is inline content that, at over 50 lines total, could live in a separate reference file. No bundle files exist to offload it. Not a 4 because content that should be separate is inlined; not a 2 because headers provide real navigability rather than a monolithic wall.	3 / 5
	Total	13 / 20 Passed

Description

53%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 clearly states what the skill does but omits any 'when to use it' trigger guidance, capping completeness. It is reasonably specific and distinct, with a few relevant trigger terms but limited synonym coverage.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when a user asks about digital marketing activation errors, delivery volume, or activation log queries for Treasure Data.'

Expand trigger-term coverage with natural user phrasings and synonyms such as 'activation failures', 'delivery status', or 'which activations failed'.

Mention the Treasure Data / parent-segment context in the description to sharpen distinctiveness and reduce overlap with generic logging skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('activation logs') and two concrete actions ('check for errors', 'view volume'), matching the anchor that names a domain plus 1-2 actions without being comprehensive. Not a 2 because it lists specific actions beyond just naming the domain; not a 4 because there are only two actions and coverage is thin.	3 / 5
Completeness	Has a clear 'what' (query activation logs to check errors and view volume) but no 'when'/'Use when' trigger guidance, which per the guidelines caps completeness at 3. Not a 4 because there is no explicit invocation trigger; not a 2 because the 'what' is clear rather than vague.	3 / 5
Trigger Term Quality	Contains relevant keywords ('activation logs', 'errors', 'volume') but lacks common variations or synonyms a user might naturally say. Not a 4 because it misses natural phrasings like 'activations failed' or 'activation errors'; not a 2 because the terms are domain-relevant rather than purely generic.	3 / 5
Distinctiveness Conflict Risk	'Activation logs' is a fairly specific niche with distinct triggers and minimal overlap with other skills. Not a 5 because the description alone does not give strongly differentiated trigger phrases; not a 3 because it is clearly more distinct than generic 'works with logs' phrasings.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: treasure-data/td-skills
Path: realtime-skills/activations/SKILL.md
Commit: 1a0845f

Reviewed: 3 hours ago

Table of Contents

Discovery Implementation Validation

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.