abra-flexibee
ABRA FlexiBee integration. Manage data, records, and automate workflows. Use when the user wants to interact with ABRA FlexiBee data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill abra-flexibee75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 successfully identifies a specific product (ABRA FlexiBee) and includes an explicit 'Use when' clause, making it complete and distinctive. However, the capabilities listed are vague ('manage data', 'automate workflows') and could benefit from more concrete actions specific to FlexiBee's functionality. The trigger terms rely heavily on the product name without covering related terminology users might use.
Suggestions
Add specific concrete actions that FlexiBee supports, such as 'create invoices, manage inventory, track orders, handle accounting entries'
Include related trigger terms users might naturally say, such as 'ERP', 'accounting software', 'Czech business software', or specific FlexiBee modules
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ABRA FlexiBee) and mentions general actions ('Manage data, records, and automate workflows'), but these actions are not concrete or comprehensive - 'manage data' and 'automate workflows' are fairly generic. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with ABRA FlexiBee data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'ABRA FlexiBee' which is the specific product name users would mention, but lacks common variations or related terms users might say (e.g., 'FlexiBee API', 'accounting software', 'ERP', 'invoices', 'inventory'). | 2 / 3 |
Distinctiveness Conflict Risk | ABRA FlexiBee is a specific product name that creates a clear niche; unlikely to conflict with other skills since the trigger is tied to this particular software system. | 3 / 3 |
Total | 10 / 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 skill provides solid, actionable CLI commands for ABRA FlexiBee integration via Membrane, with good coverage of setup, connection, and action execution. However, it wastes tokens on unnecessary product explanations, lacks validation/error handling guidance in workflows, and the 'Popular actions' section is misleadingly empty. The structure is adequate but could better leverage progressive disclosure.
Suggestions
Remove the opening paragraph explaining what ABRA FlexiBee is - Claude doesn't need this context
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Either populate the 'Popular actions' section with actual common action IDs/examples, or remove the misleading header
Add error handling guidance for common failure scenarios (auth failures, invalid action IDs, API errors)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what ABRA FlexiBee is wastes tokens on information Claude doesn't need. The overview section listing entities without context adds little value. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags documented, and the proxy request section includes a useful options table. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are listed but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. Missing feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Popular actions' section is oddly empty except for discovery commands. Could benefit from linking to external references for advanced proxy usage or action catalogs. | 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 | |
- 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.