Name: firecom
Rating: 55.2 (1 reviews)
Author: membranedev

firecom

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/firecom/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 action-oriented and well-structured with strong executable CLI guidance and good connection-state handling, but it lacks a validation/confirmation step before running destructive payment actions and the 'Popular actions' section underdelivers. Adding a pre-action verification checkpoint would most improve it.

Suggestions

Add an explicit validation/confirmation checkpoint before running payment or batch actions, e.g. 'Before running a payment action, echo the action name and input back to the user and confirm; re-read the outputSchema to verify the result state.'

Populate 'Popular actions' with concrete example action names and one-line run commands instead of only repeating the discovery command.

Trim filler like 'so you can focus on the integration logic rather than auth plumbing' to keep the body lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean operational guidance with copy-paste commands and a flag table, but contains minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed, fitting efficient-with-minor-padding rather than fully lean.	4 / 5
Actionability	It provides concrete executable commands (install, login, connection ensure/get, action list/run, request) with real flags, but the 'Popular actions' section only re-issues the discovery command instead of listing any actual popular actions, leaving a minor gap below fully copy-paste-ready coverage.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear with connection-state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but Fire.com is a payment platform where running actions is destructive/financial and there is no validation checkpoint before executing actions, so workflow clarity is capped at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no external bundle files and no nested references, but the file exceeds 50 lines and the thin 'Popular actions' section is slightly misplaced, keeping it just below the ideal single-file organization of a 5.	4 / 5
	Total	15 / 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 clearly tied to a distinct platform, but its action language is generic and its trigger terms lack the concrete financial vocabulary users would naturally say. Tightening verbs and adding terms like payments, accounts, and transactions would lift it.

Suggestions

Replace generic verbs with concrete Fire.com actions, e.g. 'List account balances, send payments, retrieve transactions, and create payment requests.'

Expand the trigger clause with natural user terms: 'Use when the user wants to check Fire.com balances, send or track payments, or manage counterparties and transactions.'

Avoid the filler 'Manage data, records, and automate workflows' — it adds breadth without specificity and weakens the distinctiveness of the named platform.

Dimension	Reasoning	Score
Specificity	It names the Fire.com domain but the actions 'Manage data, records, and automate workflows' are generic rather than concrete, matching the score-2 anchor for minimal/generic actions rather than the specific verbs needed for a 3.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Fire.com data') are present, but the 'what' is generic and the 'when' could name concrete triggers, keeping it below a 5.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Fire.com data' supplies a relevant trigger phrase but misses natural variations users would say (accounts, payments, transactions, statements), so it stops at some-relevant-keywords rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	'Fire.com integration' carves a clear named niche with minimal conflict risk, though the generic verbs ('manage data, records') leave minor overlap with adjacent finance skills rather than the fully distinct triggers of a 5.	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/firecom/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.