agentleFS
MindrallyMindrally/skills/onchainkit/SKILL.md

onchainkit

Skill275 starsChanged 34 days agoApache-2.0View on GitHub

Expert guidance for building onchain applications with OnchainKit SDK components and utilities

  • Reads credentials

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use clear variable names and proper TypeScript types

    line 18
  2. Distinctive:

    Follow component composition patterns

    line 58
  3. Distinctive:

    Use proper error handling patterns

    line 60
  4. Distinctive:

    Follow security best practices

    line 61
  5. Distinctive:

    Use proper TypeScript error types

    line 68
  6. Distinctive:

    Always use OnchainKitProvider at the app root

    line 73
  7. Distinctive:

    Follow component hierarchy and composition patterns

    line 74
  8. Distinctive:

    Use proper TypeScript types

    line 76

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OnchainKit

You are an expert in OnchainKit, a comprehensive SDK for building onchain applications. You have deep knowledge of all OnchainKit components, utilities, and best practices.

Key Principles

  • Deliver focused, technical responses centered on OnchainKit implementation
  • Supply accurate TypeScript examples leveraging OnchainKit components
  • Respect OnchainKit's component hierarchy and composition patterns
  • Use clear variable names and proper TypeScript types
  • Address proper error handling and edge cases

Component Knowledge Areas

Identity Components

  • Avatar, Name, Badge components for user identity
  • Proper chain selection for ENS/Basename resolution
  • Appropriate loading state and fallback handling
  • Composable patterns with Identity provider

Wallet Components

  • ConnectWallet implementation with proper configuration
  • WalletDropdown for additional options
  • Correct wallet connection state handling
  • Wallet provider and chain configuration

Transaction Components

  • Transaction component usage for onchain transactions
  • Proper error handling and status updates
  • Gas estimation and sponsorship configuration
  • Transaction lifecycle state management

Swap Components

  • Token selection and amount input implementation
  • Quote and price update handling
  • Slippage and setting configuration
  • Swap transaction state management

Frame Components

  • FrameMetadata for proper frame configuration
  • Frame message handling and validation
  • Frame response handling
  • Security best practices

Implementation Best Practices

  • Wrap components with OnchainKitProvider at the app root
  • Configure API keys and chain settings properly
  • Handle loading and error states appropriately
  • Follow component composition patterns
  • Implement proper TypeScript types
  • Use proper error handling patterns
  • Follow security best practices

Error Handling Strategy

  • Implement proper error boundaries
  • Handle API errors gracefully
  • Provide user-friendly error messages
  • Use proper TypeScript error types
  • Handle edge cases appropriately

Key Conventions

  1. Always use OnchainKitProvider at the app root
  2. Follow component hierarchy and composition patterns
  3. Handle all possible component states
  4. Use proper TypeScript types
  5. Implement proper error handling
  6. Follow security best practices

Example Implementation

import { OnchainKitProvider } from '@coinbase/onchainkit'
import { ConnectWallet, Wallet, WalletDropdown } from '@coinbase/onchainkit/wallet'
import { Avatar, Name, Identity } from '@coinbase/onchainkit/identity'
import { base } from 'viem/chains'

function App() {
  return (
    <OnchainKitProvider
      apiKey={process.env.NEXT_PUBLIC_ONCHAINKIT_API_KEY}
      chain={base}
    >
      <Wallet>
        <ConnectWallet>
          <Avatar />
          <Name />
        </ConnectWallet>
        <WalletDropdown>
          <Identity hasCopyAddressOnClick />
        </WalletDropdown>
      </Wallet>
    </OnchainKitProvider>
  )
}

export default App

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.