remit

Fill the Maybank remittance (bank transfer) form by editing remit.json in a Remit project.

Quality

72%

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 ./apps/remit/src-tauri/skills/remit/SKILL.md

Quality

Content

80%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 and well-structured, with a complete field schema and concrete rules. Its weakest point is workflow clarity: form/document manipulation lacks an explicit validation checkpoint before the user exports.

Suggestions

Add a validation step before handoff, e.g. 'Before the user exports, confirm all required fields (recipient name/id, bank account, amount, swift for foreign currency) are non-empty.'

Tighten the opening paragraph by dropping narrative framing ('You are the agent inside a Remit project') in favor of a one-line purpose statement.

Add a brief checklist of common error states (missing swift, currency/senderAccount mismatch) to turn the rules into a feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is efficient: a lean jsonc schema with inline comments and tight rules that assume Claude's competence, with only minor narrative padding in the opening paragraph that could be trimmed.	4 / 5
Actionability	Provides a copy-paste-ready remit.json template with all enum values and concrete field-mapping rules (e.g. MYR -> In RM slot, senderAccount by debit account), fully covering the common cases.	5 / 5
Workflow Clarity	The read-then-edit sequence is present, but this is document/form manipulation with no validation checkpoint (e.g. verifying required fields before the user exports), which caps workflow clarity at 3 per the destructive/document guideline.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections ('The document', 'Rules'), qualifying for the top score via the simple-skill exception.	5 / 5
	Total	17 / 20 Passed

Description

65%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 is specific and clearly distinguishable, stating a concrete task (filling a Maybank remittance form by editing remit.json). Its main weakness is the absence of an explicit 'when to use' trigger clause, which caps completeness.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user needs to fill or co-author a Maybank remittance/bank transfer form inside a Remit project.'

Broaden trigger terms with synonyms users might say, such as 'wire transfer', 'overseas transfer', or 'send money abroad'.

Mention the key artifacts more explicitly (e.g. 'remit.json' alongside 'Remit project') to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Maybank remittance (bank transfer) form') and two concrete actions ('Fill...form', 'editing remit.json') but the coverage is not comprehensive, matching the anchor for domain + 1-2 concrete actions.	3 / 5
Completeness	The 'what' is clear (fill the Maybank remittance form via remit.json) but there is no 'Use when...' or equivalent trigger clause, so the missing explicit 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('remittance', 'bank transfer', 'form') plus the file name 'remit.json', giving good keyword coverage with only a few synonyms missing.	4 / 5
Distinctiveness Conflict Risk	Targets a very specific niche (one bank's remittance form) with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tombrewsviews/BYOA
Path: apps/remit/src-tauri/skills/remit/SKILL.md
Commit: e2ffa8f

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