CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onchainkit

Build onchain apps with Coinbase's OnchainKit React components - wallets, swaps, NFTs, payments

58

Quality

73%

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

The body is a lean, actionable component catalog with concrete code and commands, but it lacks an explicit sequenced workflow with validation checkpoints and keeps all content inline despite referencing docs subcommands. Tightening the marketing Overview and adding a setup workflow would improve it.

Suggestions

Add an explicit numbered Quick Start workflow with a verification step (e.g. '1. npm create onchain@latest 2. npm install @coinbase/onchainkit 3. Run `npm run dev` and confirm the wallet connects') to give workflow clarity real checkpoints.

Move the per-component deep-dive material into reference files (e.g. references/wallet.md, references/swap.md) and link to them one level deep, so the implied '/onchainkit docs' commands resolve to real bundle files.

Trim the Overview marketing bullets and remove the time-sensitive '< $0.01 fees' claim, which penalizes conciseness and may go stale.

DimensionReasoningScore

Conciseness

The body is largely efficient with compact code and command tables, but the Overview carries mild marketing fluff ('No backend infrastructure required') and a time-sensitive cost claim ('< $0.01 fees') that could be trimmed.

4 / 5

Actionability

Provides concrete TSX import snippets for Wallet/Identity/Swap and executable npm/env commands, but the code fragments lack full file context and use placeholder values ('...'), leaving minor gaps.

4 / 5

Workflow Clarity

A loose setup -> configure -> use-components sequence is implied across Quick Start and Configuration, but no explicit multi-step workflow or validation checkpoints are present, and this is not a single-task skill that qualifies for the simple-skill exception.

3 / 5

Progressive Disclosure

Well-organized into clear sections with single-level external resource links and no nested references, but all content is inline with no bundle files backing the implied '/onchainkit docs ...' subcommands, a minor organization gap.

4 / 5

Total

15

/

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 is specific and distinct, naming a concrete library and four component categories, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a Use-when clause would meaningfully raise the score.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building onchain apps on Base or when the user mentions Coinbase OnchainKit, wallets, swaps, NFTs, or onchain payments.'

Add natural synonyms/extensions users might say (e.g. 'Base', 'crypto payments', '@coinbase/onchainkit') to broaden trigger-term coverage.

Vary the action verbs beyond 'Build' (e.g. 'add wallets', 'enable swaps', 'mint NFTs') to convey multiple concrete actions.

DimensionReasoningScore

Specificity

Names the domain (OnchainKit React components) and lists several concrete component categories ('wallets, swaps, NFTs, payments'), but the action verb is singular ('Build') rather than multiple distinct actions, so it sits at 4 rather than 5.

4 / 5

Completeness

The 'what' is clear ('Build onchain apps with Coinbase's OnchainKit React components - wallets, swaps, NFTs, payments') but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural user terms like 'onchain apps', 'wallets', 'swaps', 'NFTs', and 'payments', but lacks synonyms and file/package extensions, leaving a few common variations missing.

4 / 5

Distinctiveness Conflict Risk

The named library (Coinbase's OnchainKit) and React framing carve a clear niche with low conflict risk, though the generic component terms (wallets, NFTs) create minor overlap with broader web3 skills.

4 / 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/onchainkit/SKILL.md

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.