appsflyer-automation
Automate Appsflyer tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
53%
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 ./composio-skills/appsflyer-automation/SKILL.mdQuality
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 platform (Appsflyer) and integration method (Rube MCP/Composio) but fails to specify what actions are possible or when the skill should be triggered. The operational instruction about searching tools first doesn't help Claude decide when to select this skill.
Suggestions
Add specific Appsflyer capabilities like 'retrieve attribution data, manage campaigns, pull conversion reports, access app analytics'
Include a 'Use when...' clause with natural trigger terms such as 'mobile attribution', 'app install tracking', 'Appsflyer reports', or 'campaign performance'
Remove or relocate the operational instruction ('Always search tools first') to the skill body, as it doesn't help with skill selection
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Appsflyer tasks' without specifying what tasks can be automated. No concrete actions are listed - just generic 'tasks' and an instruction to 'search tools first.' | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Appsflyer tasks') and there is no 'when' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger. | 1 / 3 |
Trigger Term Quality | Contains domain-specific terms 'Appsflyer', 'Rube MCP', and 'Composio' which are relevant keywords, but lacks natural user phrases like 'mobile attribution', 'app analytics', 'campaign tracking', or common Appsflyer operations users would request. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Appsflyer' and 'Rube MCP (Composio)' provides some distinctiveness for this specific integration, but 'automate tasks' is generic enough to potentially conflict with other automation or Composio-related 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 guides Claude through Appsflyer automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully concrete examples with realistic values.
Suggestions
Provide at least one complete, realistic example with actual Appsflyer-specific tool slugs and arguments (even if noting they may change) to improve actionability
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what Appsflyer or Composio are. Every section serves a purpose and assumes Claude understands the underlying concepts. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but the examples are pseudocode-like structures rather than fully executable code. The argument placeholders and comments reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequence (discover → check connection → execute). Includes validation checkpoint for connection status and explicit instruction to confirm ACTIVE before proceeding. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table aids navigation. | 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 | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- 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.