CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rt-journey-activations

Configure RT journey activations - webhooks, Salesforce, email, and other integrations for real-time event-triggered actions

Quality

69%

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

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 content is a well-structured, concrete configuration reference with copy-paste JSON examples and a useful error table. Its weaknesses are verbosity from redundant per-type example variants, an implicit rather than explicit workflow with no pre-launch validation steps, and no progressive disclosure of the extensive example libraries into reference files.

Suggestions

Move the per-type example collections (webhook/Salesforce/email variants) into reference files (e.g., references/webhook-examples.md) and keep one canonical example per type in SKILL.md.

Add an explicit numbered workflow with validation checkpoints, e.g., 1. verify journey exists, 2. build activation config, 3. test with a single event, 4. verify delivery in the target system, 5. only then enable at scale.

State the mechanism for applying an activation config (API endpoint, CLI command, or console path) and replace comment-only test hints with executable commands.

DimensionReasoningScore

Conciseness

The body is mostly config reference rather than concept explanation, but it is noticeably padded: three webhook examples, three Salesforce examples, and two email examples repeat the same structure with minor variations, and generic best-practice bullets ("Include unsubscribe links", "Monitor bounce/complaint rates") state knowledge Claude already has. This fits the 'mostly efficient but could be tightened' anchor rather than score 4, and is well above score 2 since there is no extensive explanation of known concepts.

3 / 5

Actionability

Concrete, complete JSON configurations are provided for every activation type, plus a curl test command and a common-errors table, which is mostly copy-paste ready. It falls short of score 5 because the actual mechanism for applying a configuration (API call, CLI command, or tool invocation) is never shown, and the testing section is partly vague ("Use provider's test interface", "Verify credentials and object permissions") instead of executable commands.

4 / 5

Workflow Clarity

The sequence (prerequisites -> configure -> test -> monitor) is present but implicit, with no numbered steps and testing checkpoints expressed as comments rather than commands. Because the operations are outward-facing batch-style actions (Salesforce updates, mass email sends) without explicit validation/feedback loops before going live, workflow clarity is capped at 3 per the scoring notes.

3 / 5

Progressive Disclosure

The body has clear section headers and is easy to navigate, but all content — including full example libraries per activation type and the variable reference — is inlined in a single 455-line SKILL.md with no bundle files. This matches the 'content that should be separate is inline' anchor for score 3; it is above score 2 because structure is good, and below score 4 because the example collections clearly belong in per-type reference files.

3 / 5

Total

13

/

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 names a distinct niche with concrete integration types, but it lacks any 'Use when...' trigger guidance, which caps its completeness and overall effectiveness. Adding an explicit usage-trigger clause and a few more natural trigger phrases would raise it substantially.

Suggestions

Append an explicit trigger clause, e.g., 'Use when setting up event-triggered actions, outbound webhooks, Salesforce sync, or transactional email for an RT journey.'

Add natural trigger synonyms users might say, such as 'HTTP callback', 'notification', or 'event action', to broaden trigger term coverage.

Replace the vague 'and other integrations' with the actual remaining activation types (e.g., 'Custom integrations') to make coverage concrete.

DimensionReasoningScore

Specificity

The description lists several specific actions and integration types ("Configure RT journey activations - webhooks, Salesforce, email"), but the trailing "and other integrations" leaves coverage open rather than comprehensive, matching the 'several specific actions; minor gaps' anchor. It is above score 3 because it names more than 1-2 concrete actions, and below score 5 because it does not enumerate the full set of concrete actions.

4 / 5

Completeness

The 'what' is clear (configure RT journey activations for webhooks, Salesforce, email, and other integrations), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not score 2 because the 'what' is concrete and specific, and not score 4 because 'when' is entirely absent rather than merely weakly implied.

3 / 5

Trigger Term Quality

Natural trigger terms are present ("webhooks", "Salesforce", "email", "integrations", "real-time", "event-triggered"), giving good keyword coverage a user would plausibly say. A few natural variations are missing (e.g., "HTTP request", "notification", "event actions"), so it fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive score 5.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct ('RT journey activations' with named integration types), so it is unlikely to trigger for unrelated skills. Minor overlap risk remains with generic email-, Salesforce-, or webhook-configuration skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict score 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

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/rt-journey-activations/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.