affinda
Affinda integration. Manage data, records, and automate workflows. Use when the user wants to interact with Affinda data.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/affinda/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague and generic to be effective for skill selection. While it names the specific product (Affinda), it fails to describe what Affinda actually does or what specific capabilities this skill provides. The 'when' clause is circular, essentially saying 'use this when you need to use this.'
Suggestions
Replace generic terms like 'manage data, records, and automate workflows' with specific Affinda capabilities such as 'parse resumes, extract invoice data, process documents' — whatever the actual integration supports.
Expand the 'Use when...' clause with concrete trigger terms users would naturally say, e.g., 'Use when the user mentions Affinda, resume parsing, document intelligence, invoice extraction, or needs to process structured data from documents.'
Add file types or domain-specific terms that distinguish this from other data management or workflow automation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't explain what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with Affinda data'), but the 'when' is essentially circular — it just restates the product name without providing meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | It includes 'Affinda' as a keyword which is specific to the product, but lacks any natural terms users might say when needing this skill, such as 'resume parsing', 'document processing', 'invoice extraction', or other Affinda-specific capabilities. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Affinda' provides some distinctiveness since it's a specific product name, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration or data management skills. | 2 / 3 |
Total | 7 / 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.
The skill provides solid, actionable CLI commands for integrating with Affinda via Membrane, covering the full lifecycle from setup to running actions. Its main weaknesses are the introductory fluff that Claude doesn't need, the large table of actions with no descriptions adding little value, and the lack of explicit validation checkpoints for destructive operations. Tightening the content and adding verification steps would improve it significantly.
Suggestions
Remove or drastically shorten the introductory paragraph about what Affinda is — Claude already knows this, and the skill description covers it.
Either add meaningful descriptions to the popular actions table or remove it entirely and rely on the `membrane action list --intent` discovery mechanism.
Add explicit validation/confirmation guidance for destructive operations like delete-document (e.g., 'Always confirm with the user before running delete actions').
Consider extracting the popular actions table and action creation/polling details into a separate reference file to keep SKILL.md as a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'Affinda provides resume parsing and data extraction solutions. Recruiters and HR departments use it to automate resume screening...') that Claude already knows. The popular actions table with 'No description' for every entry adds bulk without value. However, the CLI commands 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, and running actions with parameters. The commands include specific flags and JSON input examples. | 3 / 3 |
Workflow Clarity | The workflow sequence (install → authenticate → connect → search/create actions → run) is present and logical, and the action creation section includes a polling/validation loop. However, there are no explicit validation checkpoints for destructive operations like delete-document, and the overall flow relies on implicit ordering rather than a clearly numbered end-to-end sequence. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the popular actions table (20 rows, all without descriptions) could be in a separate reference file. There are no references to external supplementary files for advanced usage or detailed schemas. | 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.