Name: freshbooks
Rating: 60.8 (1 reviews)
Author: membranedev

freshbooks

Freshbooks integration. Manage Users, Organizations, Projects, Pipelines, Goals, Filters and more. Use when the user wants to interact with Freshbooks data.

Quality

71%

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/freshbooks/SKILL.md

Quality

Content

68%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 copy-paste CLI commands and a useful action reference, and is reasonably well-structured. Its main weaknesses are some conceptual padding in the prose and a lack of validation/confirmation guidance around destructive actions like deletes.

Suggestions

Trim background prose Claude already knows (the opening paragraph defining Freshbooks and the 'auth plumbing' commentary) to tighten token efficiency.

Add a validation/confirmation checkpoint before destructive actions (e.g., confirm or list-then-delete, and verify the result) to satisfy the destructive-operations feedback-loop expectation.

Consider moving the full popular-actions table into a references file linked from the body, leaving only a few representative examples inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but includes unnecessary explanation Claude already knows ('Freshbooks is an accounting software designed for small businesses and freelancers...') and padded prose ('so you can focus on the integration logic rather than auth plumbing').	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (membrane login, connection ensure, action list/run, request) plus a concrete popular-actions table with keys and descriptions covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with polling and state checkpoints, but destructive operations (Delete Sales Invoice, Delete Contact) are presented via a bare 'membrane action run' with no validation/confirmation feedback loop, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and tables, and no nested references; the inline 20-row popular-actions table is borderline reference material that could live in a separate file, keeping it just shy of a 5.	4 / 5
	Total	15 / 20 Passed

Description

73%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 niche (Freshbooks) with an explicit 'Use when' trigger, but its capability statement relies on a single generic verb ('Manage') plus 'and more' rather than listing concrete actions. Strong on distinctiveness and trigger clarity, moderate on specificity.

Suggestions

Replace 'Manage ... and more' with 2-3 concrete verbs reflecting actual Freshbooks actions (e.g., 'Create and track invoices, manage clients and expenses, record payments').

Add natural trigger synonyms beyond the brand name (e.g., 'invoicing', 'accounting', 'expenses') so users who describe the task functionally still hit the skill.

Dimension	Reasoning	Score
Specificity	Names the Freshbooks domain and many concrete entities (Users, Organizations, Projects, Pipelines, Goals, Filters) but the only action verb is the generic 'Manage ... and more', so actions remain minimal rather than comprehensive.	3 / 5
Completeness	Both 'what' (Freshbooks integration managing listed entities) and 'when' ('Use when the user wants to interact with Freshbooks data') are present; the 'when' is explicit but the 'what' is somewhat generic with 'and more'.	4 / 5
Trigger Term Quality	The natural trigger term 'Freshbooks' appears and is repeated in 'interact with Freshbooks data'; good keyword coverage, though synonyms like invoicing/accounting are absent.	4 / 5
Distinctiveness Conflict Risk	'Freshbooks integration' names a specific commercial app, giving it a clear niche with a distinct trigger and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/freshbooks/SKILL.md
Commit: f484c82

Reviewed: 5 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.