Skip to content

cloudthinker-ai/CloudSkills / skills/connections/managing-height

managing-height

Verified

Use when working with Height — height.app project management covering tasks, lists, workspaces, and team activity analytics. Use when auditing Height workspace usage, managing tasks and lists, analyzing team workload, or reviewing project progress across a Height workspace.

Managing Height

Height workspace management and analytics via the Height REST API.

Discovery Phase

#!/bin/bash
HEIGHT_BASE="https://api.height.app"

echo "=== Workspace Info ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/workspace" | jq '{id, name, url}'

echo ""
echo "=== Lists ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/lists" \
  | jq -r '.list[] | "\(.id)\t\(.name[0:30])\t\(.type)\t\(.archivedAt // "active")"' | column -t

echo ""
echo "=== Users ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/users" \
  | jq -r '.list[] | "\(.id)\t\(.username)\t\(.email)\t\(.state)"' | column -t

echo ""
echo "=== Field Templates ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/fieldTemplates" \
  | jq -r '.list[]? | "\(.id)\t\(.name)\t\(.type)"' | column -t | head -15

Analysis Phase

#!/bin/bash
HEIGHT_BASE="https://api.height.app"
LIST_ID="${1:?List ID required}"

echo "=== List Tasks ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/lists/$LIST_ID/tasks" \
  | jq -r '.list[] | "\(.index)\t\(.name[0:40])\t\(.status)\t\(.assigneesIds | length) assignees"' | column -t | head -25

echo ""
echo "=== Task Status Distribution ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/lists/$LIST_ID/tasks" \
  | jq '[.list[].status] | group_by(.) | map({status: .[0], count: length}) | sort_by(-.count)[]'

echo ""
echo "=== Unassigned Tasks ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/lists/$LIST_ID/tasks" \
  | jq '[.list[] | select(.assigneesIds | length == 0)] | {unassigned: length, tasks: [.[:5][] | {name: .name[0:40], status}]}'

echo ""
echo "=== Recent Activity ==="
curl -s -H "Authorization: api-key $HEIGHT_API_KEY" \
  "$HEIGHT_BASE/activities?listId=$LIST_ID" \
  | jq -r '.list[:10][] | "\(.createdAt[0:16])\t\(.type)\t\(.user.username // "system")"' | column -t

Output Format

HEIGHT WORKSPACE HEALTH
Workspace:     [name]
Total Lists:   [count] ([active] active)
Total Users:   [count]

LIST HEALTH: [list_name]
Total Tasks:   [count]
Unassigned:    [count]

STATUS DISTRIBUTION
Status         Count   Pct
backLog        [n]     [pct]%
inProgress     [n]     [pct]%
done           [n]     [pct]%

Anti-Hallucination Rules

  1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
  2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
  3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
  4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
  5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations

ShortcutCounterWhy
"I'll skip discovery and check known resources"Always run Phase 1 discovery firstResource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"Follow the full discovery → analysis flowQuick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"Audit configuration explicitlyDefaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"Always check relevant metrics when availableAPI/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 errorAssumed permission failures prevent useful investigation; actual errors are informative
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 465kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 465kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 465kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 192kUpdated Claude CodeCodexVerifiedInstall