Name: ikigai
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ikigai

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

Quality

70%

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

Quality

Content

78%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 commands and real validation feedback loops, but it is held back by inconsistent step numbering (dangling "Step 2" references) and a monolithic structure with no progressive split for a 140-line skill. Tightening the intro and fixing the step labels would notably improve it.

Suggestions

Resolve the dangling "Step 2" references: either label the action-running section as Step 2 or renumber the flow consistently so "skip to Step 2" points to a real heading.

Move the detailed clientAction state machine and the proxy flags table into reference files (e.g. REFERENCES/connection-states.md) and link to them, so SKILL.md stays an overview.

Trim the introductory "Ikigai is a life purpose and career planning app..." paragraph and editorial asides to reduce tokens that don't aid execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with each flag table and example earning its place, but the introductory "what Ikigai is" paragraph and a few editorial sentences ("so you can focus on the integration logic", "This is the fastest way") are trimmable padding.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get with --wait, action list/run with --input, request with a complete flag table), covering the common cases with real parameters and --json output.	5 / 5
Workflow Clarity	There is a clear install → login → connect → poll → search → run sequence with validation checkpoints (state polling, CLIENT_ACTION_REQUIRED feedback, re-poll after user action), but the "skip to Step 2" references point to a step that is never labeled and section numbering is inconsistent.	4 / 5
Progressive Disclosure	Sections are clearly headed and navigable, but the ~140-line body is monolithic with no bundle files; content that could be split out (the detailed clientAction state machine, the proxy flags table) is inlined rather than referenced one level deep.	3 / 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 is functional and clearly identifies the product niche with an explicit "Use when" trigger, but its capability verbs are generic and it lacks synonym/extension coverage. Strengthening the action list would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete actions the skill actually performs, e.g. "Create and update records, search Ikigai data, and run workflows."

Add natural trigger synonyms and phrasings users might say, such as "Ikigai records," "Ikigai workflows," or "query Ikigai," to improve trigger term coverage.

Make the "what" clause more specific so it reads as capabilities rather than a category description.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete; it does not reach the "several specific actions" level of a 4.	3 / 5
Completeness	It states both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Ikigai data"), but the "what" is generic enough to fall short of a 5.	4 / 5
Trigger Term Quality	It includes relevant natural keywords ("Ikigai data", "interact with Ikigai") but lacks common variations, synonyms, or file extensions, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The product name "Ikigai" gives the skill a clear niche and distinct trigger, but the generic action phrasing (manage data, automate workflows) leaves minor overlap risk with other 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/ikigai/SKILL.md
Commit: f484c82

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