CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/basecamp-automation/SKILL.md

The canonical home for this skill is basecamp-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable with clear, sequenced workflows and concrete parameter guidance, but it suffers from redundant content (pitfalls and tool lists repeated) and lacks any progressive disclosure into separate reference files despite its length.

Suggestions

Remove the duplicate pitfall/ID-format content: keep it in the consolidated 'Known Pitfalls' and 'Common Patterns' sections and trim the per-workflow 'Pitfalls' to unique notes only.

Split the Quick Reference table and detailed parameter catalogs into a references/ file (e.g. REFERENCE.md) linked from the body to add progressive disclosure and reduce tokens.

Add verify-after-write checkpoints in create/update workflows (e.g. re-fetch the created to-do list and confirm it appears) to lift workflow clarity toward 5.

DimensionReasoningScore

Conciseness

Content is mostly efficient and free of irrelevant concept explanations, but pitfalls and ID-format notes are stated twice (per-workflow 'Pitfalls' subsections then again in 'Known Pitfalls') and the Quick Reference table duplicates the workflow tool lists, adding tokens that could be trimmed.

3 / 5

Actionability

Numbered tool sequences, typed parameters with formats (e.g. due_on 'YYYY-MM-DD'), an enumerated color palette, and an HTML formatting example give concrete executable guidance; minor gaps in a few parameter details keep it from a 5.

4 / 5

Workflow Clarity

Each workflow has a clearly sequenced tool chain with [Prerequisite]/[Required]/[Optional] markers and the setup includes an explicit ACTIVE-status validation checkpoint, though create/update workflows lack verify-after-write feedback loops.

4 / 5

Progressive Disclosure

The ~230-line body is well sectioned but monolithic: no bundle/reference files exist and content that could live in a separate reference (the Quick Reference table, full parameter catalogs) is inlined; with no external references it has structure but no progressive disclosure depth.

3 / 5

Total

14

/

20

Passed

Description

70%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 clearly identifies a distinct Basecamp-automation niche and several concrete capabilities, with solid trigger keywords. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit usage trigger, e.g. 'Use when the user wants to automate Basecamp to-dos, messages, people access, or project organization.'

Expand trigger terms with synonyms users say ('tasks', 'checklists', 'message board', 'project access') for broader coverage.

Consider enumerating a couple more concrete actions (e.g. 'grant/revoke project access', 'color-code to-do groups') to push specificity toward 5.

DimensionReasoningScore

Specificity

Names the Basecamp domain and several concrete action areas ('project management, to-dos, messages, people, and to-do list organization'), giving good coverage though the actions are category-level rather than fully enumerated.

4 / 5

Completeness

It clearly states what the skill does ('Automate Basecamp...') but lacks any 'Use when...' trigger clause; the trailing 'Always search tools first for current schemas' is procedural, not a usage trigger, so completeness is capped at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural user terms like 'Basecamp', 'to-dos', 'messages', and 'people' are present, but common variations/synonyms (e.g. 'tasks', 'to-do lists', 'checklists') are not exhaustively covered.

4 / 5

Distinctiveness Conflict Risk

The Basecamp-specific niche and named MCP integration make it clearly distinguishable with minimal risk of triggering for unrelated skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.