basecamp-automation

Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.

1.22x

Quality

66%

Does it follow best practices?

Impact

94%

1.22x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/basecamp-automation/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable with concrete tool sequences and parameters, but it suffers from redundancy across sections and lacks validation checkpoints for destructive operations. Splitting reference material into bundle files and de-duplicating pitfalls would improve it.

Suggestions

Add explicit verification/feedback steps to destructive workflows (e.g. after PUT_PROJECTS_PEOPLE_USERS, re-list project people to confirm the access change took effect).

De-duplicate pitfalls — keep them either inline per workflow or in the consolidated 'Known Pitfalls' section, not both — and consider moving the Quick Reference table to a references/ file to reduce token cost.

Move the bulk tool/parameter reference into a bundle file (e.g. references/quick-reference.md) and keep SKILL.md as a concise overview that links to it.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but pitfalls are stated twice (inline per workflow and again in 'Known Pitfalls') and the Quick Reference table duplicates tool slugs already listed in each workflow, which could be tightened.	3 / 5
Actionability	Concrete tool sequences with exact slugs, parameter names, types, formats, and a worked HTML example make the guidance mostly executable, with only minor gaps in example values.	4 / 5
Workflow Clarity	Sequences are clearly numbered with prerequisite/optional/required tags, but workflows involving destructive or batch operations (grant/revoke access, posting messages) lack explicit verification checkpoints, capping clarity at 3.	3 / 5
Progressive Disclosure	Well-organized sections, but the file is a ~230-line monolith with no bundle references and content (Quick Reference table, consolidated pitfalls) that could live in separate files is all inlined.	3 / 5
	Total	13 / 20 Passed

Description

75%Weight 40%Scale 1-5

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 is specific and distinctive, clearly scoped to Basecamp automation, but it lacks an explicit 'when to use' trigger clause, which limits completeness. Adding a 'Use when...' sentence would raise it to a 4–5.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to manage Basecamp projects, to-dos, messages, people, or to-do groups.'

Include a couple of natural synonyms or phrasings users might say (e.g. 'Basecamp tasks', 'Basecamp message board') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'project management, to-dos, messages, people, and to-do list organization' — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the guidelines.	3 / 5
Trigger Term Quality	Covers natural terms users would say (Basecamp, to-dos, messages, people, to-do list) but lacks synonyms or variations beyond the primary set, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to Basecamp via Rube MCP, a distinct niche with clear triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/basecamp-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.