api-bible-automation
Automate API Bible tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/api-bible-automation/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague to effectively guide skill selection. It fails to specify what concrete actions the skill performs with the API Bible service and lacks explicit trigger conditions. The technical product names provide some distinctiveness but don't help users naturally discover this skill.
Suggestions
Add specific concrete actions like 'Fetch Bible verses, search passages by keyword, retrieve available translations and books'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about Bible verses, scripture lookup, biblical passages, or needs to access Bible API data'
Replace vague 'tasks' with enumerated capabilities that users would actually request
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate API Bible tasks' without specifying what concrete actions are performed. No specific capabilities like 'fetch verses', 'search passages', or 'retrieve translations' are mentioned. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate API Bible tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('API Bible', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations like 'Bible verses', 'scripture', 'biblical text'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'API Bible' and 'Rube MCP (Composio)' provides some specificity to distinguish from generic automation skills, but 'tasks' is too broad and could overlap with other Composio-based skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently guides Claude through API Bible automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content is appropriately concise. The main weakness is that tool call examples use a pseudo-code format rather than showing actual executable syntax, which slightly reduces actionability.
Suggestions
Convert tool call examples to actual executable format (e.g., show the exact MCP tool invocation syntax or JSON payload structure) rather than pseudo-code blocks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what API Bible is or how MCP works. Every section serves a purpose and assumes Claude's competence with the underlying concepts. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but uses pseudo-code style rather than fully executable examples. The tool calls show structure but aren't copy-paste ready since they're not in a specific language syntax. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status and explicit guidance to confirm ACTIVE status before proceeding. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides at-a-glance navigation. External toolkit docs linked appropriately without deep nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- Reviewed
Table of Contents
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.