本文へ移動
cccskills
無料GitHub で公開

managing-census

Use when working with Census — census reverse ETL management — monitor syncs, destinations, models, source connections, and sync run health. Use when debugging sync failures, inspecting record delivery, auditing destination mappings, or reviewing sync schedules.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Managing Census

Manage and monitor Census reverse ETL — syncs, destinations, models, and sync run health.

Discovery Phase

#!/bin/bash

CENSUS_API="https://app.getcensus.com/api/v1"
AUTH="Authorization: Bearer $CENSUS_API_TOKEN"

echo "=== Sources ==="
curl -s -H "$AUTH" "$CENSUS_API/sources" \
  | jq -r '.data[] | [.id, .name, .type, .connection_details.host // "cloud"] | @tsv' | column -t | head -10

echo ""
echo "=== Destinations ==="
curl -s -H "$AUTH" "$CENSUS_API/destinations" \
  | jq -r '.data[] | [.id, .name, .type, .connection_details.instance_url // ""] | @tsv' | column -t | head -10

echo ""
echo "=== Models ==="
curl -s -H "$AUTH" "$CENSUS_API/models" \
  | jq -r '.data[] | [.id, .name, .source_id, .query[:50]] | @tsv' | column -t | head -15

echo ""
echo "=== Syncs ==="
curl -s -H "$AUTH" "$CENSUS_API/syncs" \
  | jq -r '.data[] | [.id, .label, .destination_object, .schedule_frequency, .paused] | @tsv' | column -t | head -15

Analysis Phase

#!/bin/bash

CENSUS_API="https://app.getcensus.com/api/v1"
AUTH="Authorization: Bearer $CENSUS_API_TOKEN"

echo "=== Recent Sync Runs ==="
curl -s -H "$AUTH" "$CENSUS_API/sync_runs?limit=15&order=desc" \
  | jq -r '.data[] | [.id, .sync_id, .status, .records_processed, .records_failed, .created_at] | @tsv' | column -t

echo ""
echo "=== Failed Sync Runs ==="
curl -s -H "$AUTH" "$CENSUS_API/sync_runs?status=failed&limit=10" \
  | jq -r '.data[] | [.id, .sync_id, .created_at, .error_message[:60]] | @tsv' | column -t

echo ""
echo "=== Sync Health Summary ==="
for SYNC_ID in $(curl -s -H "$AUTH" "$CENSUS_API/syncs" | jq -r '.data[:5][].id'); do
  SYNC_NAME=$(curl -s -H "$AUTH" "$CENSUS_API/syncs/$SYNC_ID" | jq -r '.data.label')
  LAST_RUN=$(curl -s -H "$AUTH" "$CENSUS_API/syncs/$SYNC_ID/sync_runs?limit=1" \
    | jq '{status: .data[0].status, records_processed: .data[0].records_processed, records_failed: .data[0].records_failed}')
  echo "$SYNC_NAME: $LAST_RUN"
done

echo ""
echo "=== Sync Field Mappings ==="
curl -s -H "$AUTH" "$CENSUS_API/syncs/$CENSUS_SYNC_ID" \
  | jq -r '.data.mappings[] | [.from.data, .to, .operation] | @tsv' | column -t | head -10

Output Format

SOURCES
ID       Name             Type         Host
<id>     <source-name>    <type>       <host>

DESTINATIONS
ID       Name             Type         Instance
<id>     <dest-name>      <type>       <url>

SYNCS
ID       Label            Object          Frequency   Paused
<id>     <sync-label>     <dest-object>   <freq>      false

SYNC RUNS
ID       Sync ID  Status      Processed  Failed   Created
<id>     <sid>    completed   <n>        <n>      <timestamp>

FAILED RUNS
ID       Sync ID  Created         Error
<id>     <sid>    <timestamp>     <message>

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Cloudflare GraphQL Analytics for zone traffic, firewall events, Workers metrics, and schema exploration. Use when querying Cloudflare analytics data or exploring the GraphQL API.

日本語の概要は準備中です。原文の説明を表示しています。

cloudthinker-ai/CloudSkills62026年4月5日 更新

Use when working with Alloydb — google AlloyDB instance analysis, query insights, columnar engine optimization, maintenance windows, and cluster health.

日本語の概要は準備中です。原文の説明を表示しています。

cloudthinker-ai/CloudSkills62026年4月5日 更新

Use when working with Aqua — aqua Security platform analysis. Covers container runtime protection, image assurance policies, compliance frameworks, vulnerability management, workload protection, and registry scanning. Use when analyzing container security posture, reviewing image compliance, investigating runtime alerts, or auditing security policies.

日本語の概要は準備中です。原文の説明を表示しています。

cloudthinker-ai/CloudSkills62026年4月5日 更新

Use when working with Bigquery — google BigQuery job analysis, slot utilization, cost analysis, dataset management, and query optimization.

日本語の概要は準備中です。原文の説明を表示しています。

cloudthinker-ai/CloudSkills62026年4月5日 更新

Use when working with Cassandra — apache Cassandra keyspace analysis, compaction strategies, repair status, nodetool operations, and cluster health monitoring.

日本語の概要は準備中です。原文の説明を表示しています。

cloudthinker-ai/CloudSkills62026年4月5日 更新

Use when working with Checkov — checkov infrastructure-as-code security scanning. Covers Terraform, CloudFormation, Kubernetes, and Dockerfile scanning, policy management, custom checks, compliance frameworks, and suppression management. Use when scanning IaC for security misconfigurations, evaluating compliance, managing custom policies, or reviewing scan results.

日本語の概要は準備中です。原文の説明を表示しています。

cloudthinker-ai/CloudSkills62026年4月5日 更新

cloudthinker-ai のスキルをすべて見る

このスキルの問題を報告する