Name: announcekit
Rating: 48.8 (1 reviews)
Author: membranedev

announcekit

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

Quality

53%

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

Quality

Content

57%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 concrete Membrane CLI commands and a clear connection-state workflow, but it loses points for inlined API reference, mild explanatory padding, and the absence of validation checkpoints before destructive operations like Delete Post.

Suggestions

Add a verification step before destructive actions, e.g. run `membrane action run get-post` to confirm the target before `delete-post`, and warn the user before executing deletes.

Move the 20-row popular-actions table into a references file (e.g. ACTIONS.md) and keep only a few representative examples inline to improve progressive disclosure.

Trim the introductory 'AnnounceKit is a changelog...' paragraph and the empty overview tree, since Claude can infer product context from the docs link.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the intro paragraph explaining what AnnounceKit is, the vague overview tree ('Use action names and parameters as needed.'), and some restated prose could be trimmed, matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a popular-actions table with real keys; minor gaps (placeholder CONNECTION_ID, no per-action input/output examples) keep it just below the fully-covered anchor 5.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but destructive actions (Delete Post, Delete Label, Delete Roadmap Issue) appear with no validation/verification checkpoint, which caps this dimension at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Content is organized into clear sections with no nested references, but the 20-row popular-actions table is reference data inlined in SKILL.md and there are no one-level-deep references to deeper material, fitting the 'some structure but reference content inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

48%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 names the product and includes an explicit 'Use when' trigger, but the capability description is generic boilerplate ('Manage data, records, and automate workflows') rather than concrete AnnounceKit actions, and it lacks synonyms like changelog or product updates.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete AnnounceKit actions, e.g. 'Create and schedule product announcements, manage roadmap issues, labels, and feedback.'

Add natural trigger synonyms such as 'changelog', 'product updates', or 'release notes' so the skill surfaces for users who don't name AnnounceKit directly.

Tighten the 'when' clause to concrete intents, e.g. 'Use when the user wants to post product updates, manage a changelog, or triage feedback in AnnounceKit.'

Dimension	Reasoning	Score
Specificity	It names the domain ('AnnounceKit integration') but the actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete AnnounceKit actions like creating posts or listing feedbacks, matching the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	Both a 'what' and an explicit 'Use when...' clause are present, but the 'what' ('Manage data, records, and automate workflows') is vague fluff and the 'when' is generic, so it sits below the clear-what-and-when anchor 4.	3 / 5
Trigger Term Quality	'AnnounceKit' is a relevant natural keyword and 'interact with AnnounceKit data' gives a usable trigger, but synonyms users might say (changelog, product updates, announcements) are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named brand 'AnnounceKit' gives a clear, distinct trigger with low conflict risk, though the generic boilerplate ('Manage data, records...') overlaps slightly with sibling Membrane integration skills, keeping it just below the minimal-conflict anchor 5.	4 / 5
	Total	12 / 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/announcekit/SKILL.md
Commit: f484c82

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