Name: tealium
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

tealium

Tealium integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tealium data.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tealium/SKILL.md

Quality

Content

67%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 delivers strong, executable Membrane CLI guidance with a well-sequenced, state-validated connection workflow and clear section structure. The main weaknesses are conceptual padding in the intro, a dangling "Step 2" reference, and an undefined <agentType> placeholder.

Suggestions

Trim the CDP intro paragraph and rhetorical asides ("so you can focus on the integration logic rather than auth plumbing") to reduce token overhead.

Resolve the dangling "skip to Step 2" reference by labeling the numbered steps consistently or removing the forward reference.

Define the <agentType> placeholder concretely (the Agent Types list appears later and is vague with "etc.") so the login command is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI command examples, but includes unnecessary conceptual padding such as the CDP intro paragraph and "so you can focus on the integration logic rather than auth plumbing." Not 4 because several passages of over-explanation could be trimmed.	3 / 5
Actionability	It provides concrete, executable membrane CLI commands (install, login, connection ensure, action run) plus a full proxy flag table. Not 5 because some guidance is discovery-directed ("Use ... to discover available actions") and placeholders like <agentType> are left undefined.	4 / 5
Workflow Clarity	Connection setup is clearly sequenced with explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-polling feedback loops. Not 5 because of a dangling "skip to Step 2" reference with no labeled Step 2 and weaker checkpointing on the action-running flow.	4 / 5
Progressive Disclosure	It is a single-file skill with well-organized section headings and no need for external references. Not 5 because it exceeds the simple-skill line count and inlines content (full proxy flag table, action discovery) that could be split into reference files.	4 / 5
	Total	15 / 20 Passed

Description

61%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 targets the Tealium niche with an explicit "Use when" trigger, but its capability list ("manage data, records, automate workflows") is generic rather than naming concrete Tealium operations. It is distinctive but lacks specificity and trigger-term breadth.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Tealium capabilities such as managing visitor profiles, consent preferences, data layers, events, and user identifiers.

Add natural trigger-term variations beyond the brand name, e.g. "Use when the user wants to query Tealium EventStream, manage AudienceStream attributes, or interact with Tealium data layers."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Tealium domain and a few actions, but every action is generic and non-concrete rather than naming specific Tealium capabilities. Not 3 because no concrete operations are enumerated; not 1 because multiple actions and the domain are named.	2 / 5
Completeness	It has both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Tealium data"). Not 5 because the "what" is vague rather than concrete; not 3 because the "when" clause is present and explicit.	4 / 5
Trigger Term Quality	"Tealium" and "interact with Tealium data" provide relevant natural keywords a user would say, but coverage is limited to the brand name with no synonyms or variations. Not 4 because there are no common variations or file extensions beyond the brand itself.	3 / 5
Distinctiveness Conflict Risk	It is tied specifically to the Tealium CDP brand with distinct triggers ("Tealium integration", "interact with Tealium data"), giving it a clear niche and minimal overlap with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/tealium/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.