Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

dstack-setup

Estrelas0

Forks0

Atualizado2 de abril de 2026 às 17:39

Check and verify the Upsolve MCP connection and data-stack prerequisites. Use when first setting up, troubleshooting a connection issue, or verifying the environment is ready for data analysis. Trigger phrases: "setup", "check connection", "is Upsolve connected?", "troubleshoot", "verify setup", "MCP not working".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Upsolve-Labs

Upsolve-Labs/data-stack

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Cientistas de dadosInformática e Matemática·SOC 15-2051

SKILL.md

readonly

Mais deste repositório

mesmo repositório

dstack-advisor

Upsolve-Labs/data-stack

Recommends which data skill to run next. Use when starting a new analysis session or unsure where to begin. Asks what you are trying to accomplish and recommends the right skill with reasoning. Trigger phrases: "where should I start?", "what skill should I use?", "advisor", "help me figure out what to run", "I don't know where to begin".

2026-04-020

dstack-compare

Upsolve-Labs/data-stack

Period-over-period or cohort comparison. Use to understand what changed between two time periods, groups, or experiments. Breaks down the delta by key dimensions to find where the difference comes from. Trigger phrases: "last week vs prior week", "before vs after launch", "compare these two groups", "A/B results", "what changed?", "why is X different?".

2026-04-020

dstack-explore

Upsolve-Labs/data-stack

Dataset discovery and schema mapping. Use when starting fresh with data, exploring what's available, or mapping a new data source. Opens an Upsolve thread, surfaces available tables and schemas, profiles row counts and key columns, and outputs a structured data map. Strongly recommended as the first step before any analysis. Trigger phrases: "what data do I have?", "show me my tables", "explore this dataset", "what's available?", "I'm new to this data".

2026-04-020

dstack-funnel

Upsolve-Labs/data-stack

Funnel drop-off analysis. Define conversion steps and get conversion rates, absolute drop-off counts, and segment breakdowns at each stage. Use for product analytics, marketing funnels, checkout flows, or any sequential user journey. Trigger phrases: "funnel analysis", "where are users dropping off?", "conversion rate", "show me the funnel", "why aren't users converting?".

2026-04-020

dstack-investigate

Upsolve-Labs/data-stack

Anomaly root cause analysis. Use when a metric looks wrong or surprising. Runs a structured 4-phase investigation over a single Upsolve thread: confirm → narrow → hypothesize → validate. Findings use numbered codes (1A CONFIRMED, 1B CANDIDATE, 2A RULED_OUT). Trigger phrases: "revenue dropped", "metric is spiking", "why did X change?", "something looks wrong", "root cause", "debug this metric".

2026-04-020

dstack-metric-brief

Upsolve-Labs/data-stack

KPI deep dive report. Given a metric name, produces a structured brief: current value, WoW and MoM trend, top contributing segments, and notable outliers. Outputs a shareable summary for Slack, docs, or stakeholder updates. Trigger phrases: "summarize this metric", "metric brief", "what's happening with X", "give me a KPI summary", "how is [metric] doing?", "weekly metric update".

2026-04-020

name	dstack-setup
description	Check and verify the Upsolve MCP connection and data-stack prerequisites. Use when first setting up, troubleshooting a connection issue, or verifying the environment is ready for data analysis. Trigger phrases: "setup", "check connection", "is Upsolve connected?", "troubleshoot", "verify setup", "MCP not working".
disable-model-invocation	true
license	MIT
metadata	{"author":"Upsolve Labs"}

Update Check (run first)

_UPD=$(~/.claude/skills/data-stack/bin/data-stack-update-check 2>/dev/null || .claude/skills/data-stack/bin/data-stack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true

If output shows UPGRADE_AVAILABLE <old> <new>: read ~/.claude/skills/data-stack/skills/dstack-upgrade/SKILL.md and follow the "Inline upgrade flow". If JUST_UPGRADED <from> <to>: tell user "Running data-stack v{to} (just updated!)" and continue.

Setup

Check Upsolve MCP Connection

Test the Upsolve MCP by calling:

analyze_data("List available tables or confirm the connection is working.")

Report the result:

Check	Status
Upsolve MCP reachable	✓ / ✗
Project configured	✓ / ✗
Tables accessible	✓ / ✗

If Connection Fails

Common issues and fixes:

No project found:

"Upsolve MCP is connected but has no project set up. Visit upsolve.ai to create a project, then reconnect the MCP."

MCP not reachable:

"The Upsolve MCP tool is not available in this session. Make sure the MCP server is configured in your Claude Code settings under MCP servers."

Authentication error:

"Upsolve MCP authentication failed. Check your API key in the MCP server configuration."

Check data-stack Prerequisites

Run checks silently, then report:

Tool	Check	Required By
data-stack bin	`ls ~/.claude/skills/data-stack/bin/`	all skills

Verify Skill Symlinks

List all skills in ~/.claude/skills/ that point to the data-stack repo. Report any broken or missing symlinks. If symlinks are broken: suggest re-running install.sh.