anchor-browser-automation
Automate Anchor Browser tasks via Rube MCP (Composio). Always search tools first for current schemas.
65
51%
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/anchor-browser-automation/SKILL.mdQuality
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 is too terse and relies heavily on product-specific jargon without explaining what concrete actions the skill enables or when it should be used. It lacks natural trigger terms users would say and provides no explicit guidance for skill selection. The technical terminology may help with distinctiveness but hurts discoverability for users unfamiliar with these specific tools.
Suggestions
Add a 'Use when...' clause with natural trigger terms like 'browser automation', 'automate website', 'web tasks', 'click buttons', 'fill web forms'
List 2-3 specific concrete actions the skill can perform (e.g., 'navigate web pages, click elements, extract page content, fill forms')
Include common user phrases that would indicate need for this skill (e.g., 'automate browsing', 'control browser', 'web automation')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Anchor Browser, Rube MCP, Composio) and mentions 'automate tasks' but doesn't list specific concrete actions like 'navigate pages, fill forms, extract data'. The instruction to 'search tools first' is procedural rather than capability-describing. | 2 / 3 |
Completeness | Partially addresses 'what' (automate browser tasks) but is vague. Completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('Rube MCP', 'Composio') that users wouldn't naturally say. Missing natural terms like 'browser automation', 'web scraping', 'click', 'navigate', or 'automate website'. 'Anchor Browser' is a specific product name but lacks common variations. | 1 / 3 |
Distinctiveness Conflict Risk | The specific product names (Anchor Browser, Rube MCP, Composio) provide some distinctiveness, but 'automate browser tasks' is generic enough to potentially conflict with other browser automation or web scraping 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 Anchor Browser automation through Rube MCP. Its strengths are clear workflow sequencing, good organization, and comprehensive pitfall documentation. The main weakness is that tool call examples use placeholder syntax rather than fully concrete, executable examples with realistic argument values.
Suggestions
Replace pseudocode argument placeholders with concrete example values (e.g., show a real use case like navigating to a URL or clicking an element with actual argument values)
Add at least one complete end-to-end example showing a specific Anchor Browser task from discovery through execution with real tool slugs and arguments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Anchor Browser or Composio are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudocode-style blocks 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 with explicit sequence (discover → check connection → execute). Includes validation checkpoint for connection status ('Confirm connection status shows ACTIVE before running any workflows') and known pitfalls section addresses error prevention. | 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 | |
- 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.