CtrlK
BlogDocsLog inGet started
Tessl Logo

akismet

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/akismet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a well-structured, executable guide to driving Akismet through the Membrane CLI, with concrete commands, a clear connection-state workflow, and good sectioning. Its main weakness is a few slightly verbose motivational phrases and the absence of an explicit post-run validation step.

DimensionReasoningScore

Conciseness

The body is largely efficient with executable commands and minimal over-explanation, though phrases like 'so you can focus on the integration logic rather than auth plumbing' and the verbose connection-state explanation are slightly more than necessary.

4 / 5

Actionability

Commands are copy-paste ready (e.g. `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{...}' --json`), the proxy section lists concrete flags, and the popular-actions table enumerates real action names with keys.

5 / 5

Workflow Clarity

There is a clear sequence (install CLI, authenticate, ensure connection, poll until READY, search actions, run) with explicit state-handling (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback loops, though it is missing a final validation checkpoint for confirming an action actually succeeded beyond reading the `output` field.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested references; it is one self-contained file, which is appropriate given no bundle files exist, though the Popular-actions table and Best practices could be trimmed further.

4 / 5

Total

17

/

20

Passed

Description

51%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 and includes both a what and an explicit when-trigger, but the actions are generic ('manage data, records, automate workflows') rather than reflecting Akismet's concrete spam-filtering capabilities. It is decent but padded with vague terms that don't match the service's real purpose.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with Akismet-specific actions like 'Check comments for spam, submit ham/spam, and verify API keys'.

Add natural trigger phrases users would actually say, e.g. 'Use when the user wants to check comments for spam, verify Akismet API keys, or manage spam/ham submissions.'

Drop the buzzword 'automate workflows', which is vague fluff that does not describe a concrete Akismet capability.

DimensionReasoningScore

Specificity

The phrase 'Manage data, records, and automate workflows' names the domain (Akismet) but the actions are generic and not specific to Akismet's actual capabilities (spam checking, key verification, ham/spam submission); the concrete actions are merely 'interact with Akismet data'.

2 / 5

Completeness

It has a clear 'what' (Akismet integration / manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Akismet data'), so both are present, though the 'when' is generic and could be more specific to spam-filtering scenarios.

4 / 5

Trigger Term Quality

'Akismet integration' and 'interact with Akismet data' surface the key brand term, but there are no natural user phrases or synonyms like 'spam', 'spam filtering', 'comment spam', or 'check for spam' that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

The Akismet brand name gives it a clear niche with minimal conflict risk versus other skills, though the generic 'manage data, records, and automate workflows' wording could overlap with other data-management skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.