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

fireberry

Fireberry integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Fireberry 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/fireberry/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 highly actionable, well-structured CLI integration guide with strong command examples and a clear connection workflow. Its main gap is the absence of validation/verification steps for the destructive and batch data operations it enables.

Suggestions

Add a verification step after create/update/delete actions, e.g. re-fetch the record with the corresponding get-* action to confirm the change took effect.

For proxy requests involving DELETE/PUT/PATCH, include a guidance note to confirm the target id and check the response status before proceeding.

Trim the CRM background sentence and the "so you can focus on the integration logic" aside to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean CLI commands and tables, with only minor over-explanation (e.g., the CRM intro and the "so you can focus on the integration logic" aside) that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands with full flag tables for auth, connection, action list/run, and proxy requests, covering the common integration cases.	5 / 5
Workflow Clarity	The connection setup is well sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop, but the skill enables destructive/batch data operations (create/update via action run, DELETE via proxy) with no validation or verification guidance, capping the score at 3.	3 / 5
Progressive Disclosure	Content is well organized into clear sections with no bundle files to navigate; the inline 20-row actions table is borderline but reasonable as a quick-reference overview.	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.

A concise, third-person description that covers both what the skill does and when to use it, anchored to a distinctive product name. The main weakness is the generic "Manage" verb and a slightly vague trigger phrase.

Suggestions

Replace the generic "Manage" with more specific verbs per entity (e.g., "create, update, and list Organizations, Pipelines, Users, Goals, Filters").

Tighten the trigger clause with concrete user phrasings, e.g. "Use when the user wants to list, create, or update Fireberry records such as contacts, deals, or tasks."

Consider adding common synonyms (e.g., "accounts", "opportunities") to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	It lists several concrete resource types to manage ("Organizations, Pipelines, Users, Goals, Filters"), but the single generic verb "Manage" leaves minor coverage gaps versus distinct per-entity actions.	4 / 5
Completeness	It states a clear "what" (manage those Fireberry entities) and an explicit "Use when..." clause, but the trigger ("interact with Fireberry data") is somewhat generic rather than tied to concrete phrases.	4 / 5
Trigger Term Quality	It surfaces the product name "Fireberry" plus the entity keywords a user would naturally name, though a few natural synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	The distinctive brand "Fireberry" carves a clear niche with minimal overlap risk against 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/fireberry/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.