CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

veil

Privacy and shielded transactions on Base via Veil Cash - ZK-based anonymous transfers

57

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/veil/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A compact, command-focused skill body that is easy to act on: syntax, examples, env setup, and requirements are all present. Its main weaknesses are the duplicated Setup content, the absence of any verification steps around irreversible fund operations, and one vague directive ('Use dedicated RPC') with no concrete alternative.

Suggestions

Add validation checkpoints around fund movement, e.g., 'After /veil deposit, confirm the pending deposit with /veil queue before it appears in /veil private' and 'Run /veil status to verify relay health before withdrawals'.

Merge the duplicate '### Setup' command block and '## Setup' section into a single setup section to remove the repeated '/veil init' and env-var content.

Replace 'Use dedicated RPC to avoid rate limits' with a concrete configuration (e.g., an explicit env var and example endpoint) and add one concrete '/veil transfer' example showing a real veil-key format.

DimensionReasoningScore

Conciseness

The body is a lean command reference with no over-explanation of concepts Claude already knows, but the '## Setup' section duplicates the '/veil init' content from the '### Setup' command block and the Examples section repeats commands verbatim, so a few tokens could be trimmed.

4 / 5

Actionability

Commands are concrete and executable with explicit syntax ('/veil deposit <amount>', '/veil withdraw <amount> <address>') plus realistic examples ('/veil deposit 0.1', '/veil withdraw 0.05 0x1234...') and a concrete install step ('npm install -g @veil-cash/sdk'). Minor gaps: 'Use dedicated RPC to avoid rate limits' gives no concrete configuration, and no example shows a real veil-key format for '/veil transfer'.

4 / 5

Workflow Clarity

The deposit/transfer/withdraw sequence is listed coherently in 'How It Works' and commands are grouped by stage, but there are no validation checkpoints (e.g., check '/veil queue' or '/veil status' after a deposit before withdrawing) for operations that move funds irreversibly, which caps this dimension at 3 per the rubric's destructive-operations rule.

3 / 5

Progressive Disclosure

The skill is self-contained with clearly labeled sections (How It Works, Commands, Examples, Security Notes, Requirements) and no bundle files, which is appropriate at this size. The duplicate 'Setup' heading (once as '### Setup' under Commands, again as '## Setup') is a minor navigation/organization flaw that keeps it from a 5.

4 / 5

Total

15

/

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.

A distinct, well-targeted description that clearly states what the skill does in the Veil Cash/Base privacy niche, with natural trigger keywords. Its gaps are the missing 'when to use' guidance and incomplete coverage of the concrete operations (deposit, withdraw, transfer) that the skill actually provides.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user wants to send ETH privately on Base, mention Veil Cash, shielded/private transactions, or anonymous transfers.'

Name the core operations to raise specificity, e.g., 'Deposit ETH into a private pool, transfer privately, and withdraw to a public address on Base via Veil Cash ZK proofs.'

Include a couple of common user phrasings as synonyms ('send ETH anonymously', 'private payments') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain clearly ('Privacy and shielded transactions on Base via Veil Cash') and includes 1-2 concrete actions ('transactions', 'ZK-based anonymous transfers'), but omits the core operations (deposit, withdraw, private transfer, balance). It is not a 4 because it does not list several specific actions, and not a 2 because 'ZK-based anonymous transfers' is more concrete than a generic domain label.

3 / 5

Completeness

It clearly answers 'what' (privacy and shielded transactions on Base via Veil Cash, ZK-based anonymous transfers) but contains no 'Use when...' clause or equivalent trigger guidance, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'Privacy', 'shielded transactions', 'anonymous transfers', 'Base' are phrases a user needing this skill would plausibly say. A few natural terms are missing (e.g., 'send ETH privately', 'private payments', 'hide transaction'), which keeps it below comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Naming the specific platform ('Veil Cash'), network ('Base'), and technology ('ZK-based') carves out a clear niche with essentially no overlap risk with other skills, matching the minimal-conflict anchor.

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.

Validation — 15 / 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

alsk1992/CloddsBot

Path

src/skills/bundled/veil/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill