affinity-automation
Automate Affinity tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill affinity-automation65
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/skillEvaluation — 81%
↑ 6.23xAgent success when using this skill
Validation for skill structure
Discovery
22%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 to effectively guide skill selection. It names the target platform (Affinity) but fails to specify what actions are possible or when the skill should be triggered. The meta-instruction about searching tools first is operational guidance that doesn't help with skill selection.
Suggestions
Add specific capabilities like 'Create and update contacts, manage deals, track interactions, search organizations' instead of generic 'Automate Affinity tasks'
Add an explicit 'Use when...' clause with trigger terms like 'Affinity CRM', 'relationship management', 'deal tracking', 'contact database'
Remove or relocate the meta-instruction 'Always search tools first for current schemas' as this is implementation guidance, not a description of capabilities
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Automate Affinity tasks' which is extremely vague - it doesn't specify what tasks can be automated (creating contacts, managing deals, updating records, etc.). The only concrete action mentioned is 'search tools first' which is meta-guidance, not a capability. | 1 / 3 |
Completeness | The 'what' is extremely weak ('Automate Affinity tasks' is not specific), and there is no 'when' clause at all. No explicit triggers or 'Use when...' guidance is provided, which per the rubric should cap completeness at 2 maximum, but the weak 'what' brings this to 1. | 1 / 3 |
Trigger Term Quality | Contains 'Affinity' which is a specific CRM product name users might mention, and 'Rube MCP' and 'Composio' as technical terms. However, it lacks natural user phrases like 'CRM', 'contacts', 'deals', 'relationships', or 'pipeline' that users would actually say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | 'Affinity' is a specific product name which helps distinguish it, but 'Automate tasks' is generic enough to potentially conflict with other automation or CRM-related skills. The mention of 'Rube MCP (Composio)' adds some distinctiveness but could conflict with other Composio-based skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently teaches Affinity automation through Rube MCP. It excels at workflow clarity with explicit validation steps and progressive disclosure with good organization. The main weakness is actionability - while the patterns are clear, the examples use placeholder syntax rather than concrete, executable examples with realistic values.
Suggestions
Replace placeholder arguments like '/* schema-compliant args from search results */' with concrete example values showing a realistic Affinity operation (e.g., creating a contact or updating a list)
Add one complete end-to-end example showing a specific Affinity task from search through execution with actual tool slugs and arguments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Affinity or Composio are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameter structures, but uses pseudocode-style examples rather than fully executable code. The argument placeholders like '/* schema-compliant args from search results */' reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status ('Confirm connection status shows ACTIVE before running any workflows') and addresses error recovery through the pitfalls section. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table provides efficient navigation for common operations. | 3 / 3 |
Total | 11 / 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.