airparser
Airparser integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airparser data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill airparser72
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 adequately identifies the integration and includes an explicit 'Use when' clause, which is good for completeness. However, it lacks specific concrete actions that Airparser performs (like parsing emails or extracting structured data from documents) and uses generic terms that could conflict with other data/automation skills.
Suggestions
Add specific concrete actions like 'parse emails', 'extract structured data from documents', 'configure parsing rules', or 'set up document inboxes'
Include natural trigger terms users would say such as 'email parsing', 'document extraction', 'automated data extraction', or 'parse attachments'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airparser) and mentions general actions ('manage data, records, and automate workflows'), but lacks concrete specific actions like 'create parsers', 'extract fields', or 'configure webhooks'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Airparser data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Airparser' and 'data' as keywords, but misses natural variations users might say like 'parse emails', 'extract data from documents', 'document parsing', or 'inbox parsing'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is quite generic and could overlap with many other integration or automation skills. The Airparser name provides some distinction, but the actions described are not unique. | 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 Airparser integration with good structure and a useful actions reference table. However, it includes unnecessary explanatory content about what Airparser is, and lacks validation/error handling guidance in the workflows. The content would benefit from trimming the intro and adding explicit verification steps.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Airparser is - Claude already knows this
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Include error handling guidance - what to do when membrane commands fail or return unexpected output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Airparser is, which Claude likely already knows. The content is mostly efficient but includes some unnecessary context like 'Think of it as a way to programmatically pull information out of unstructured documents.' | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with specific flags and options. The action table, proxy request examples, and connection setup commands are all copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No explicit verification steps after running actions or connecting - missing feedback loops for error recovery when commands fail. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The popular actions table and proxy options could be split into separate reference files for better navigation. | 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.