Name: bilflo
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bilflo

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

Quality

75%

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/bilflo/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.

The content is highly actionable with copy-paste CLI commands and a clear connection-state workflow, but it lacks validation/verification guidance for the destructive create/update/delete operations it enables. Organization is strong for a single-file skill though some reference tables could be externalized.

Suggestions

Add a verification/confirmation step for mutating actions and proxy DELETE/PUT calls, e.g. 'For Create/Update/Delete, confirm the target ID with the user and check the response output for success before proceeding.'

Trim the FP&A background sentence and 'auth plumbing' commentary to tighten conciseness.

Consider moving the popular-actions table and proxy-flags table into a reference file referenced one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven reference material, but includes minor over-explanation such as the FP&A intro and 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed, fitting anchor 4 rather than 5.	4 / 5
Actionability	It provides copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, request) with real flags and a concrete JSON-input example, plus a popular-actions table and proxy-flags reference.	5 / 5
Workflow Clarity	The connection flow has excellent state validation and feedback loops, but the skill exposes destructive/mutating operations (Create/Update actions and proxy POST/PUT/DELETE) with no verification or confirmation steps, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The single-file body is well organized into clear sections with easy navigation, but at ~165 lines it inlines reference-like material (the 20-row actions table and proxy-flags table) that could be split into separate files, leaving it just short of anchor 5.	4 / 5
	Total	16 / 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 answers both what and when with an explicit trigger clause and a product-specific niche, but its capability verbs are generic ('manage', 'automate') rather than concrete. It is solid but could name specific Bilflo actions to lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Bilflo actions, e.g. 'List and create clients, contractors, jobs, and payments' to raise specificity.

Expand the trigger phrase with natural variations a user would say, e.g. 'Use when the user wants to query or update Bilflo clients, jobs, or payments.'

Dimension	Reasoning	Score
Specificity	The description names the Bilflo domain and a couple of actions ('Manage data, records, and automate workflows'), but the verbs 'manage' and 'automate' are generic rather than concrete like 'extract' or 'fill', placing it between anchors 2 and 3.	3 / 5
Completeness	Both 'what' (Bilflo integration managing data/records and automating workflows) and 'when' ('Use when the user wants to interact with Bilflo data') are present and explicit, but the 'what' is generic rather than listing concrete actions, so it does not reach anchor 5.	4 / 5
Trigger Term Quality	It includes a natural trigger phrase ('Use when the user wants to interact with Bilflo data') plus relevant keywords ('Bilflo', 'data', 'records', 'workflows'), with only minor synonym coverage missing.	4 / 5
Distinctiveness Conflict Risk	The description is bound to a specific named product ('Bilflo') with a distinct trigger ('interact with Bilflo data'), giving it a clear niche and minimal overlap 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/bilflo/SKILL.md
Commit: f484c82

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