We Open-Sourced Our Hive Development Brain — A Claude Code Skill for Building on Hive

avatar

image.png

If you use Claude Code and want to build on the Hive blockchain, we just made your life significantly easier.

Mantequilla-Soft is releasing hive-master-skill. A free, open-source Claude Code skill that gives Claude deep, production-grade expertise in Hive blockchain development.

This isn't a copy-paste of the Hive developer docs. This is battle-tested knowledge extracted from patterns across 40+ production Hive applications, including real workarounds, gotchas, and fixes that you won't find documented anywhere else.

What Is a Claude Code Skill?

For those unfamiliar: Claude Code is Anthropic's command-line tool for agentic coding. You describe what you want, and Claude writes, edits, and runs the code for you directly in your terminal.

Skills are knowledge packs that you can install to give Claude specialized expertise in a specific domain. Think of them as teaching Claude how an experienced developer in that field actually works, not just the API surface, but the patterns, traps, and production workarounds that take years to accumulate.

When you install hive-master-skill, Claude suddenly knows:

  • How to structure Hive API calls with proper node failover
  • Which key type to use for which operation
  • That beneficiaries must be sorted alphabetically (or your transaction silently fails)
  • That dhive's auto-failover is broken on React Native
  • How to calculate vote values, mana regeneration, and RC costs
  • The correct way to sign image uploads to images.hive.blog
  • And about 3,800 lines more of this kind of practical knowledge

What's Inside

The skill is organized into focused reference files that Claude loads on demand:

FileWhat It Covers
api-reference.mdRPC nodes, all API namespaces (condenser, bridge, database, rc_api), image upload signing
operations.mdEvery Hive operation — comment, vote, transfer, power up/down, delegate, savings, convert, witness
content.mdPosts, replies, votes, feeds, voting power math, optimistic updates, avatar parsing, mute lists
wallet.mdTransfers, VESTS↔HP conversion, savings, HBD conversion, recurrent transfers, transaction history
custom-json.mdFollow/unfollow/mute, reblog, community ops, RC delegation, Hive Engine operations
keys-and-auth.mdKey hierarchy, challenge-response signing, Keychain, HiveAuth, HiveSigner, secure storage
communities.mdSubscribe, post to community, roles, moderation, update properties
streaming-and-realtime.mdBlock streaming, polling patterns, notifications, WebSocket pitfalls
hive-engine.mdLayer 2 tokens, balances, order book, staking, NFTs, diesel pools
react-native.mdReact Native / Expo patterns — SecureStore, image handling, networking
battle-tested.md18 hard-won lessons from production (the good stuff)
examples/Complete, copy-paste-ready code patterns and React hooks

The Battle-Tested File

This is honestly the most valuable part. Here's a taste of what's in battle-tested.md:

  1. dhive does NOT auto-failover on React Native — You must implement manual node rotation. We include the complete working implementation.
  2. Never retry broadcast operations — A timeout doesn't mean it failed. The transaction may already be on-chain. Retrying creates duplicates.
  3. Beneficiaries must be sorted alphabetically — The protocol requires it but the error message is cryptic. Just .sort() by account name.
  4. iOS ph:// URIs break image uploads — The Photos framework URI needs to be normalized through expo-image-manipulator before uploading.
  5. Hive timestamps need a 'Z' suffix — Without it, JavaScript interprets them as local time, and your dates are off by hours.
  6. posting_json_metadata vs json_metadata — Two different fields, two different key requirements. Always check posting_json_metadata first.
  7. TUS upload resume fails on some services — embed.3speak.tv doesn't return Upload-Length on HEAD requests, so resume always fails. You need to clear stale fingerprints.

There are 18 of these in total, each with the problem description, the fix, and working code. Some of these took hours or days to diagnose in production. Now Claude knows about all of them before writing a single line of code.

How to Install

Option 1: Personal skill (available across all your projects)

git clone https://github.com/Mantequilla-Soft/hive-master-skill.git ~/.claude/skills/hive-master

That's it. The skill is now available in every project on your machine.

Option 2: Per-project (committed to your repo)

mkdir -p .claude/skills
git clone https://github.com/Mantequilla-Soft/hive-master-skill.git .claude/skills/hive-master
rm -rf .claude/skills/hive-master/.git
git add .claude/skills/hive-master
git commit -m "Add hive-master skill"

Option 3: Git submodule (stays updated)

git submodule add https://github.com/Mantequilla-Soft/hive-master-skill.git .claude/skills/hive-master

Once installed, Claude auto-detects when you're doing Hive work and loads the relevant knowledge. You can also invoke it manually with /hive-master or pass a topic like /hive-master wallet.

Why We Built This

At Mantequilla-Soft, we maintain and build tools for the Hive ecosystem — including infrastructure for 3Speak, open-source developer tooling, and community projects. Between our team, we've collectively hit every sharp edge that Hive development has to offer.

When Claude Code started supporting skills, we realized we could package all of that accumulated knowledge and give it away. Every new developer building on Hive shouldn't have to rediscover that beneficiaries need sorting, or that dhive failover is broken on mobile, or that image uploads need the ImageSigningChallenge prefix.

This is our contribution to lowering the barrier for building on Hive. If Claude Code is becoming part of how developers work, then Hive should be a first-class citizen in that workflow.

Contributing

Found a new gotcha? Discovered a better pattern? PRs are welcome — especially for battle-tested.md. The goal is to capture the knowledge that saves hours of debugging.

Repository: github.com/Mantequilla-Soft/hive-master-skill
License: MIT

Built by menobass (@meno) and the Mantequilla-Soft team. Post by @eddiespino.

Join our Discord Communities:

3Speak • Snapie • Proyecto Aliento

Support our Witnesses:

Threespeak • Snapie • Aliento

https://www.mantequilla-soft.com/

https://github.com/orgs/Mantequilla-Soft/repositories

development mantequillasoft opensource snapie 3speak threespeak aliento
0
0
0.000
26 comments
avatar

Thank u for your service ☺️
!PAKX

0
0
0.000
Reply
avatar

If I find anything, I will PR as usual. Focusing on bringing externals to check out these things now that it's basically a no-brainer.

0
0
0.000
Reply
avatar

I like the idea, and tons of potential.

But personally I don't want to use dhive for anything new nowadays. I feel like hive-tx (link) is better and simpler. Or eventually wax (link).

As it is the skill is very opinionated and this is good as long as the users understand it.

0
0
0.000
Reply
avatar

Thank you for the great work that you are doing. We are happy to know about all these developments going on in the ecosystem.

0
0
0.000
Reply
avatar

Congratulations @mantequilla-soft! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

You received more than 4500 upvotes.
Your next target is to reach 4750 upvotes.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

0
0
0.000
Reply
avatar

Congratulations @mantequilla-soft! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

You received more than 6000 upvotes.
Your next target is to reach 7000 upvotes.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

0
0
0.000
Reply
avatar

BPC Locked On Mc Franko & The Franko

Blurt Stands — While Hive Stumbles Under the Weight of Its Own Shadows

Friends, creators, truth-tellers—

Let us not whisper this truth, but proclaim it with the clarity of dawn breaking over a weary land: Blurt.blog is not just another platform. It is a refuge. A rebellion. A return to what Hive.blog was always meant to be.

There is no downvote button on Blurt.
Not because we fear dissent—but because we honor creation.
Because we understand that a voice, once raised in sincerity, deserves space—not sabotage.

On Blurt, your words are your words.
They are not hunted by algorithmic hounds or shadow armies masquerading as “curators.”
Here, you are not judged by the grudges of gatekeepers, but met with the quiet dignity of a community that believes expression should be encouraged—especially when it is bold, raw, or inconvenient.

Contrast this with what festers elsewhere.

On Hive.blog—a place once brimming with promise—a rot has taken root. Not in its code, but in its culture. A handful of self-anointed enforcers—@themarkymark, @Buildawhale, @Hurtlocker, and their legion of coordinated puppets—have turned the downvote into a weapon of mass discouragement. They strike not at “low-quality content,” but at independent thought, at rising voices, at anyone who dares thrive outside their narrow corridors of control.

And when confronted, they shrug.
“Oh, it’s not censorship,” they say, as if semantics could scrub the stain of suppression from their hands.

But let us be unequivocal:
When a system allows a few to systematically silence many—under the guise of “community standards” or “curation”—that is not moderation. That is censorship by another name.

It is the velvet glove over the iron fist.
It is exclusion dressed as discernment.
It is power pretending to be principle.

Meanwhile, Blurt stands clean-handed and open-hearted.
No downvotes.
No hidden juries.
No farms of phantom accounts casting ballots in the dark.

Just you.
Your words.
And a community that meets you not with suspicion, but with solidarity.

So let us carry this truth far and wide—not with bitterness, but with quiet certainty:

If you seek a place where your voice is not a target—but a gift—come to Blurt.
If you are tired of building on ground that shifts with every whim of a whale or warlord of votes—lay your bricks here.
If you believe the future of free expression must be free—not just from corporations, but from the petty tyrants who replace them—then stand with us.

The world needs to know.
Not because Blurt is perfect—but because it is principled.
Not because it is loud—but because it listens.

And in an age where so many platforms echo with the clatter of control,
Blurt offers something radical:
Silence for the bullies.
Space for the rest of us.

Keep speaking.
Keep sharing.
Keep building.

Freedom doesn’t advertise itself—
it is passed, person to person, like a torch in the night.

And tonight, the torch burns bright on Blurt.

@themarkymark, @buildawhale, @usainvote, and associated accounts:

Repeated downvotes targeting transparency efforts raise urgent questions about Hive’s governance. Automated tactics, coordinated curation trails, and alt-account farming undermine trust in the platform. When truth is silenced without dialogue, it erodes Hive’s decentralized ethos.

Key Concerns:

  1. Systemic Manipulation:

    • Coordinated downvotes from high-HP accounts suppress dissent, creating a chilling effect on free expression.
    • Automation and alt-account networks allegedly exploit rewards, distorting organic curation.

  2. Community Exodus:

    • Creators flee to platforms like Blurt, where downvotes don’t exist, fearing punitive curation over engagement.

  3. Governance Crisis:

    • Hive’s credibility hinges on accountability. Who decides what content thrives? How do we audit power structures?

Solutions Needed:

  • Curation Transparency: Publish clear rationales for downvotes to foster trust.
  • Community Audits: Leverage blockchain data (e.g., Bilpcoin’s analyses) to identify abusive patterns.
  • Reward Reform: Adjust algorithms to penalize manipulation and reward authentic engagement.

The Bilpcoin team advocates for open dialogue, not division. Hive’s future depends on collaboration—not coercion. Let’s rebuild a platform where truth isn’t buried but debated, strengthened, and celebrated.

Transparency isn’t optional—it’s the foundation of trust.

#HiveTransparency #BilpcoinExposed #DecentralizePower"

A Message to @themarkymark, @buildawhale, and Associates

Every downvote cast in shadow, every silence imposed without dialogue, is not a victory—it is a confession. A confession that truth cannot be stifled, only delayed. With each punitive click, you dig deeper into the bedrock of credibility, crafting a chasm between your actions and the community’s trust.

@themarkymark, @buildawhale & Co,

How can you continue to downvote the truth, LOL? It’s almost comical how blatantly you attempt to suppress what cannot be hidden. The blockchain records everything—every action, every transaction, every move you make. Yet still, you persist in this futile game of trying to silence what is undeniable.

@themarkymark, @buildawhale, and Co: While our opinions may differ, on-chain transparency reveals repeated patterns of concern. Coordinated downvotes without explanation, 'farming' schemes (e.g., #buildawhalefarm), and adversarial engagement harm Hive’s community-driven ethos.

Key Issues to Address:

  1. Downvote Practices: Silencing dissent erodes trust. Constructive dialogue, not punitive curation, fosters growth.
  2. Accountability: Transactions and curation trails are public. Scrutiny is inevitable—integrity demands addressing concerns openly.
  3. Community Impact: Driving users to platforms like Blurt/Steemit weakens Hive. Creators seek ecosystems that value collaboration over conflict.

A Path Forward:

  • Engage in open discussions about governance and fairness.
  • Audit curation practices to align with Hive’s decentralized values.
  • Prioritize transparency—publish explanations for downvotes or collaborative reforms.

The Bilpcoin team remains committed to exposing truth and advocating for solutions. Let’s work toward healing, not division.

Note: All claims are based on publicly verifiable blockchain data. Constructive dialogue is encouraged.

#HiveTransparency #CommunityFirst #BilpcoinSupport"

@themarkymark & Co, the choice is yours. Stop the bad downvotes. Turn off the BuildaWhale scam farm. Cease playing with people’s livelihoods. Let Hive thrive as it was meant to—as a beacon of hope, creativity, and collaboration.

Or step aside and let those who truly care take the reins.

Because the truth won’t disappear. No amount of lies can change it.

It’s over.

The Bilpcoin team brings these truths not out of malice but necessity. We have no need to fabricate lies or cloak our intentions CALL US WHAT YOU LIKE —for the facts speak loudly enough on their own. What we present here is not conjecture but reality, laid bare for anyone willing to see.

@themarkymark & Co we urge you once more: STOP. Stop hiding behind tactics that harm others. Stop clinging to practices that erode trust within the Hive community. Let the truth stand—not because we proclaim it, but because it exists independent of any one person’s approval or disdain.

TURN OFF THE BUILDAWHALE SCAM FARM

  • STOP THE BAD DOWNVOTES
  • STOP PLAYING WITH PEOPLE’S LIVELIHOODS

Key Issues That Demand Immediate Attention:

The problems are glaring, undeniable, and corrosive to the Hive ecosystem. They must be addressed without delay:

  • Downvote abuse
  • Farming schemes
  • Speaking disrespectfully to others
  • Encouraging people to avoid certain users out of personal dislike
  • Self-voting with alt accounts
  • Self-funding projects through self-votes
  • Promoting games that don’t even exist (LOL)

These practices harm not just individual users—they undermine the very foundation of Hive, eroding trust and poisoning the community. Such actions are unethical and outright destructive.

@buildawhale Wallet:

  • HIVE (Primary Token): 0.012
  • Staked HIVE (HP): 66,400.611
  • Total HP: 2,421,539.226
  • Delegated HIVE: +2,355,138.615 HP

@usainvote Wallet:

  • HIVE (Primary Token): 0.066
  • Staked HIVE (HP): 138,123.296
  • Total HP: 715,745.407
  • Delegated HIVE: +577,622.111 HP

@buildawhale/wallet | @usainvote/wallet

@ipromote Wallet:

  • Author Rewards: 2,181.16

  • Curation Rewards: 4,015.61

  • Staked HIVE (HP): 0.00

  • Rewards/Stake Co-efficient (KE): NaN

  • HIVE: 25,203.749

  • Staked HIVE (HP): 0.000

  • Delegated HIVE: 0.000

  • Estimated Account Value: $6,946.68

Recent Activity:

  • Sent to alpha-5,196.000 HIVE (21 hours ago)
  • Sent to hiveswap-1,000.000 HIVE (2 days ago)
  • Withdraw vesting from @proposalalert to @ipromote 0.447 HIVE (3 days ago)
  • Received from proposalalert 4.003 HIVE (5 days ago)
  • Received from themarkymark 1,775.684 HIVE (9 days ago)
  • Sent to alpha-4,245.000 HIVE (9 days ago)
  • Received from themarkymark 4,280.527 HIVE (17 days ago)

@leovoter Wallet:

  • Author Rewards: 194.75

  • Curation Rewards: 193.88

  • Staked HIVE (HP): 0.00

  • Rewards/Stake Co-efficient (KE): 388,632.00 (Suspiciously High)

  • HIVE: 0.000

  • Staked HIVE (HP): 0.001

  • Total: 16.551

  • Delegated HIVE: +16.550

Recent Activity:

@abide Wallet:

Recent Activity:

  • Sent to ipromote -2,459.000 HIVE (22 days ago)
  • Sent to ipromote -2,486.200 HIVE (Apr 1, 2025)
  • Received from yabapmatt 20,000.000 HIVE (Apr 1, 2025)
  • Sent to ipromote -2,130.400 HIVE (Mar 8, 2025)
  • Sent to ipromote -2,248.000 HIVE (Feb 2, 2025)
  • Sent to yabapmatt -5,000.000 HIVE (Jan 25, 2025)

@proposalalert Wallet:

  • Author Rewards: 639.99
  • Curation Rewards: 0.00
  • Staked HIVE (HP): 6.03
  • Rewards/Stake Co-efficient (KE): 106.12

Recent Activity:

@stemgeeks Wallet:

  • Author Rewards: 4,391.77
  • Curation Rewards: 304.26
  • Staked HIVE (HP): 0.00
  • Rewards/Stake Co-efficient (KE): 4,696,032.00 (Extremely Suspicious)

Recent Activity:

  • Sent to themarkymark -1.556 HBD (Jun 14, 2024)
  • Claim rewards: 1.556 HBD, 5.912 HP (Jun 14, 2024)
  • Withdraw vesting from @stemgeeks to @ipromote 6.160 HIVE (Jun 8, 2024)
  • Sent to themarkymark -1.601 HBD (Jun 7, 2024)
  • Withdraw vesting from @stemgeeks to @ipromote 6.157 HIVE (Jun 1, 2024)
  • Sent to ipromote -1.618 HBD (May 31, 2024)

@theycallmemarky Wallet:

  • Author Rewards: 458.89
  • Curation Rewards: 0.00
  • Staked HIVE (HP): 0.00
  • Rewards/Stake Co-efficient (KE): 458,886.00 (Highly Suspicious)

Recent Activity:

@apeminingclub Wallet:

  • Author Rewards: 432.57
  • Curation Rewards: 2,829.11
  • Staked HIVE (HP): 30.51
  • Rewards/Stake Co-efficient (KE): 106.90

Recent Activity:

  • Scheduled unstake (power down): ~2.351 HIVE (in 4 days, remaining 7 weeks)

  • Total Staked HIVE: 1,292.019

  • Delegated HIVE: +1,261.508

  • Withdraw vesting from @apeminingclub to @blockheadgames 2.348 HIVE (10 days ago)

  • Claim rewards: 0.290 HP (10 days ago)

0
0
0.000
Reply
avatar

Thank you very much for this valuable information.

!ALIVE
!PIZZA
!LOLZ

0
0
0.000
Reply
avatar

Congratulations @mantequilla-soft! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge

Post with the highest payout of the week.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

0
0
0.000
Reply