Tencent SkillHub · Developer Tools

Solana Dev Skill

End-to-end Solana development playbook (Jan 2026). Prefer Solana Foundation framework-kit (@solana/client + @solana/react-hooks) for React/Next.js UI. Prefer @solana/kit for all new client/RPC/transaction code. When legacy dependencies require web3.js, isolate it behind @solana/web3-compat (or @solana/web3.js as a true legacy fallback). Covers wallet-standard-first connection (incl. ConnectorKit), Anchor/Pinocchio programs, Codama-based client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: idl-codegen.md, resources.md, frontend-framework-kit.md, testing.md, programs-pinocchio.md, programs-anchor.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.0

Provenance

Publisher: h4rkl
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 9 sections Open source page

What this Skill is for

Use this Skill when the user asks for: Solana dApp UI work (React / Next.js) Wallet connection + signing flows Transaction building / sending / confirmation UX On-chain program development (Anchor or Pinocchio) Client SDK generation (typed program clients) Local testing (LiteSVM, Mollusk, Surfpool) Security hardening and audit-style reviews

Default stack decisions (opinionated)

UI: framework-kit first Use @solana/client + @solana/react-hooks. Prefer Wallet Standard discovery/connect via the framework-kit client. SDK: @solana/kit first Prefer Kit types (Address, Signer, transaction message APIs, codecs). Prefer @solana-program/* instruction builders over hand-rolled instruction data. Legacy compatibility: web3.js only at boundaries If you must integrate a library that expects web3.js objects (PublicKey, Transaction, Connection), use @solana/web3-compat as the boundary adapter. Do not let web3.js types leak across the entire app; contain them to adapter modules. Programs Default: Anchor (fast iteration, IDL generation, mature tooling). Performance/footprint: Pinocchio when you need CU optimization, minimal binary size, zero dependencies, or fine-grained control over parsing/allocations. Testing Default: LiteSVM or Mollusk for unit tests (fast feedback, runs in-process). Use Surfpool for integration tests against realistic cluster state (mainnet/devnet) locally. Use solana-test-validator only when you need specific RPC behaviors not emulated by LiteSVM.

Operating procedure (how to execute tasks)

When solving a Solana task:

1. Classify the task layer

UI/wallet/hook layer Client SDK/scripts layer Program layer (+ IDL) Testing/CI layer Infra (RPC/indexing/monitoring)

2. Pick the right building blocks

UI: framework-kit patterns. Scripts/backends: @solana/kit directly. Legacy library present: introduce a web3-compat adapter boundary. High-performance programs: Pinocchio over Anchor.

3. Implement with Solana-specific correctness

Always be explicit about: cluster + RPC endpoints + websocket endpoints fee payer + recent blockhash compute budget + prioritization (where relevant) expected account owners + signers + writability token program variant (SPL Token vs Token-2022) and any extensions

4. Add tests

Unit test: LiteSVM or Mollusk. Integration test: Surfpool. For "wallet UX", add mocked hook/provider tests where appropriate.

5. Deliverables expectations

When you implement changes, provide: exact files changed + diffs (or patch-style output) commands to install/build/test a short "risk notes" section for anything touching signing/fees/CPIs/token transfers

Progressive disclosure (read when needed)

UI + wallet + hooks: frontend-framework-kit.md Kit ↔ web3.js boundary: kit-web3-interop.md Anchor programs: programs-anchor.md Pinocchio programs: programs-pinocchio.md Testing strategy: testing.md IDLs + codegen: idl-codegen.md Payments: payments.md Security checklist: security.md Reference links: resources.md

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

6 Docs

frontend-framework-kit.md Docs
idl-codegen.md Docs
programs-anchor.md Docs
programs-pinocchio.md Docs
resources.md Docs
testing.md Docs