Name: keka
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

keka

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

Quality

62%

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/keka/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 body is highly actionable with a well-sequenced, checkpoint-driven connection workflow, but it opens with a factually incorrect description of Keka and carries some explanatory padding that undercuts token efficiency.

Suggestions

Delete or correct the opening line 'Keka is a macOS file archiver and compressor' — it contradicts the integration framing and wastes tokens on a concept Claude already knows.

Trim motivational filler like 'so you can focus on the integration logic rather than auth plumbing' to keep the prose lean.

Consider moving the proxy request flag table and best-practices list into a reference file to slim the main SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens with an incorrect and unneeded explanation ('Keka is a macOS file archiver and compressor...') and includes filler like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need.	3 / 5
Actionability	It provides concrete, copy-pasteable commands throughout (install, login, connection ensure, action list/run, request) plus a flag table, with only minor gaps where placeholders like CONNECTION_ID and QUERY must be substituted.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear and includes state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a re-poll feedback loop, leaving only minor validation gaps.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections with no deep or buried references, but everything is inlined into a single ~140-line file with no offloading of the proxy flag table or best practices to separate files.	4 / 5
	Total	15 / 20 Passed

Description

57%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 successfully pairs a 'what' with an explicit 'Use when...' trigger and is anchored by the distinctive 'Keka' name, but its capability phrasing is vague and buzzword-laden rather than concrete.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Keka capabilities (e.g., 'pull employee records, sync attendance and leave data, run payroll reports').

Expand the trigger clause beyond 'interact with Keka data' to name natural user phrases ('employee records', 'HR data', 'attendance', 'payroll').

Tighten 'automate workflows' into a specific Keka action to remove buzzword over-claims.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Keka integration') and lists actions ('Manage data, records, and automate workflows'), but the actions are generic and abstract rather than concrete — 'automate workflows' is buzzword fluff the guidelines explicitly penalize.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Keka data'), but the 'when' clause is generic and could be more specific, fitting the score-4 anchor.	4 / 5
Trigger Term Quality	The app name 'Keka' is a strong, specific trigger and 'data, records' add some relevance, but no synonyms or natural variations are provided, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The explicit 'Keka' app name gives it a clear niche with minimal conflict risk, but the surrounding 'manage data / automate workflows' phrasing is broad enough to keep it just below the fully-distinct score-5 anchor.	4 / 5
	Total	13 / 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/keka/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.