Name: podium
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

podium

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

Quality

74%

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/podium/SKILL.md

Quality

Content

82%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 highly actionable with executable commands and a well-structured connection state-machine feedback loop, held back only by minor verbosity and loose step numbering. It is a strong, navigable single-file skill.

Suggestions

Trim editorial padding (e.g. 'so you can focus on the integration logic rather than auth plumbing') and condense the marketing-style opening paragraph to a one-line domain summary.

Fix the dangling 'skip to Step 2' reference by adding an explicit 'Step 2: Search for actions' header and renumbering '1b' consistently so the workflow sequence is unambiguous.

Add a brief verification note after 'Running actions' (e.g. check the `output` field and `error` status) so non-connection workflows also have an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and a flags table, with only minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and the marketing-style Podium intro, matching anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure/get with --wait, action list/run with --input, request proxy) plus a complete flags table, matching anchor 5.	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence has a genuine feedback loop (poll BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll), but the dangling 'skip to Step 2' reference and loose '1b' numbering are minor gaps, matching anchor 4 rather than the checklist-grade anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single file is organized into clear, navigable sections (Overview, Working with Podium, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices), matching anchor 4's good structure with minor organization gaps rather than the multi-reference anchor 5.	4 / 5
	Total	17 / 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 correctly includes both a 'what' and a 'Use when' clause and is highly distinct thanks to the named Podium platform, but its action list and trigger phrasing are generic. Tightening the verbs and adding concrete user-facing terms (reviews, messages, payments) would raise it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Podium actions such as 'gather reviews, send text messages, and collect payments.'

Expand the 'Use when' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to send Podium text messages, request reviews, or collect payments.'

Add file-extension or object synonyms (e.g. 'Podium conversations, customer records, invitations') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Podium domain plus a few action verbs ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete (e.g. no 'extract,' 'send,' 'fetch'), matching anchor 3 and falling short of anchor 4's specific action list.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Podium data') are present, but the 'when' clause is generic rather than listing concrete trigger phrases, matching anchor 4 and below anchor 5.	4 / 5
Trigger Term Quality	The brand term 'Podium' is a natural keyword a user would say, but the only trigger phrasing ('interact with Podium data') misses common synonyms users actually use like reviews, text messages, payments, or reputation, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform 'Podium' gives it a clear niche with a distinctive trigger term and minimal risk of firing for an unrelated skill, matching anchor 5.	5 / 5
	Total	15 / 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/podium/SKILL.md
Commit: f484c82

Reviewed: 5 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.