Query onchain data on Base using SQL with per-query x402 payments.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add coinbase/agentic-wallet-skills --skill query-onchain-dataCompatible with
Supported agents
Access decoded events, transactions, and blocks via CoinbaseQL, a ClickHouse-based SQL dialect supporting joins, CTEs, subqueries, and standard functions
Three main tables available: base.events (decoded smart contract logs), base.transactions (full transaction data), and base.blocks (block metadata)
Requires filtering on indexed fields ( event_signature , address , block_timestamp ) in event queries to avoid full tab
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionquery-onchain-dataExecute the skills CLI command in your project's root directory to begin installation:
epx add coinbase/agentic-wallet-skills --skill query-onchain-dataFetches query-onchain-data from coinbase/agentic-wallet-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/query-onchain-data
Restart Cursor to activate query-onchain-data. Access via /query-onchain-datain your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
stock-price-query
tjefferson/stock-price-query · Productivity · tag: query
csv-data-wrangler
404kidwiz/claude-supercode-skills · Productivity · tag: data
llm-council
am-will/codex-skills · AI/ML · same category
ai-video-generation
inference-sh/skills · AI/ML · same category
domain-hunter
resciencelab/opc-skills · AI/ML · same category
qq-email
shadowcz007/skills · AI/ML · same category
Solid pick for teams standardizing on skills: query-onchain-data is focused, and the summary matches what you get after install.
Keeps context tight: query-onchain-data is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added query-onchain-data from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend query-onchain-data for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in query-onchain-data — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
query-onchain-data has been reliable in day-to-day use. Documentation quality is above average for community skills.
query-onchain-data reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend query-onchain-data for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
query-onchain-data is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
query-onchain-data fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 73