affinity
Affinity integration. Manage Organizations, Leads, Pipelines, Users, Roles, Filters. Use when the user wants to interact with Affinity data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill affinity75
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 adequately identifies the Affinity integration domain and includes an explicit 'Use when' clause, making it functional for skill selection. However, it lacks specificity in the actions beyond 'Manage' and could benefit from more natural trigger terms that users might say when needing CRM functionality.
Suggestions
Replace 'Manage' with specific actions like 'Create, update, search, and delete Organizations, Leads, Pipelines...' to improve specificity
Add natural trigger terms users might say: 'CRM', 'contacts', 'deals', 'relationship management', 'customer data'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Affinity) and lists entity types (Organizations, Leads, Pipelines, Users, Roles, Filters), but 'Manage' is vague - doesn't specify concrete actions like create, update, delete, search, or sync. | 2 / 3 |
Completeness | Clearly answers both what ('Manage Organizations, Leads, Pipelines, Users, Roles, Filters') and when ('Use when the user wants to interact with Affinity data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Affinity' as a key trigger and entity names users might mention, but misses natural variations like 'CRM', 'contacts', 'deals', 'relationship management', or common action phrases users would say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Affinity' is a specific product name that creates a clear niche; unlikely to conflict with other CRM or data management skills due to the explicit product reference. | 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 good actionable CLI commands for Affinity integration via Membrane, with a useful actions reference table. However, it wastes tokens on unnecessary platform description, contains a broken/incomplete overview section, and lacks validation checkpoints in the workflow. The structure is adequate but could benefit from cleanup and error handling guidance.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Affinity is - Claude doesn't need this context
Fix or remove the broken 'Affinity Overview' section which lists Document/Section/Project/Tag without explanation
Add validation steps after key commands (e.g., 'Verify connection with: membrane connection list --json | grep affinity')
Add error handling guidance for common failure scenarios (auth failures, invalid connection IDs, rate limits)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Affinity is wastes tokens on information Claude doesn't need. The 'Affinity Overview' section with Document/Section/Project/Tag is cryptic and unhelpful. However, the CLI commands and action tables are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands for installation, login, connection setup, action discovery, and running actions. The commands are copy-paste ready with clear parameter placeholders and the action table gives concrete action IDs. | 3 / 3 |
Workflow Clarity | The setup workflow (install → login → connect) is clear, but there are no validation checkpoints or error recovery steps. Missing guidance on what to do if commands fail, and no verification that connections are working before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Affinity Overview' section is incomplete/broken (just lists items with no explanation). No references to external files for advanced topics. The popular actions table could be in a separate reference file. | 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.