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

kickfire

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/kickfire/SKILL.md

Quality

Content

67%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 a strong, command-driven integration guide with a clear authenticated workflow and good state-handling checkpoints. Its weak spots are some marketing-flavored prose, a 'Popular actions' section that lists nothing, and the absence of a verification guardrail around destructive proxy calls.

Suggestions

Trim the introductory marketing paragraph and the 'focus on the integration logic rather than auth plumbing' aside so the body leads with actionable setup steps.

Either populate 'Popular actions' with a few concrete KickFire actions (e.g., company match, visitor lookup) or remove the empty heading to avoid implying content that isn't there.

Add a verification checkpoint before destructive proxy calls (e.g., confirm the method and target with the user before PUT/PATCH/DELETE, and check the response status/error field) to satisfy the destructive-operations feedback-loop expectation.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and a tight flags table, but the opening marketing paragraph ('identifies the company behind anonymous website traffic... improve conversion rates') and asides like 'so you can focus on the integration logic rather than auth plumbing' add explanation that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests with a concrete flags table; the main gap is the 'Popular actions' heading that tells you to discover actions rather than listing any.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run → proxy sequence with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but no verification step before potentially destructive proxy methods (PUT/PATCH/DELETE).	4 / 5
Progressive Disclosure	The single SKILL.md is well organized with clear section headers and no nested references, and no bundle files are needed for this single-integration skill; minor redundancy between 'Searching for actions' and 'Popular actions' keeps it from 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 correctly identifies the KickFire niche and includes an explicit 'Use when' trigger, but its capability verbs are generic rather than concrete. Tightening the action list to specific KickFire capabilities would lift specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete KickFire capabilities such as 'identify companies behind website visitors, look up firmographics, and enrich lead records'.

Add natural synonyms and file/term variations users might say (e.g., 'company IP enrichment', 'visitor identification', 'firmographic lookup') to broaden trigger coverage.

Make the 'when' clause more specific than 'interact with KickFire data' by listing the triggering intents (e.g., 'when the user wants to identify website visitors' companies or enrich leads with firmographics').

Dimension	Reasoning	Score
Specificity	It names the domain ('KickFire integration') but the actions are generic verbs — 'Manage data, records, and automate workflows' and 'interact with KickFire data' — with no concrete capabilities, matching the 'Names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with KickFire data'), but the 'what' is generic rather than concrete, so it stops short of a 5.	4 / 5
Trigger Term Quality	The proper noun 'KickFire' is a natural term users would say, plus 'data', 'records', and 'workflows', but common variations or synonyms are missing, fitting 'Some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The named product 'KickFire' gives it a clear, distinct niche with minimal conflict risk, but the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with adjacent sales/marketing 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/kickfire/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.