airbyte
Airbyte integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airbyte data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill airbyte72
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
67%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 both what and when clauses, and identifies the Airbyte domain. However, it lacks specific concrete actions that Airbyte performs (like managing connections, syncing data sources, configuring destinations) and misses natural trigger terms users would use when working with ETL/data pipelines.
Suggestions
Add specific Airbyte actions like 'create connections', 'configure sources and destinations', 'monitor sync jobs', 'manage data pipelines'
Include natural trigger terms users would say: 'ETL', 'data pipeline', 'sync', 'connectors', 'data integration', 'extract transform load'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airbyte) and mentions general actions ('Manage data, records, and automate workflows'), but lacks specific concrete actions like 'create connections', 'sync sources', or 'configure destinations'. | 2 / 3 |
Completeness | Has both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Airbyte data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Airbyte' and 'data' as keywords, but misses common variations users might say like 'ETL', 'data pipeline', 'sync', 'connectors', 'sources', or 'destinations'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic and could overlap with other data integration or workflow automation skills. The Airbyte mention helps but the actions are too broad. | 2 / 3 |
Total | 9 / 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 Airbyte integration via Membrane, with good coverage of common operations. However, it wastes tokens explaining what Airbyte is, includes a bulky action table with empty descriptions, and lacks validation/error handling guidance that would make workflows more robust.
Suggestions
Remove the opening paragraph explaining what Airbyte is - Claude already knows this
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Either add descriptions to the action table entries or remove the table and rely on the action list --intent discovery pattern
Move the detailed action table to a separate REFERENCE.md file and keep only the most common 3-4 actions inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Airbyte is wastes tokens on information Claude already knows. The action table with 'No description' entries adds bulk without value. However, the CLI examples are reasonably tight. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, flags documented in tables, and copy-paste ready examples for all major operations including connection setup, action discovery, and proxy requests. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection flows, but lacks validation checkpoints. No guidance on verifying successful connection, handling failed syncs, or error recovery when actions fail. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the large action table could be moved to a reference file. Links to official docs exist but no internal file references for advanced topics like troubleshooting or detailed API patterns. | 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.