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

makelog

Makelog integration. Manage data, records, and automate workflows. Use when the user wants to interact with Makelog 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/makelog/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 content is highly actionable with executable Membrane CLI commands and a clear, state-driven connection workflow with retry loops. Its weaknesses are mild verbosity in the intro and a couple of placeholder lines, plus a dangling 'Step 2' reference and no validation checkpoint before action execution.

Suggestions

Trim the marketing-style intro ('Makelog is a changelog and release notes tool for software development teams. It helps them automate the process...') and the vague 'When to use which actions' line to assume Claude's competence.

Label the 'Searching for actions' section as 'Step 2' (or remove the dangling 'Step 2' references) so the workflow sequence is unambiguous.

Add an explicit validation/verification checkpoint before running actions (e.g. confirm the connection is READY and re-check the action inputSchema) to strengthen the workflow for batch or destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command examples, but it includes unnecessary padding such as the marketing-style intro paragraph ('Makelog is a changelog and release notes tool...') and the vague filler line 'When to use which actions: Use action names and parameters as needed.'.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure, polling, action run with JSON input) plus a flag table, covering the common cases concretely.	5 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with an explicit state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-retry feedback loop, but the 'Step 2' reference is unlabeled and there is no validation checkpoint before executing actions.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections with no nested references and no bundle files to navigate, which is appropriate for a self-contained skill; minor gaps are the inlined proxy flag table and best-practices prose that could live in reference files.	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 clearly identifies the Makelog niche and includes an explicit 'Use when' trigger, satisfying both the what and when requirements. Its main weakness is generic action vocabulary that undersells Makelog-specific capabilities and misses natural synonyms like 'changelog' and 'release notes'.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Makelog capabilities such as 'create releases, manage changelog entries, and publish release notes'.

Add natural trigger synonyms users actually say, e.g. 'Use when the user wants to manage changelogs, release notes, or product updates in Makelog'.

Tighten the 'when' clause to reference specific Makelog artifacts (releases, entries) rather than the broad 'interact with Makelog data'.

Dimension	Reasoning	Score
Specificity	Names the Makelog domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Makelog capabilities like releases or changelog entries, so coverage is not comprehensive.	3 / 5
Completeness	It states both what the skill does ('Makelog integration. Manage data, records, and automate workflows.') and when to use it ('Use when the user wants to interact with Makelog data'), though the 'when' clause is somewhat generic.	4 / 5
Trigger Term Quality	'Makelog' is a natural trigger term, but the accompanying keywords ('data', 'records', 'workflows') are generic and miss common variations users would say, such as 'changelog' or 'release notes'.	3 / 5
Distinctiveness Conflict Risk	Naming the niche app 'Makelog' makes it mostly distinct and unlikely to trigger for unrelated skills, though the broad 'interact with Makelog data' phrasing leaves minor overlap risk with generic data 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/makelog/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.