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

Blog Docs Log in Get started

hootsuite

Hootsuite integration. Manage Users, Teams. Use when the user wants to interact with Hootsuite 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/hootsuite/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 body is highly actionable with a well-checkpointed connection workflow and clean section structure. Weaknesses are minor over-explanation up front and a bulky inline action table that could be externalized.

Suggestions

Trim the introductory paragraph explaining what Hootsuite is and the auth-plumbing aside; Claude already knows the platform and the CLI's value proposition.

Add a brief verification step for destructive actions (Delete Message, Reject Message), e.g. confirming the message ID or listing before deletion, to satisfy the batch/destruction validation expectation.

Consider moving the full Popular actions table into a references/ file and keeping only the 3-4 most common actions inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but opens by explaining what Hootsuite is ('Hootsuite is a social media management platform...') and adds mild padding ('so you can focus on the integration logic rather than auth plumbing') that Claude does not need.	4 / 5
Actionability	It provides copy-paste-ready commands for the full lifecycle — install, login (incl. headless), connection ensure/get with --wait, action list/run with JSON input, and proxy requests — covering the common cases concretely.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop; the minor gap is that destructive actions (Delete/Reject Message) are listed without any verification guidance.	4 / 5
Progressive Disclosure	Content is organized into clear sections with no nested or broken references, and the Popular actions table is a reasonable inline quick-reference; the gap is that the 14-row action catalog could live in a separate reference file to keep SKILL.md as an overview.	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 is distinct and includes an explicit Use-when clause, but its capability list is narrow (only Users/Teams) and the trigger phrasing is generic. Expanding both would lift the mid-range scores.

Suggestions

Broaden the capability list beyond 'Manage Users, Teams' to mention messages, social profiles, and organizations that the skill actually supports.

Replace the generic 'interact with Hootsuite data' trigger with concrete phrases users would say, e.g. 'when the user wants to schedule posts, manage social profiles, or list Hootsuite messages'.

Dimension	Reasoning	Score
Specificity	Names the domain (Hootsuite) and only 1-2 concrete actions ('Manage Users, Teams'), omitting the message/post/profile capabilities the skill actually supports, so it is not comprehensive.	3 / 5
Completeness	It has both a 'what' ('Hootsuite integration. Manage Users, Teams.') and an explicit 'when' ('Use when the user wants to interact with Hootsuite data.'), but the 'when' clause is generic rather than naming concrete trigger phrases.	4 / 5
Trigger Term Quality	The only trigger phrase is 'interact with Hootsuite data', which is a single generic keyword tied to the brand name; it lacks natural variations a user might say (posts, scheduling, social profiles).	3 / 5
Distinctiveness Conflict Risk	Hootsuite is a named third-party product, giving the skill a clear niche with distinct brand-based triggers and minimal risk of firing for an unrelated skill.	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/hootsuite/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.