Name: heysummit
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

heysummit

HeySummit integration. Manage Summits. Use when the user wants to interact with HeySummit data.

Quality

66%

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

Quality

Content

71%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 is highly actionable with copy-paste CLI commands and a well-sequenced connection workflow including state-based feedback loops, but it carries some marketing padding and inlines reference-grade material that would benefit from separation into bundled files.

Suggestions

Trim the marketing overview of HeySummit's audience and the vague agent-types note; assume Claude knows the CLI tooling context and keep only task-relevant detail.

Move the clientAction state schema and the proxy-flag reference table into a references/ file (e.g. references/connection-states.md) and link to it from SKILL.md so the main file stays an overview.

Label the workflow steps explicitly (e.g. '## Step 2: Find and run actions') so the 'skip to Step 2' reference resolves to a real heading.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command references, but the marketing-style overview ("used by marketers, entrepreneurs, and educators to share knowledge, generate leads, and build community") and the awkward agent-types note pad sections Claude does not need, fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure/get, action list/run, request proxy) with flags documented and a popular-actions table, matching the score-5 anchor of fully executable examples covering common cases.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll/state-machine→search→run sequence with explicit polling feedback loops and per-state handling, but the "skip to Step 2" reference points to no labeled Step 2, a minor sequencing gap keeping it at 4.	4 / 5
Progressive Disclosure	Section headers are clear and logically ordered, but the skill is monolithic: the detailed clientAction state schema, proxy-flag reference table, and popular-actions table are all inlined with no one-level-deep reference files, matching the score-3 anchor of content that should be separate being inline.	3 / 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 is well-targeted with an explicit 'Use when' trigger and a highly distinctive named-product niche, but its capability statement is generic ('Manage Summits') and lacks concrete action verbs or keyword variations.

Suggestions

Replace the generic 'Manage Summits' with concrete actions, e.g. 'Create and manage summits, talks, speakers, attendees, and reports' to lift specificity.

Add natural keyword variations a user might say, such as 'HeySummit events', 'summit attendees', or 'HeySummit talks', to broaden trigger coverage.

Tie the 'Use when' clause more tightly to those concrete entities, e.g. 'Use when the user wants to manage HeySummit summits, talks, attendees, or reports.'

Dimension	Reasoning	Score
Specificity	The phrase "Manage Summits" names the domain but offers only a single generic verb; it does not enumerate concrete actions like create, list, update, or delete, which fits the score-2 anchor of naming the domain with minimal/generic actions.	2 / 5
Completeness	It states what it does ("HeySummit integration. Manage Summits.") and gives an explicit "Use when the user wants to interact with HeySummit data" trigger, satisfying both what and when; the 'what' could be more specific, so it lands at 4 rather than 5.	4 / 5
Trigger Term Quality	It surfaces the core natural term ("HeySummit") plus "Summits" and "HeySummit data", but offers no synonyms, common variations, or related phrases, matching the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	HeySummit is a specific named SaaS product with a clear niche and distinct triggers ("HeySummit data", "Summits"), giving minimal overlap risk 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/heysummit/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.