better-proposals-automation
Automate Better Proposals 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/better-proposals-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 integration (Better Proposals via Rube MCP/Composio) but fails to specify what actions are available or when Claude should use this skill. The operational instruction about searching tools first doesn't help with skill selection.
Suggestions
Add specific capabilities like 'Create proposals, track views, manage templates, send reminders' to clarify what actions are available.
Add a 'Use when...' clause with natural trigger terms such as 'Use when the user mentions Better Proposals, sales proposals, quotes, or proposal tracking'.
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 Better Proposals tasks' without specifying what concrete actions are possible. No specific capabilities like 'create proposals', 'track status', or 'manage clients' are mentioned. | 1 / 3 |
Completeness | The 'what' is extremely vague ('tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger. | 1 / 3 |
Trigger Term Quality | Includes 'Better Proposals' as a product name and 'Rube MCP' and 'Composio' as technical terms, but lacks natural user language. Users might say 'proposal', 'quote', or 'sales document' but these aren't included. | 2 / 3 |
Distinctiveness Conflict Risk | 'Better Proposals' is a specific product name which provides some distinctiveness, but 'Automate tasks' is generic enough to potentially conflict with other automation or proposal-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 teaches Claude how to automate Better Proposals via Rube MCP. The workflow is clearly sequenced with appropriate validation checkpoints, and the content respects token budget. The main weakness is that the tool call examples use placeholder syntax rather than fully executable examples with realistic field values.
Suggestions
Provide at least one complete, realistic example with actual Better Proposals use case (e.g., creating a proposal) showing exact arguments rather than placeholder comments like '/* schema-compliant args from search results */'
Add an example of what a successful RUBE_SEARCH_TOOLS response looks like so Claude knows what to expect and how to parse the returned schemas
| 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 Better Proposals is or how APIs work. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameter structures, but examples use placeholder syntax rather than fully executable code. The workflow steps are clear but lack complete, copy-paste ready examples with realistic values. | 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 error recovery guidance in Known Pitfalls. | 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 provides excellent 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.