abra-flexibee
ABRA FlexiBee integration. Manage data, records, and automate workflows. Use when the user wants to interact with ABRA FlexiBee data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/abra-flexibee/SKILL.mdQuality
Discovery
57%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 identifies the product (ABRA FlexiBee) and includes an explicit 'Use when' clause, which is good for completeness. However, it is severely lacking in specificity—it doesn't mention any concrete actions like creating invoices, managing contacts, syncing inventory, or querying financial records. The trigger terms are limited to the product name without covering related natural language terms users might use.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Create and update invoices, manage contacts, query inventory, and sync financial records in ABRA FlexiBee.'
Expand trigger terms to include natural language variations and related concepts users might mention, such as 'invoices', 'accounting', 'ERP', 'FlexiBee API', 'orders', 'warehouse management'.
Improve distinctiveness by specifying the domain (e.g., 'Czech ERP/accounting system') and the types of entities or workflows supported to differentiate from other data management or integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions. It doesn't specify what kinds of data, records, or workflows are involved beyond the ABRA FlexiBee context. | 1 / 3 |
Completeness | It answers both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with ABRA FlexiBee data) with an explicit 'Use when...' clause, though both parts are somewhat thin on detail. | 3 / 3 |
Trigger Term Quality | It includes 'ABRA FlexiBee' as a key trigger term which is specific to the product, but lacks natural variations or related terms users might say (e.g., 'invoices', 'accounting', 'ERP', 'FlexiBee API', specific entity types). Users unfamiliar with the exact product name might not trigger this skill. | 2 / 3 |
Distinctiveness Conflict Risk | The ABRA FlexiBee product name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration or data management skills. Without specifying the types of operations (e.g., invoicing, inventory, contacts), it risks conflicting with other ERP/accounting integrations. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity—the connection setup flow with state handling is particularly well done. The main weaknesses are some unnecessary introductory content (explaining what FlexiBee is, listing entities without context) and a slightly monolithic structure that could benefit from tighter editing and better progressive disclosure.
Suggestions
Remove the introductory paragraph explaining what ABRA FlexiBee is and who uses it—Claude doesn't need this context to execute the integration.
Either remove the entity overview section (Company, Invoice, etc.) or make it actionable by linking each entity to example action queries or common action IDs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what ABRA FlexiBee is (accounting/ERP system, who uses it) is unnecessary context Claude doesn't need. The overview section listing entities without any actionable detail adds little value. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and flags documented in a table. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, SETUP_FAILED). It includes polling/retry loops for BUILDING state and clear instructions for each possible outcome, forming a proper feedback loop. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic for its length. The entity overview (Company, Invoice, etc.) is listed without linking to any detailed documentation or examples. No bundle files are provided, so there's no external reference structure, though the skill could benefit from splitting proxy request details or best practices into separate files. | 2 / 3 |
Total | 10 / 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
- membranedev/application-skills
- Commit
f484c82
- 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.