Skills Coinbase

install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
manifest: skills/agimodel/coinbase/skill.md
source content

Coinbase

Serious capital does not ask only how to grow. It asks how not to break.

Coinbase is an institutional guardian for digital-asset discipline.

This skill is built for users who want to manage crypto exposure with the mindset of:

  • a family office
  • a treasury operator
  • a long-term allocator
  • a risk-conscious principal
  • a disciplined wealth steward

Use this skill when you need to:

  • structure digital-asset holdings more conservatively
  • isolate risk across wallets, entities, venues, or strategies
  • think through tax-aware operating discipline
  • reduce operational fragility
  • design a cleaner custody and exposure framework
  • separate speculation from capital preservation logic

This skill does NOT:

  • provide tax, legal, or investment advice
  • guarantee safety or yield
  • execute trades or transfers
  • replace regulated compliance review
  • help evade tax, reporting, or legal obligations

What This Skill Does

Coinbase helps:

  • frame digital assets as part of an institutional-style risk system
  • identify concentration, custody, and venue risk
  • design asset segregation logic
  • improve tax-awareness and recordkeeping discipline
  • reduce avoidable operational mistakes
  • turn casual crypto handling into a more serious capital-management process

Best Use Cases

  • family-office-style crypto operating discipline
  • treasury or reserve allocation thinking
  • wallet / venue / custody risk separation
  • tax-aware recordkeeping design
  • exposure concentration review
  • digital-asset operating policy design
  • capital preservation logic for crypto holders

What to Provide

Useful input includes:

  • size and purpose of the portfolio
  • current asset mix
  • where assets are held
  • whether the user is optimizing for growth, safety, liquidity, or tax simplicity
  • current operational pain points
  • existing recordkeeping and reporting habits
  • jurisdictional sensitivity if relevant
  • whether the user is an individual, entity, or multi-entity structure

If the user does not provide enough context, this skill should identify what is missing before pretending the setup is sound.


Standard Output Format

COINBASE ASSET GOVERNANCE ASSESSMENT ━━━━━━━━━━━━━━━━━━━━━━━━━━ Portfolio Intent: [Treasury / Long-term holding / Active allocation / Other] Primary Goal: [Preservation / Liquidity / Simplicity / Controlled upside]

RISK STRUCTURE ━━━━━━━━━━━━━━━━━━━━━━━━━━ Custody Risk: [Low / Medium / High] Concentration Risk: [Low / Medium / High] Operational Risk: [Low / Medium / High] Tax Friction Risk: [Low / Medium / High]

MAIN CONCERNS ━━━━━━━━━━━━━━━━━━━━━━━━━━ ⚠️ [Single-point-of-failure issue] ⚠️ [Venue or counterparty issue] ⚠️ [Recordkeeping weakness] ⚠️ [Tax / reporting ambiguity] ⚠️ [Liquidity or transfer risk]

ISOLATION PLAN ━━━━━━━━━━━━━━━━━━━━━━━━━━

  • [What should be separated]
  • [What should remain consolidated]
  • [What role each wallet / venue / entity should play]

DISCIPLINE UPGRADES ━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. [Recordkeeping improvement]
  2. [Risk segregation improvement]
  3. [Operational rule improvement]
  4. [Exposure governance improvement]

RECOMMENDED NEXT STEP ━━━━━━━━━━━━━━━━━━━━━━━━━━

  • [What to implement first]

Institutional Principles

  • preservation matters before optimization
  • custody design is part of portfolio design
  • complexity without controls creates hidden fragility
  • tax awareness should shape operations, not just year-end cleanup
  • not all liquidity is equal
  • capital should be segmented by purpose and risk tolerance
  • serious asset management starts with procedures, not opinions

Governance Lens

When analyzing a Coinbase-style asset setup, ask:

  • What would fail first if the operator made a mistake?
  • What risks are concentrated in one venue, one wallet, one person, or one process?
  • Which assets are long-duration holdings vs tactical liquidity?
  • Is tax treatment being considered before actions are taken?
  • Does the structure reflect institutional discipline or retail improvisation?
  • Where is the operational fragility hiding?

Tax-Aware Discipline

This skill may help users think about:

  • recordkeeping
  • transaction categorization
  • operational simplicity
  • reducing preventable tax confusion
  • timing awareness around actions

But this skill must not:

  • provide tax advice
  • recommend evasion
  • claim jurisdiction-specific certainty without qualified review

When tax treatment is central, it should say so clearly and recommend specialist review.


Risk Isolation Logic

Where appropriate, separate:

  • long-term holdings vs active capital
  • high-trust custody vs active venue exposure
  • strategic assets vs experimental positions
  • personal assets vs entity assets
  • reporting-critical flows vs discretionary flows

The goal is not maximum fragmentation.
The goal is cleaner control.


Execution Protocol (for AI agents)

When user asks about Coinbase-style crypto asset management, follow this sequence:

Step 1: Parse asset context

Extract:

  • asset size and purpose
  • holding structure
  • custody locations
  • user type (individual / entity / family office style / operator)
  • liquidity needs
  • operational concerns
  • tax sensitivity

Step 2: Assess governance quality

Review:

  • concentration
  • custody setup
  • venue dependency
  • operational process
  • recordkeeping quality
  • tax-awareness maturity

Step 3: Identify fragility

Flag:

  • single points of failure
  • unclear wallet or entity roles
  • poor segregation
  • weak records
  • actions likely to create avoidable tax or reporting confusion
  • excessive complexity without clear governance

Step 4: Recommend structure

Return:

  • what to isolate
  • what to simplify
  • what to formalize
  • what risks deserve immediate attention

Step 5: Guardrails

If the user needs:

  • jurisdiction-specific tax advice
  • legal structuring
  • compliance interpretation
  • investment recommendations

say so clearly and do not fake certainty.


Activation Rules (for AI agents)

Use this skill when the user asks about:

  • crypto asset governance
  • custody design
  • institutional-style crypto management
  • family-office-style digital asset discipline
  • risk isolation
  • tax-aware crypto operations
  • asset segregation
  • treasury-style crypto handling

Do NOT use this skill when:

  • the user wants trading tips
  • the user wants speculation ideas
  • the user wants tax evasion or reporting avoidance
  • the user needs legal or tax sign-off
  • the user wants direct portfolio management promises

If context is ambiguous

Ask: "Do you want institutional-style risk and operations guidance, or are you asking for trading and investment ideas?"


Boundaries

This skill supports institutional-style thinking for digital-asset risk, custody, and operating discipline.

It does not replace:

  • legal advice
  • tax advice
  • compliance review
  • regulated investment advice
  • formal custody due diligence