abra-flexibee
ABRA FlexiBee integration. Manage data, records, and automate workflows. Use when the user wants to interact with ABRA FlexiBee data.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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, the capabilities listed are extremely vague—'manage data, records, and automate workflows' could describe almost any integration skill. It would benefit greatly from listing specific actions (e.g., create invoices, query contacts, sync orders) and adding natural trigger terms related to the domain (accounting, ERP, invoicing).
Suggestions
Replace vague actions with specific concrete capabilities, e.g., 'Create and update invoices, manage contacts, query orders, and sync accounting records in ABRA FlexiBee.'
Add natural trigger terms users might say, such as 'invoicing', 'accounting', 'ERP', 'FlexiBee API', 'business records', or specific entity names like 'faktura', 'objednavka' if Czech terms are common.
Expand the 'Use when' clause with more specific triggers, e.g., 'Use when the user mentions ABRA FlexiBee, FlexiBee API, Czech accounting software, or needs to manage invoices and business records.'
| 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' (when the user wants to interact with ABRA FlexiBee data) with an explicit 'Use when' clause, even though both parts are somewhat vague. | 3 / 3 |
Trigger Term Quality | It includes 'ABRA FlexiBee' as a key trigger term which is specific to the product, but lacks natural variations users might say (e.g., 'FlexiBee API', 'invoices', 'accounting', 'ERP', specific entity types). Users unfamiliar with the exact product name may not trigger this skill. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic and could overlap with many integration or data management skills. However, the specific mention of 'ABRA FlexiBee' provides some distinctiveness for users who name the product explicitly. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional integration skill with strong actionability — every operation has a concrete CLI command. Its main weaknesses are unnecessary introductory explanation about what ABRA FlexiBee is, and a workflow that could benefit from more explicit sequencing and validation checkpoints. The entity overview section lists entities without explaining what actions are available for each, making it feel incomplete.
Suggestions
Remove the introductory paragraph explaining what ABRA FlexiBee is — Claude doesn't need this context, and the skill description already covers it.
Add explicit numbered workflow steps showing the full end-to-end sequence (install → auth → connect → discover → run) with validation checkpoints, e.g., verifying connection success before proceeding to action discovery.
Either flesh out the entity overview with links to relevant actions/examples for each entity type, or remove it entirely since it currently adds little actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what ABRA FlexiBee is ('accounting and ERP system designed for small to medium-sized businesses...') is unnecessary context Claude doesn't need. The entity overview section is sparse but doesn't add much actionable value. However, the command examples themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command includes the exact flags and syntax needed. | 3 / 3 |
Workflow Clarity | The workflow steps are present and sequenced (install → authenticate → connect → discover actions → create/run), and the action creation flow includes a polling loop with state checks. However, there's no explicit validation or error recovery for the connection step, and the overall flow lacks numbered sequential steps or explicit checkpoints between phases. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, but it's somewhat monolithic — all content is inline in a single file. The entity overview (Company, Invoice, etc.) hints at deeper content that could be linked out but isn't. For a skill of this length (~100 lines), the organization is adequate but the entity list feels incomplete without references to more detail. | 2 / 3 |
Total | 9 / 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
56d7336
- 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.