Name: harmonic
Rating: 65.60000000000001 (1 reviews)
Author: membranedev

harmonic

Harmonic integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Harmonic data.

Quality

78%

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/harmonic/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 CLI commands and a well-sequenced, state-aware workflow. It is efficient and well-organized, with only minor over-explanation and an unanchored "Step 2" reference.

Suggestions

Remove the opening "Harmonic is a SaaS platform for video streaming..." gloss and the "so you can focus on the integration logic rather than auth plumbing" filler to tighten conciseness.

Replace the dangling "Step 2" references with explicit numbered steps or in-section anchors so the workflow sequence is unambiguous.

Move the static Popular actions and proxy-flag tables into a references file to keep SKILL.md a lean overview and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is command-heavy and mostly efficient (install, login, connection, search, run, proxy), with only minor over-explanation such as the introductory "Harmonic is a SaaS platform..." line and "so you can focus on the integration logic rather than auth plumbing."	4 / 5
Actionability	Copy-paste-ready commands are provided throughout (npm install, membrane login, connection ensure, action list/run, request) with flags, JSON output, and a Popular actions table mapping names to keys, fully covering common cases.	5 / 5
Workflow Clarity	A clear install→auth→connect→poll→search→run sequence exists with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but references to "Step 2" are not anchored to any numbered step, leaving minor navigation gaps.	4 / 5
Progressive Disclosure	The single-file content is well-sectioned (Overview, Working with Harmonic, Popular actions, Best practices) with no nested or buried references, but it exceeds 50 lines so the simple-skill full-score exception does not apply and no detail is offloaded to bundle files.	4 / 5
	Total	17 / 20 Passed

Description

75%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 concise, third-person, and answers both what and when with a clear trigger clause. It is solid but stops short of comprehensive, distinct action verbs and exhaustive natural trigger synonyms.

Suggestions

Replace the single generic "Manage" verb with a few distinct concrete actions (e.g., "Create and update Pipelines, assign Goals to Users, filter Organizations") to lift specificity.

Expand the "Use when" clause with concrete user phrasings (e.g., "when the user wants to query Harmonic people/companies, run saved searches, or browse company employees").

Add at least one file-format or domain qualifier to the trigger to reduce overlap with generic CRM-style skills.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Goals, Filters" lists several specific entity-actions rather than vague abstraction, though a single generic "Manage" verb applied to a noun list leaves minor coverage gaps versus distinct concrete actions.	4 / 5
Completeness	Both "what" (Harmonic integration, manage the listed entities) and an explicit "Use when the user wants to interact with Harmonic data" trigger are present; the "when" clause is explicit but somewhat generic.	4 / 5
Trigger Term Quality	Concrete entity keywords (Organizations, Pipelines, Users, Goals, Filters) plus "interact with Harmonic data" give good natural-term coverage, but common user phrasings or synonyms for each entity are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	The Harmonic niche is clearly named and distinct, but the entity list (Organizations, Pipelines, Users, Goals, Filters) is fairly generic CRM-style vocabulary that could mildly overlap with related skills.	4 / 5
	Total	16 / 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/harmonic/SKILL.md
Commit: f484c82

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