Name: peaka
Rating: 61.6 (1 reviews)
Author: membranedev

peaka

Peaka integration. Manage Organizations, Pipelines, Users, Filters, Files, Notes and more. Use when the user wants to interact with Peaka data.

Quality

73%

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/peaka/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 body delivers highly actionable, executable CLI guidance with a clear connection workflow and validation via state checks, but it inlines reference-style detail that would be better split into bundle files, and a few minor sequencing and validation gaps remain.

Suggestions

Extract the connection-state reference (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and the request-flag table into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Add an explicit validate/verify step after running an action (e.g., check the output schema or confirm the result before reporting success) to close the workflow validation gap.

Fix the step numbering (the body references 'Step 2' without a labeled Step 1) and trim the promotional overview paragraph that does not aid execution.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete commands and flags, though a few explanatory passages (e.g., 'Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing') and the Peaka overview blurb pad slightly beyond what is needed.	4 / 5
Actionability	Fully executable copy-paste-ready commands appear throughout (install, login, connection ensure, action list/run with --json, request proxy) plus a complete flag table, covering the common cases directly.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-checking checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling loop, but there is no validate-after-run step for action outputs and the step numbering is inconsistent (Step 2 referenced without a Step 1 label).	4 / 5
Progressive Disclosure	The single SKILL.md is reasonably sectioned, but no bundle files exist and the bulk of the connection-state reference, flag table, and action details are all inlined rather than split into clearly signaled one-level-deep reference files.	3 / 5
	Total	16 / 20 Passed

Description

67%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 covers the product domain and lists concrete managed entities with an explicit 'Use when' trigger, but relies on a single generic verb and weak trigger phrasing rather than diverse natural keywords. It is solid but not exemplary.

Suggestions

Replace the single verb 'Manage' with distinct concrete actions per entity (e.g., 'Create and update Pipelines, add and remove Users, apply Filters') to raise specificity.

Expand the 'Use when' clause with natural user phrasings and synonyms (e.g., 'Use when the user wants to query or update Peaka Organizations, Pipelines, or Users, or when they mention Peaka data').

Drop the vague 'and more' filler so the scope reads as bounded and concrete.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete entities to manage ('Organizations, Pipelines, Users, Filters, Files, Notes'), though the single verb 'Manage' covers them all rather than listing distinct actions like extract/fill/merge, leaving a minor coverage gap.	4 / 5
Completeness	Provides a clear 'what' (manage the listed entities) and an explicit 'Use when the user wants to interact with Peaka data' trigger, but the 'when' is generic and could be more specific.	4 / 5
Trigger Term Quality	Includes the product name 'Peaka' and the phrase 'interact with Peaka data' plus an entity list, but lacks the natural synonyms or phrasings a user would actually say, so relevant keywords are present with common variations missing.	3 / 5
Distinctiveness Conflict Risk	The 'Peaka' niche and entity list make it mostly distinct with minimal overlap risk against other skills, though the generic 'Manage ... and more' framing leaves a small chance of broad overlap.	4 / 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/peaka/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.