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

apibible

API.Bible integration. Manage data, records, and automate workflows. Use when the user wants to interact with API.Bible 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/apibible/SKILL.md

Quality

Content

75%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 executable Membrane CLI commands and a clear connection-to-execution workflow including state validation, though it carries some unnecessary explanatory/marketing prose and a dangling "Step 2" reference.

Suggestions

Trim the introductory "API.Bible is a service that provides access..." paragraph and the "so you can focus on the integration logic" marketing phrasing to improve token efficiency.

Fix the dangling "skip to Step 2" reference by adding a matching "Step 2: Search for actions" heading or removing the step numbering.

Fill the empty Description column in the "Popular actions" table so the reference is self-contained and useful without an extra lookup.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows ("API.Bible is a service that provides access to various Bible translations...") and marketing padding ("so you can focus on the integration logic rather than auth plumbing"), matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for the full lifecycle (membrane login, connection ensure, connection get --wait, action list, action run, request) with concrete flag examples, matching the fully-executable anchor covering common cases.	5 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear with state-based validation checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the referenced "Step 2" has no matching heading and the flow is slightly scattered, fitting the clear-sequence-with-minor-gaps anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no bundle files to navigate; the inlined "Popular actions" table is minor reference material that could live separately, matching the good-structure-with-minor-gaps anchor.	4 / 5
	Total	16 / 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 correctly includes an explicit "Use when" trigger and names the API.Bible niche, but its capability list is generic ("manage data, records, automate workflows") rather than concrete Bible-specific actions, limiting specificity and trigger richness.

Suggestions

Replace generic verbs with concrete API.Bible capabilities, e.g. "Search Bible passages, retrieve verses and chapters, list translations and audio Bibles."

Expand trigger terms with natural synonyms users would say, such as "Bible verses, translations, passages, chapters, audio Bibles".

Tighten the "when" clause to name concrete intents, e.g. "Use when the user wants to look up, search, or retrieve Bible content."

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the API.Bible domain but the actions are generic ("manage data", "automate workflows") rather than concrete Bible-specific operations, fitting the anchor that names the domain but offers only minimal/generic actions.	2 / 5
Completeness	It states both a "what" ("API.Bible integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with API.Bible data"), but the "when" clause is somewhat generic and could be more specific, matching the anchor where both are present yet the when could be more explicit.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with API.Bible data" surfaces the relevant keyword "API.Bible data" but lacks natural synonyms or variations users might say (e.g., Bible verses, translations, passages), matching the anchor with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	"API.Bible integration" carves a clear niche that is unlikely to trigger for unrelated skills, though the generic "Manage data, records, and automate workflows" tail creates minor overlap risk with other integration skills, fitting the mostly-distinct 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/apibible/SKILL.md
Commit: f484c82

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