Name: meetingpulse
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

meetingpulse

MeetingPulse integration. Manage Organizations. Use when the user wants to interact with MeetingPulse data.

Quality

68%

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/meetingpulse/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 body is highly actionable with copy-paste-ready CLI commands and a solid connection-setup validation loop, supported by clear section structure. Its main weaknesses are mild verbosity in the conceptual intro and a couple of broken/ orphaned step-numbering references that slightly weaken workflow clarity.

Suggestions

Trim the opening conceptual paragraph about what MeetingPulse is; Claude can infer product context, so lead directly with the integration setup.

Fix the orphaned step references — either add a labeled "Step 2" (search/run actions) and a "1a" heading, or remove the "skip to Step 2" phrasing in favor of section links.

Remove soft padding like "so you can focus on the integration logic rather than auth plumbing" to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and a useful reference table, but the opening conceptual paragraph ("MeetingPulse is a meeting engagement platform that helps presenters...") and soft phrasing ("so you can focus on the integration logic rather than auth plumbing") could be trimmed.	3 / 5
Actionability	Copy-paste-ready, fully executable commands with explicit flags cover the common cases — install, login, connection ensure/get with --wait, action list/run, and request proxying — supplemented by a complete options table.	5 / 5
Workflow Clarity	The connection setup has an explicit validation feedback loop (poll --wait, check state, retry after CLIENT_ACTION_REQUIRED), but the sequence is weakened by an orphaned "skip to Step 2" reference and a "1b" heading with no "1a".	4 / 5
Progressive Disclosure	Content is well-organized into clear ##/### sections with no nested references and easy navigation; no bundle files exist, and the inlined proxy options table is appropriately placed for a CLI integration skill, with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

62%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 third-person, includes an explicit "Use when" trigger, and names a clear niche via the product name, but it is thin on concrete actions and lacks natural synonyms (polls, Q&A, surveys). It answers both what and when, with the "when" being generic rather than trigger-rich.

Suggestions

Expand the action list beyond "Manage Organizations" to surface concrete capabilities like running polls, managing Q&A, and surveys so specificity reaches a 4-5.

Add natural trigger terms users would actually say (e.g. "polls", "Q&A", "surveys", "audience engagement") to the "Use when" clause.

Make the "when" clause more concrete, e.g. "Use when the user wants to run polls, manage Q&A, or gather real-time feedback in MeetingPulse."

Dimension	Reasoning	Score
Specificity	Names the domain (MeetingPulse) and one concrete action ("Manage Organizations"), but coverage is not comprehensive — the body reveals Meetings, Pulses, Questions, Polls, Attendees, Accounts, and Users that the description omits.	3 / 5
Completeness	Both a "what" ("MeetingPulse integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with MeetingPulse data.") are present, but the "when" is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The product name "MeetingPulse" is a relevant keyword, but natural synonyms users would say (polls, Q&A, surveys, meetings, audience engagement) are missing from the trigger clause.	3 / 5
Distinctiveness Conflict Risk	The named product "MeetingPulse" gives a clear niche with distinct triggers and minimal conflict risk, though "Manage Organizations" alone is generic enough to risk minor overlap with org-management skills.	4 / 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/meetingpulse/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.