Name: ikas
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ikas

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

Quality

66%

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

Quality

Content

67%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 concrete Membrane CLI commands, a clear connection-state workflow, and good section organization. It loses points to marketing-style intro padding, placeholder-heavy examples, and slightly inconsistent step numbering.

Suggestions

Trim the marketing intro and the "focus on the integration logic rather than auth plumbing" aside to nothing; keep only the factual statement that Membrane handles auth.

Fix the step numbering (remove the orphan "Step 2" / "1b" references) or renumber the connection flow as a proper ordered list.

Add one fully-worked action example with real values (a concrete intent and actionId) alongside the placeholder versions so the common case is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and a flag table, but the intro ("streamline operations, improve efficiency, and reduce manual effort") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action list/run, and proxy requests plus a full flag table, but several examples rely on generic placeholders (QUERY, actionId, CONNECTION_ID) without a fully worked real-value example.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear with explicit state checks and feedback loops (poll until not BUILDING, re-poll after user action, inspect error field), but inconsistent numbering ("Step 2", "1b") leaves minor gaps.	4 / 5
Progressive Disclosure	A single well-sectioned file with clear headers and no nested references; minor redundancy where "Popular actions" repeats the same action-list command already shown in "Searching for actions".	4 / 5
	Total	15 / 20 Passed

Description

66%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 clear and distinct, naming a specific platform with both a what and a when clause in third-person voice. It is held back by generic action verbs and a thin set of trigger keywords beyond the product name.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Ikas-specific actions such as "enroll students, manage courses and teachers, process payments".

Expand the "Use when" clause with natural trigger phrases a user would say, e.g. "Use when the user wants to manage Ikas enrollments, courses, teachers, or payments".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Ikas domain plus a few actions, but the actions are generic ("manage data", "records") rather than concrete, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Ikas data"), but the when clause is somewhat generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural keywords are "Ikas" and "Ikas data" (the app name); there are no synonyms, task phrases, or file extensions a user might say, matching the anchor with some relevant but incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"Ikas integration" and the "Ikas data" trigger name a specific platform niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/ikas/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.