CtrlK
BlogDocsLog inGet started
Tessl Logo

chatfuel

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/chatfuel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 executable commands and a clear connection workflow, weakened only by minor verbosity and the absence of post-action validation for destructive operations.

Suggestions

Trim editorial padding (the Chatfuel overview paragraph and 'focus on integration logic' asides) to assume Claude's competence.

Add an explicit verification step after destructive/batch actions (e.g. confirm a broadcast was sent or a page disconnect succeeded) to strengthen workflow feedback loops.

Consider moving the full proxy-flag table to a reference file if the body grows, keeping SKILL.md an overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands, but includes padded asides Claude could infer ('so you can focus on the integration logic rather than auth plumbing') and a product-marketing overview paragraph.

3 / 5

Actionability

It provides copy-paste-ready bash commands for install, auth, connection, polling, action list/run, and proxy requests, with flag tables and JSON input examples covering the common cases.

5 / 5

Workflow Clarity

The install→auth→connect→poll→search→run sequence is clear with state-based checkpoints and a re-poll feedback loop, though destructive/batch actions (broadcasting, disconnect) lack explicit post-run validation.

4 / 5

Progressive Disclosure

Single well-organized SKILL.md with clear section headers and no nested references; no bundle files are needed, though a few inline tables could optionally be split out.

4 / 5

Total

16

/

20

Passed

Description

66%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 cleanly states both purpose and trigger with a distinctive product name, but the capability list is generic rather than enumerating concrete Chatfuel actions.

Suggestions

Replace generic verbs with concrete Chatfuel actions (e.g. 'create bots, connect pages, broadcast messages, manage WhatsApp contacts') to lift specificity.

Add natural synonyms a user might say (e.g. 'chatbot', 'Facebook Messenger bot', 'broadcasting') to broaden trigger coverage.

Tighten the 'what' clause to mirror the action table already documented in the skill body.

DimensionReasoningScore

Specificity

It names the domain (Chatfuel) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Chatfuel operations, matching the anchor for naming a domain with 1-2 minimal actions.

3 / 5

Completeness

Both a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Chatfuel data') are present; the 'when' is explicit but the 'what' is somewhat generic.

4 / 5

Trigger Term Quality

'Chatfuel', 'data', 'records', and 'interact with Chatfuel data' are relevant keywords, but common natural variations or synonyms a user would say are missing.

3 / 5

Distinctiveness Conflict Risk

'Chatfuel' is a clearly distinct niche trigger with minimal overlap risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.