Name: buddy
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

buddy

Buddy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Buddy data.

Quality

57%

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/buddy/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 skill is action-dense with strong executable commands and a solid connection workflow, but it over-explains basics, omits verification for destructive record updates, and keeps reference material inline. It is practical but would benefit from tightening and a validation step.

Suggestions

Add a verification step after running Update/create actions (e.g. re-query the record or check the action output) to satisfy the destructive/batch validation requirement.

Move the proxy flag reference table and action-discovery details into a separate REFERENCES.md and link to it from the body to improve progressive disclosure.

Trim the introductory explanation of what Buddy is and the "focus on integration logic" aside, and make the Buddy Overview list reference concrete action names instead of "Use action names and parameters as needed".

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, but the Buddy-is-a-CI/CD-tool intro, the "focus on integration logic rather than auth plumbing" aside, and the terse vague Buddy Overview list add explanation Claude does not need and could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxying; the only gap is the Overview's vague "Use action names and parameters as needed" guidance, which is not executable.	4 / 5
Workflow Clarity	The connection setup is well sequenced with state checks and a poll/retry feedback loop, but the core Update operations on goals, habits, tasks, and journal entries are modifying/destructive with no verification step, which caps workflow clarity; "skip to Step 2" also references an unlabeled step.	3 / 5
Progressive Disclosure	There are no bundle files and content is a single monolithic SKILL.md; headers give reasonable structure, but reference-like material (the proxy flags table, action discovery) is inlined rather than split into clearly signaled one-level-deep references.	3 / 5
	Total	13 / 20 Passed

Description

57%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 answers both what and when and is anchored to a distinct product, but its capability list is generic rather than concrete and the trigger terms lack synonyms. It is competent but not sharply specific.

Suggestions

Replace generic verbs with concrete Buddy actions, e.g. "Create and update goals, habits, tasks, and journal entries" instead of "Manage data, records, and automate workflows".

Add natural trigger synonyms a user might say (e.g. "goals", "habits", "task tracking", "journal") to the Use-when clause.

Name the specific record types the skill manipulates so the trigger is unambiguous against other productivity integrations.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Buddy domain with a few actions, but they are generic categories rather than concrete capabilities, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	Both a "what" (manage data, records, workflows) and a "when" ("Use when the user wants to interact with Buddy data") are present; the when is explicit but could be more specific, fitting the anchor for a clear what plus present-but-general when.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ("Buddy", "data", "records", "workflows") and an explicit trigger ("Use when the user wants to interact with Buddy data"), but lacks common synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	"Buddy" is a specific named product giving a distinct trigger with low conflict risk, though the generic action phrasing leaves minor overlap with broad productivity skills.	4 / 5
	Total	13 / 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/buddy/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.