affinda
Affinda integration. Manage data, records, and automate workflows. Use when the user wants to interact with Affinda data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill affinda52
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
17%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 fails to explain what Affinda is or what specific capabilities it offers, relying entirely on users knowing the product name. The vague terms 'data, records, and workflows' provide no meaningful differentiation from other skills, and the circular 'Use when' clause doesn't help Claude understand when to select this skill.
Suggestions
Explain what Affinda is (e.g., 'resume parsing service', 'document intelligence platform') and list 2-3 specific actions like 'parse resumes', 'extract invoice data', or 'analyze documents'
Add natural trigger terms users would say, such as 'resume parsing', 'CV extraction', 'document AI', or whatever Affinda's actual domain is
Replace the circular 'Use when' clause with specific scenarios like 'Use when parsing resumes, extracting structured data from CVs, or processing recruitment documents'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what Affinda actually does or what specific operations are available. | 1 / 3 |
Completeness | Has a weak 'what' (manage data/records/workflows) and includes a 'Use when' clause, but the trigger condition is circular ('when the user wants to interact with Affinda data') and doesn't help Claude understand actual use cases. | 2 / 3 |
Trigger Term Quality | The only trigger term is 'Affinda' which requires users to already know the product name. Generic terms like 'data', 'records', and 'workflows' are too broad and would conflict with many other skills. | 1 / 3 |
Distinctiveness Conflict Risk | Terms like 'data', 'records', and 'automate workflows' are extremely generic and would conflict with dozens of other integration or data management skills. Only 'Affinda' provides distinctiveness. | 1 / 3 |
Total | 5 / 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 guidance for Affinda integration via Membrane CLI with executable commands throughout. The main weaknesses are some unnecessary introductory context about what Affinda is, and missing validation/verification steps in the workflows. The popular actions table is comprehensive but adds bulk that could be externalized.
Suggestions
Remove the introductory paragraph explaining what Affinda is and who uses it - Claude already knows this context
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list' after creating a connection)
Consider moving the popular actions table to a separate ACTIONS.md reference file and linking to it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., 'Recruiters and HR departments use it to automate resume screening' is context Claude doesn't need). The hierarchy diagram and best practices section add value, but some sections could be tighter. | 2 / 3 |
Actionability | Provides fully executable bash commands for all operations including installation, login, connection setup, action discovery, and running actions. The proxy request section includes concrete flag documentation and examples. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No explicit verification steps after running actions or creating connections. The workflow for 'getting list of existing connections' vs 'creating new connection' could be clearer as a decision tree. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the popular actions table is quite long and could be referenced externally. The skill is self-contained without external file references, which is acceptable for its length, but the structure could better separate quick-start from reference material. | 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.