Name: akeneo
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

akeneo

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/akeneo/SKILL.md

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 body is highly actionable with copy-paste membrane CLI commands and a well-sequenced workflow including a state-polling feedback loop. Its main weakness is conciseness, with some concept padding (PIM definition, entity list) that could be trimmed.

Suggestions

Cut the explanatory paragraph defining what Akeneo/PIM is — Claude already knows this; keep only the integration-relevant framing.

Trim or collapse the 'Akeneo Overview' entity bullet list unless it directly drives action selection; reference it only if needed.

Remove motivational prose like 'so you can focus on the integration logic rather than auth plumbing' to save tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and a flag table, but includes unnecessary explanation Claude already knows (the PIM definition, the entity bullet list, and 'auth plumbing' prose), matching anchor 3 rather than 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready membrane CLI commands (login, connection ensure, action list/run, request) with flags and JSON examples covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	Sequences install -> auth -> connect -> poll -> search -> run -> proxy with an explicit feedback loop (poll state until READY, handle clientAction, re-poll), matching anchor 5's validation checkpoints and error recovery.	5 / 5
Progressive Disclosure	A single self-contained SKILL.md with clear, well-labeled sections and no nested references, but it exceeds the simple-skill line length and inlines some reference-like bulk (entity list, flag table), fitting anchor 4.	4 / 5
	Total	17 / 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 answers both what and when with an explicit 'Use when' clause and a distinctive product name, but its listed actions are generic and it lacks PIM-specific synonyms. Strengthening it with concrete Akeneo operations and richer trigger terms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Akeneo operations, e.g. 'Manage products, attributes, categories, and families; enrich and distribute product data across channels.'

Add natural trigger synonyms users say, such as 'PIM', 'product catalog', or 'product information', in the 'Use when' clause.

Tighten the 'when' clause to list multiple concrete triggers, e.g. 'Use when the user wants to manage Akeneo product catalogs, attributes, or PIM data.'

Dimension	Reasoning	Score
Specificity	Names the Akeneo domain and lists a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete PIM-specific operations, matching anchor 3 better than 4.	3 / 5
Completeness	It states a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Akeneo data'), though the trigger could be more specific, matching anchor 4.	4 / 5
Trigger Term Quality	'Akeneo' and 'interact with Akeneo data' give some natural keywords, but common synonyms like 'PIM', 'product catalog', or 'product information' are missing, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	Anchoring on the specific product name 'Akeneo' gives a clear niche with minimal conflict risk, though the generic 'manage data, records' wording leaves minor overlap, fitting anchor 4.	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/akeneo/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.