Name: basecamp
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

basecamp

Basecamp integration. Manage Projects, Persons, Clients. Use when the user wants to interact with Basecamp data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/basecamp/SKILL.md

Quality

Content

67%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 a strong, mostly executable guide with a genuinely well-sequenced connection workflow and clear sections, weakened mainly by mild explanatory padding up front and a large inline action table that could be split out. It is close to the top anchors on actionability and workflow clarity.

Suggestions

Cut the opening 'Basecamp is a project management...' paragraph and the 'so you can focus on the integration logic rather than auth plumbing' aside; assume Claude knows what Basecamp is.

Move the full Popular actions table into a references/actions.md file and link to it, keeping only a few representative examples inline.

Add an explicit validation step after running actions (e.g. check the response `output`/`error` fields before proceeding) to turn the run workflow into a closed feedback loop.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opening paragraph explaining what Basecamp is ('project management and team communication tool...') and editorial phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	Concrete, copy-pasteable commands populate every section (membrane login, connection ensure, action list/run, request) plus full action and flag tables, with only minor placeholders like <actionId> and <id> keeping it just short of fully executable across all cases.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops (poll again, check error field), missing a 5 only because recovery steps for CLIENT_ACTION_REQUIRED are described rather than scripted.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections with no nested references and no bundle files to misroute, though the large 20-row Popular actions table is content that arguably belongs in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

62%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 cleanly answers what the skill does and when to use it with a concrete third-person voice and a clear app-specific niche, but it leans on the generic verb 'Manage' and offers limited trigger-term variety. Tightening the action list and adding synonyms would lift it toward the top anchors.

Suggestions

Replace the generic 'Manage Projects, Persons, Clients' with concrete verbs the skill performs (e.g. 'List, create, and update Projects, To-dos, Messages, and People').

Expand the trigger clause with natural synonyms users say, e.g. 'Use when the user wants to work with Basecamp projects, to-do lists, messages, or campfire chats.'

Add the key entity terms from the body (to-dos, message boards, campfire) to the description so the trigger matches more user phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain ('Basecamp') and concrete entities ('Manage Projects, Persons, Clients'), but 'Manage' is a generic verb with no detail on the actual operations, so coverage is partial rather than comprehensive.	3 / 5
Completeness	Both 'what' ('Manage Projects, Persons, Clients') and an explicit 'when' ('Use when the user wants to interact with Basecamp data') are present, matching the anchor that has both but where the 'when' could be more specific.	4 / 5
Trigger Term Quality	The natural keyword 'Basecamp' appears and the trigger 'interact with Basecamp data' is reasonable, but it lacks synonyms or variations users might say (e.g. to-dos, messages, project management), leaving keyword coverage incomplete.	3 / 5
Distinctiveness Conflict Risk	'Basecamp' is a specific named application giving a clear niche and distinct trigger, but the single generic 'interact with Basecamp data' phrasing leaves minor overlap risk with adjacent project-management skills rather than minimal risk.	4 / 5
	Total	14 / 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: membranedev/application-skills
Path: skills/basecamp/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.