Name: okra
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

okra

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

Quality

64%

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/okra/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 delivers strong actionable CLI commands and a well-validated connection workflow, with clear sectioning and no dangling file references. Its main weaknesses are minor verbosity in the introductory company description and a "Popular actions" section that repeats discovery guidance without concrete action examples.

Suggestions

Trim the opening marketing/background paragraph ("Plaid for Africa", company description) to a one-line context statement; Claude does not need Okra's company history.

Flesh out the "Popular actions" section with 2-3 concrete example action ids and sample inputs/outputs instead of restating the discovery command.

Fix the dangling "skip to Step 2" reference by labeling the search/run steps as numbered steps so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the opening "Okra is a data infrastructure company... essentially the Plaid for Africa" and "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding Claude does not need, matching anchor 3.	3 / 5
Actionability	Concrete, copy-paste-ready commands (install, login, connection ensure, action run, proxy flag table) cover the common cases, but placeholders like CONNECTION_ID and the "Popular actions" section repeating the list command without concrete action examples leave minor gaps, matching anchor 4.	4 / 5
Workflow Clarity	The connect-and-run flow is clearly sequenced with explicit state-validation feedback loops (poll until READY, branch on CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), but the dangling "skip to Step 2" reference and missing numbered step labels are minor gaps, matching anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist and the single self-contained CLI guide is well-sectioned with no buried or nested references, but the inline action/proxy reference material could justify a separate reference file, matching anchor 4 rather than the cleanly split structure of 5.	4 / 5
	Total	15 / 20 Passed

Description

61%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 clearly identifies a distinct niche (Okra) and includes an explicit trigger clause, but its capability statement relies on generic verbs ("manage data, records, automate workflows") rather than concrete actions. Trigger keyword coverage is adequate but thin on synonyms.

Suggestions

Replace generic verbs with concrete Okra capabilities, e.g. "Retrieve bank transactions, verify account balances, and fetch identity/income records via Okra."

Broaden trigger terms to include natural synonyms users might say, such as "financial data", "bank transactions", "account balance", or "African bank data".

Tighten the "Use when" clause to name specific intents, e.g. "Use when the user wants to query Okra financial data, transactions, balances, or identity records."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Okra domain but the actions are generic and minimal rather than concrete API capabilities, matching anchor 2; it falls short of 3 which requires 1-2 concrete actions.	2 / 5
Completeness	Both a "what" ("Okra integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Okra data") are present, but the trigger could be more specific, matching anchor 4.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Okra data" surfaces the relevant "Okra"/"Okra data" keywords but omits natural variations like financial data, bank transactions, or balance, matching anchor 3 rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	"Okra" is a unique named company/API, giving a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.	5 / 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/okra/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.