Name: freeagent
Rating: 64.8 (1 reviews)
Author: membranedev

freeagent

Freeagent integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Freeagent data.

Quality

77%

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

Quality

Content

76%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.

A well-structured, highly actionable integration guide with concrete commands and a clear connection-state workflow. Its main weakness is the absence of validation/verification steps around destructive and batch actions, and minor over-explanation of basic concepts.

Suggestions

Add a validation/verification checkpoint after create/update/delete actions (e.g., re-fetch the entity or confirm the returned state before reporting success).

Trim the introductory paragraph explaining what FreeAgent is and who uses it, since Claude already knows this.

Remove the redundant 'Freeagent Overview' entity bullet list or fold it into the Popular actions table to avoid duplication.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands and tables, but includes minor over-explanation (what FreeAgent is and who uses it) and a redundant entity bullet list that overlaps the Popular actions table.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request proxy) plus a documented flag table and a Popular actions catalog covering common cases.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with a poll/act/re-check feedback loop, but the destructive and batch action workflows (create/update/delete invoices, bills) lack validation or verification checkpoints, capping this dimension at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Single-file structure with clear section headers and no nested references; the inlined Popular actions and proxy-flag tables are well placed, though the full action catalog could arguably live in a reference file. No bundle files exist to verify.	4 / 5
	Total	16 / 20 Passed

Description

78%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 specific niche (Freeagent accounting) with explicit 'what' and 'when' clauses and concrete entity names. It is slightly generic in its trigger phrasing and uses the repeated verb 'Manage' with an 'and more' hedge.

Suggestions

Replace the repeated 'Manage' verb with varied concrete actions (e.g., create, list, update, delete) for the named entities.

Expand the trigger clause with natural synonyms users would say, e.g. 'Use when the user wants to manage FreeAgent accounting, invoices, contacts, or projects.'

Drop the 'and more' hedge or make coverage explicit to avoid implying incompleteness.

Dimension	Reasoning	Score
Specificity	Lists several concrete entity targets ('Manage Deals, Persons, Organizations, Leads, Projects, Pipelines'), but the generic repeated verb 'Manage' and the 'and more' hedge leave minor gaps versus comprehensive coverage.	4 / 5
Completeness	Explicitly states both what it does ('Freeagent integration', managing named entities) and when to use it ('Use when the user wants to interact with Freeagent data'); the 'when' clause is present but fairly generic, not a concrete trigger list.	4 / 5
Trigger Term Quality	Names the specific app clearly and includes a natural trigger phrase ('Use when the user wants to interact with Freeagent data'), though it misses common synonyms like accounting, invoices, or expenses.	4 / 5
Distinctiveness Conflict Risk	Freeagent is a specific named accounting app, giving a clear niche with distinct 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: membranedev/application-skills
Path: skills/freeagent/SKILL.md
Commit: f484c82

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