cloudthinker-ai/CloudSkills / skills/connections/managing-baselime
managing-baselime
VerifiedUse when working with Baselime — baselime serverless observability platform for AWS Lambda, CloudFlare Workers, and Vercel functions. Covers log and trace querying, alert management, service discovery, and performance analysis of serverless workloads. Use when investigating serverless function performance, querying Baselime events, managing alerts, or analyzing cold start and duration metrics.
Baselime Monitoring Skill
Query, analyze, and manage Baselime observability data using the Baselime API.
API Overview
Baselime uses a REST API at https://api.baselime.io/v1.
Core Helper Function
#!/bin/bash
bl_api() {
local method="$1"
local endpoint="$2"
local data="${3:-}"
if [ -n "$data" ]; then
curl -s -X "$method" "https://api.baselime.io/v1/${endpoint}" \
-H "Authorization: Bearer $BASELIME_API_KEY" \
-H "Content-Type: application/json" \
-d "$data"
else
curl -s -X "$method" "https://api.baselime.io/v1/${endpoint}" \
-H "Authorization: Bearer $BASELIME_API_KEY"
fi
}
bl_query() {
local query_json="$1"
bl_api POST "query" "$query_json"
}
MANDATORY: Discovery-First Pattern
Always discover environments, services, and datasets before querying.
Phase 1: Discovery
#!/bin/bash
echo "=== Environments ==="
bl_api GET "environments" | jq -r '.[] | "\(.id)\t\(.name)"' | head -10
echo ""
echo "=== Services ==="
bl_api GET "services" | jq -r '.[] | "\(.name)\t\(.type // "unknown")\t\(.runtime // "N/A")"' | head -20
echo ""
echo "=== Datasets ==="
bl_api GET "datasets" | jq -r '.[] | "\(.id)\t\(.name)"' | head -15
echo ""
echo "=== Alerts ==="
bl_api GET "alerts" | jq -r '.[] | "\(.id)\t\(.name)\t\(.enabled)\t\(.threshold // "N/A")"' | head -15
Phase 2: Analysis
#!/bin/bash
echo "=== Lambda Performance (last 1h) ==="
bl_query '{
"datasets": ["lambda-logs"],
"calculations": [
{"operator": "COUNT"},
{"operator": "P95", "key": "duration"},
{"operator": "AVG", "key": "duration"}
],
"groupBy": ["@service"],
"timeframe": "1h",
"limit": 15
}' | jq -r '.results[] | "\(.group["@service"])\tcount:\(.COUNT)\tp95:\(.P95 // "N/A")ms\tavg:\(.AVG // "N/A")ms"' | head -15
echo ""
echo "=== Error Events ==="
bl_query '{
"datasets": ["lambda-logs"],
"filters": [{"key": "@level", "operator": "=", "value": "error"}],
"calculations": [{"operator": "COUNT"}],
"groupBy": ["@service"],
"timeframe": "1h",
"limit": 15
}' | jq -r '.results[] | "\(.group["@service"])\t\(.COUNT) errors"' | sort -t$'\t' -k2 -rn | head -15
echo ""
echo "=== Cold Starts ==="
bl_query '{
"datasets": ["lambda-logs"],
"filters": [{"key": "@initDuration", "operator": "exists"}],
"calculations": [{"operator": "COUNT"}, {"operator": "AVG", "key": "@initDuration"}],
"groupBy": ["@service"],
"timeframe": "1h",
"limit": 15
}' | jq -r '.results[] | "\(.group["@service"])\tcold_starts:\(.COUNT)\tavg_init:\(.AVG // "N/A")ms"' | head -15
Output Rules
- TOKEN EFFICIENCY: Target ≤50 lines — use
limitandgroupByfor aggregation - Use calculations with groupBy for service-level summaries
- Filter at query level before post-processing
Output Format
Present results as a structured report:
Managing Baselime Report
════════════════════════
Resources discovered: [count]
Resource Status Key Metric Issues
──────────────────────────────────────────────
[name] [ok/warn] [value] [findings]
Summary: [total] resources | [ok] healthy | [warn] warnings | [crit] critical
Action Items: [list of prioritized findings]
Target ≤50 lines of output. Use tables for multi-resource comparisons.
Anti-Hallucination Rules
- NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
- NEVER fabricate metric names or dimensions — verify against the service documentation or
--helpoutput. - NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
- ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
- ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.
Counter-Rationalizations
| Shortcut | Counter | Why |
|---|---|---|
| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |