Name: khoros-marketing
Rating: 60 (1 reviews)
Author: membranedev

khoros-marketing

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

Quality

70%

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 ./skills/khoros-marketing/SKILL.md

Quality

Content

75%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 CLI commands and a clear connection workflow including validation feedback loops. Its main weakness is a fluffy intro paragraph that explains general product knowledge, and a few dangling step references.

Suggestions

Trim the introductory paragraph about what Khoros Marketing is and who uses it; Claude does not need that background.

Label the workflow steps explicitly (Step 1a/1b/Step 2) so the "skip to Step 2" reference resolves to a real heading.

Consider moving the proxy flags table and clientAction state detail into a references file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Khoros Marketing is a social media management platform. It helps marketing teams schedule posts...") explains general product knowledge Claude does not need, and phrases like "so you can focus on the integration logic rather than auth plumbing" pad the prose.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get with --wait, action list/run with --input, and a thorough proxy flags table covering the common cases.	5 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with state-based validation checkpoints and a feedback loop (poll again after CLIENT_ACTION_REQUIRED), but the dangling "skip to Step 2" reference has no matching labeled section.	4 / 5
Progressive Disclosure	No bundle files exist, but the body is organized into well-labeled sections (Overview, Working with, Searching, Popular actions, Proxy, Best practices); the inline proxy table and clientAction state reference could optionally be split out, hence not a 5.	4 / 5
	Total	16 / 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 answers both what and when and is clearly distinct thanks to the named product, but its action language is generic and it lacks trigger synonyms. Tightening the action list and broadening the 'Use when' phrasing would raise it.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Khoros Marketing actions such as schedule posts, engage audiences, or pull analytics.

Broaden the trigger clause to include natural phrasings like 'social media management', 'scheduling posts', or 'social analytics' rather than only 'interact with Khoros Marketing data'.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Khoros Marketing domain plus a couple of semi-concrete actions, but the verbs and nouns (data, records) are generic rather than comprehensive.	3 / 5
Completeness	It states both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Khoros Marketing data"), though the trigger is somewhat narrow.	4 / 5
Trigger Term Quality	It surfaces the natural product name "Khoros Marketing" plus "data" and "workflows", but misses common synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	The product name "Khoros Marketing" is a distinct niche trigger with minimal risk of firing for unrelated skills.	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/khoros-marketing/SKILL.md
Commit: f484c82

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