Name: bancontact-payconiq-company
Rating: 52.8 (1 reviews)
Author: membranedev

bancontact-payconiq-company

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

Quality

59%

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/bancontact-payconiq-company/SKILL.md

Quality

Content

61%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 solid, command-driven integration guide with strong actionability and a real connection-state feedback loop, but it loses points to a definitional intro, a missing verification step for destructive payment actions, and inlined reference material. Adding a verify-after-run step and splitting the flag/clientAction reference into a bundled file would lift the weaker dimensions.

Suggestions

Add an explicit verification step after running destructive actions (e.g. re-query the transaction/payout status and confirm the expected state before reporting success).

Trim the opening definitional paragraph and editorial asides so the file leads directly with the integration workflow.

Move the full proxy flag table and clientAction field reference into a bundled reference file (e.g. references/PROXY.md) and link to it, keeping only essentials inline.

Dimension	Reasoning	Score
Conciseness	Largely command-focused and efficient, but opens with definitional context Claude already knows ('a payment processing service popular in Belgium') and includes some editorial padding ('so you can focus on the integration logic rather than auth plumbing'), fitting the score-3 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, copy-pasteable commands throughout (login, connection ensure, action run, request) with a flag table and JSON examples, matching the score-4 'mostly executable guidance with minor gaps' anchor; not a 5 because placeholders like QUERY/CONNECTION_ID/<actionId> are never tied into a single complete worked example.	4 / 5
Workflow Clarity	A clear Install→Auth→Connect→Search→Run sequence with a genuine poll/validation loop for connection state, but the action-run path for destructive payment operations (refunds, payouts) has no verify step, so the destructive-operation cap holds at 3.	3 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and one-level navigation, but no bundle references exist and reference-style material (full flag tables, detailed clientAction field docs) is inlined, fitting the score-4 'good structure, minor organization gaps' anchor rather than the well-split, clearly-signaled-references bar for a 5.	4 / 5
	Total	14 / 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 a specific product niche and includes an explicit 'Use when' clause, but its action language is generic ('manage data, records, and automate workflows') and trigger phrases lack natural synonyms. Tightening actions to concrete payment verbs (refund, payout, list transactions) and adding concrete trigger terms would raise it.

Suggestions

Replace generic actions with concrete payment verbs, e.g. 'list transactions, issue refunds, and view payouts'.

Add natural trigger terms and synonyms beyond the product name, e.g. 'Use when the user wants to query Bancontact/Payconiq transactions, process refunds, or check payouts.'

Specify the file or identifier types involved (merchant IDs, transaction IDs, payout references) to sharpen when-to-use guidance.

Dimension	Reasoning	Score
Specificity	Names the domain ('Bancontact Payconiq Company integration') but the actions ('Manage data, records, and automate workflows') are minimal and generic, matching the score-2 anchor rather than the concrete 1-2 actions required for a 3.	2 / 5
Completeness	Both a 'what' (integration, manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with...') are present, but the trigger could be more concrete, matching the score-4 anchor rather than the explicit-trigger-phrases bar for a 5.	4 / 5
Trigger Term Quality	The product name is a relevant keyword, but the trigger phrase ('interact with Bancontact Payconiq Company data') is generic with no synonyms or natural variations a user would say, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The named Belgian payment product gives it a mostly-distinct niche with minor overlap risk, though the generic 'manage data, records, and automate workflows' wording could overlap with other integration 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/bancontact-payconiq-company/SKILL.md
Commit: f484c82

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