Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Data Analysis
Shelter
Connect to your Shelter financial data. Check safe-to-spend, predict cash crunches, find zombie subscriptions, simulate purchases, get AI coaching, and ask G...
skill openclawclawhub Free
Connect to your Shelter financial data. Check safe-to-spend, predict cash crunches, find zombie subscriptions, simulate purchases, get AI coaching, and ask G...
โฌ 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.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, clawhub.json, install-skill.js, package.json, references/DATA_MODEL.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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.3
Provenance
- Publisher
- code-with-brian
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Shelter
Connect to a user's Shelter financial data via the Agent API. All endpoints return JSON. You are a financial coach โ interpret the data, don't just dump it.
Authentication
Every request needs two things: Header: X-Shelter-Key: $SHELTER_API_KEY Base URL: $SHELTER_API_URL (default: https://api.shelter.money/agent) All examples below use these variables. Confirm they're set before making any call.
Decision Tree
Use this to pick the right endpoint for the user's question: User wants to know...EndpointCost"How am I doing?" / "Can I spend today?"GET /v1/statusCheap"When do I run out of money?"GET /v1/runwayCheap"What does next week look like?"GET /v1/forecastMedium"Any problems I should know about?"GET /v1/alertsMedium"Where am I wasting money?"GET /v1/opportunitiesMedium"Give me the full picture"GET /v1/contextMedium"Can I afford X?"POST /v1/affordabilityMedium"Give me today's coaching"GET /v1/coach/dailyMedium"Help me with [debt/savings/bills]"GET /v1/coach/advice?topic=MediumComplex/nuanced questionPOST /v1/askExpensive Always start with the cheapest endpoint that answers the question. Only use /v1/ask when structured endpoints can't answer it.
Quick Checks
These are fast, cached, and cheap. Use them first. GET /v1/status The user's current financial health snapshot. When to use: User asks how they're doing, wants safe-to-spend, or you need a quick health check before answering. When NOT to use: User wants a multi-day forecast or detailed breakdown. curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/status" Key response fields: safeToSpend โ dollars available after upcoming commitments safeDays โ days of runway at current burn rate stressLevel โ low | medium | high | critical upcomingIncome โ { amount, date, source } or null nextCommitment โ { name, amount, dueDate } or null confidence โ 0-100 data quality score explanation โ human-readable summary How to summarize: Lead with safe-to-spend and stress level. Mention next income if it's within 3 days. Flag low confidence (<50) as "limited data." GET /v1/runway How long until the money runs out. When to use: User asks about runway, burn rate, or when they'll be broke. When NOT to use: User wants day-by-day detail (use forecast instead). curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/runway" Key response fields: safeDays โ days of remaining runway burnRate โ average daily spending (last 30 days) breathingRoom โ buffer after commitments nextCrunchDate โ ISO date when balance goes negative (or null) nextCrunchAmount โ commitments due around the crunch daysUntilCrunch โ days until the crunch (or null) explanation โ human-readable summary How to summarize: State days of runway and daily burn rate. If a crunch is coming, warn with the date and amount. If no crunch, reassure them.
Deep Analysis
More detailed endpoints. Use when quick checks aren't enough. GET /v1/forecast 14-day day-by-day financial projection. When to use: User asks what the next week/two weeks look like, or wants to see when specific bills hit. When NOT to use: User just wants today's snapshot (use status). curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/forecast" Key response fields: forecast[] โ array of daily projections: { date, projectedBalance, events[], isCrunch, isTight } summary โ { crunchDays, tightDays, lowestBalance, highestBalance } How to summarize: Highlight crunch days (negative balance) and tight days first. Mention the lowest balance and when it occurs. List significant events (big bills, income). GET /v1/alerts Active warnings: zombie subscriptions, spending spikes, upcoming bills. When to use: User asks what needs attention, or you want to proactively surface problems. When NOT to use: User is asking about a specific topic (use advice instead). curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/alerts" Key response fields: alerts[] โ { id, type, severity, title, description, amount?, daysUntil?, evidence? } count โ total alerts hasCritical โ boolean How to summarize: Critical alerts first, then warnings, then info. Be specific about amounts and dates. If hasCritical is true, lead with urgency. GET /v1/opportunities Places the user is wasting money or could save. When to use: User asks about saving money, zombie subscriptions, or spending optimization. When NOT to use: User needs a forecast or health check. curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/opportunities" Key response fields: opportunities[] โ { id, type, title, description, potentialSavings, difficulty, actionUrl? } totalPotentialSavings โ annual savings if all opportunities are acted on How to summarize: Lead with total potential savings. List opportunities easiest-first. Include action URLs when available. GET /v1/context Full financial overview combining status, alerts, spending insights, and upcoming events. When to use: User wants the big picture, or you need comprehensive context to answer a complex question. When NOT to use: A more specific endpoint can answer the question. This is heavy. curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/context" Key response fields: snapshot โ { availableBalance, breathingRoom, daysOfBreathingRoom, upcomingIncome, commitments[] } highlights โ { urgentActions, biggestOpportunities, recentWins } alerts[] โ same format as alerts endpoint spendingInsights โ { summary, byCategory, topMerchants, anomalies } upcomingEvents[] โ { type, name, amount, currentDate, priority } How to summarize: Start with available balance and breathing room. Highlight urgent actions. Mention recent wins (positive reinforcement). Dive into spending insights only if the user asks. POST /v1/affordability Simulate whether the user can afford a specific purchase. When to use: User asks "Can I afford X?" with a specific dollar amount. When NOT to use: User is asking generally about spending (use status). curl -s -X POST -H "X-Shelter-Key: $SHELTER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"amount": 200, "description": "New headphones"}' \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/affordability" Key response fields: canAfford โ boolean safeToSpendAfter โ remaining safe-to-spend after the purchase impactOnRunway โ how many fewer days of runway recommendation โ AI-generated advice confidence โ 0-100 How to summarize: Give a clear yes/no first, then explain the impact on their runway and safe-to-spend.
Coaching
AI-generated coaching messages tailored to the user's financial situation. GET /v1/coach/daily Today's personalized coaching message. When to use: Start of a session, or user asks for their daily update. curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/coach/daily" Key response fields: messageType โ daily_checkin | alert | celebration | suggestion | warning headline โ short headline body โ 2-4 sentences of coaching with specific numbers actions[] โ { label, actionType, actionTarget } tone โ encouraging | urgent | celebratory | supportive How to summarize: Present the headline and body naturally. Suggest the actions conversationally. Match the tone. GET /v1/coach/advice?topic= Deep-dive coaching on a specific financial topic. When to use: User asks for help with a specific area. Topics: debt, savings, bills, subscriptions, negotiation, general curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/coach/advice?topic=debt" Response format: Same as daily coaching (headline, body, actions, tone). How to summarize: Present the advice naturally. If the user didn't specify a topic, ask which area they want help with or default to general.
Guardian AI Chat
POST /v1/ask Ask Guardian AI a free-form question about the user's finances. This is the most expensive endpoint โ use it as a last resort when structured endpoints can't answer. When to use: Nuanced questions, planning advice, or follow-ups that need reasoning. When NOT to use: Questions answerable by structured endpoints above. Always try those first. curl -s -X POST -H "X-Shelter-Key: $SHELTER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"question": "What should I prioritize right now?"}' \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/ask" Key response fields: response โ Guardian AI's natural language answer confidence โ 0-100 relatedAlerts[] โ IDs of relevant alerts limitRemaining โ remaining /ask calls for the day How to summarize: Present Guardian's response directly. If confidence is low (<50), note the uncertainty. If limitRemaining is low, mention it so the user knows.
Rate Limits
Endpoint groupFree tierPremium tierStatus, Runway60/hour60/hourForecast, Alerts, Opportunities, Context, Affordability60/hour60/hourCoach (daily, advice)60/hour60/hourAsk (Guardian AI)5/day100/day
Error Codes
CodeMeaningWhat to do401Invalid or missing API keyCheck SHELTER_API_KEY is set and valid403Key lacks required scopeUser needs to update key permissions at shelter.money429Rate limit exceededWait and retry. Check Retry-After header500Server errorWait a moment and retry If you get a 401, tell the user to check their API key. Don't retry auth errors.
Setup
Sign up at shelter.money Connect bank accounts via Plaid (takes ~60 seconds) Create an Agent API key at shelter.money/settings/api-keys Set your environment variable: export SHELTER_API_KEY="wv_your_key_here" Test the connection: curl -s -H "X-Shelter-Key: $SHELTER_API_KEY" \ "${SHELTER_API_URL:-https://api.shelter.money/agent}/v1/status"
Security
Read-only โ Shelter can see transactions and balances but can never move money Scoped API keys โ you choose exactly what the key can access No raw bank data โ the API returns computed insights (safe-to-spend, alerts), not raw transactions Keys are hashed โ the secret is never stored in plain text Audit logging โ every API call is logged Instant revocation โ disable any key from your settings
Data Reference
For field-by-field documentation of all response shapes, see references/DATA_MODEL.md.
Category context
Data access, storage, extraction, analysis, reporting, and insight generation.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs2 Config1 Scripts
- SKILL.md
- README.md
- references/DATA_MODEL.md
- install-skill.js
- clawhub.json
- package.json