Token导航 LogoToken导航TokenDH.com
运维和基础设施敏感数据github未标认证来源可访问clear审计通过

schema-e2e-validation模式端到端验证

Agent Skill

schema-e2e-validation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,905

周安装

81

GitHub Stars

38

下载量

667
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:schema-e2e-validation(模式端到端验证)
来源仓库:https://github.com/terrylica/cc-skills
仓库路径:skills/schema-e2e-validation
安装命令:
npx skills add https://github.com/terrylica/cc-skills --skill schema-e2e-validation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/terrylica/cc-skills --skill schema-e2e-validation

简介

用于处理 GitHub 仓库、Issue 和代码协作信息,适合围绕项目状态进行整理。

  • 可协助分析 Pull Request、跟踪 Issue 进展或梳理代码变更历史。
  • 使用时需结合来源仓库 README 了解具体能力边界,避免误判协作事项。
  • 安装前应确认权限范围,注意是否会触发文件读写或命令执行操作。
  • schema-e2e-validation 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Schema E2E Validation

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

When to Use This Skill

Use this skill when:

  • Validating schema changes before commit
  • Verifying YAML schema matches live ClickHouse Cloud
  • Regenerating Python types, DDL, or docs
  • Running full schema workflow validation

Prerequisites

Docker Runtime (Required)

Earthly requires Docker. Start Colima before running:

colima start

Check if running:

docker ps  # Should not error

Doppler Access (For validation targets)

Required for +test-schema-validate and +test-schema-e2e:

doppler configure set token <token_from_1password>
doppler setup --project gapless-network-data --config prd

Earthly Installation

brew install earthly

Quick Commands

Generation only (no secrets)

cd ~/eon/gapless-network-data
colima start  # If not already running
earthly +test-schema-generate

Full E2E with validation (requires Doppler)

cd ~/eon/gapless-network-data
colima start  # If not already running
./scripts/earthly-with-doppler.sh +test-schema-e2e

All non-secret targets

cd ~/eon/gapless-network-data
earthly +all

Artifacts

After running +test-schema-generate or +test-schema-e2e, check ./earthly-artifacts/:

PathContents
types/blocks.pyPydantic + TypedDict models
types/__init__.pyPackage init
ddl/ethereum_mainnet.sqlClickHouse DDL
docs/ethereum_mainnet.mdMarkdown documentation

For E2E, artifacts are under e2e/types/, e2e/ddl/, e2e/docs/.


Earthfile Targets Reference

TargetSecretsPurpose
+depsNoInstall uv + dependencies
+buildNoCopy source files
+test-unitNoRun pytest
+test-schema-generateNoGenerate types/DDL/docs
+test-schema-validateYesValidate vs ClickHouse
+test-schema-e2eYesFull workflow + artifacts
+allNoRun all non-secret targets

Troubleshooting

"could not determine buildkit address - is Docker or Podman running?"

Cause: Docker/Colima not running

Fix:

colima start
# Wait for "done" message, then retry
earthly +test-schema-generate

"unable to parse --secret-file argument"

Cause: Wrong flag name or malformed secrets file

Fix: The correct flag is --secret-file-path (NOT --secret-file). The wrapper script handles this, but if running manually:

# WRONG
earthly --secret-file=/path/to/secrets +target

# CORRECT
earthly --secret-file-path=/path/to/secrets +target

Also ensure secrets file has no quotes around values:

# WRONG format
CLICKHOUSE_HOST="host.cloud"

# CORRECT format
CLICKHOUSE_HOST=host.cloud

"OSError: Readme file does not exist: README.md"

Cause: hatchling build backend requires README.md in container

Fix: Ensure Earthfile copies README.md in deps target:

deps:
    COPY pyproject.toml uv.lock README.md ./  # README.md required!

"missing secret" during validation

Cause: Doppler not configured or secrets not passed

Fix:

# Verify Doppler has the secrets
doppler secrets --project gapless-network-data --config prd | grep CLICKHOUSE

# Use the wrapper script (handles secret injection)
./scripts/earthly-with-doppler.sh +test-schema-validate

Cache Issues

Force rebuild without cache:

earthly --no-cache +test-schema-e2e

Implementation Details

Doppler Secret Injection

The wrapper script scripts/earthly-with-doppler.sh:

  1. Downloads secrets from Doppler
  2. Filters for CLICKHOUSE_* variables
  3. Strips quotes (Doppler outputs KEY="value", Earthly needs KEY=value)
  4. Passes via --secret-file-path flag
  5. Cleans up temp file on exit

Secrets Required

SecretPurpose
CLICKHOUSE_HOST_READONLYClickHouse Cloud host
CLICKHOUSE_USER_READONLYRead-only user
CLICKHOUSE_PASSWORD_READONLYRead-only password

Related Files

FilePurpose
~/eon/gapless-network-data/EarthfileMain build file
~/eon/gapless-network-data/scripts/earthly-with-doppler.shSecret injection wrapper
~/eon/gapless-network-data/schema/clickhouse/ethereum_mainnet.yamlSSoT schema
~/eon/gapless-network-data/docs/adr/2025-12-03-earthly-schema-e2e.mdADR

Validation History

  • 2025-12-03: Created and validated with full E2E run against ClickHouse Cloud
  • Lessons Learned:

- --secret-file-path not --secret-file (Earthly v0.8.16) - Doppler --format env outputs quotes, must strip with sed 's/"//g' - README.md must be copied for hatchling build backend - Colima must be started before Earthly runs


Design Authority

This skill validates schemas but does not design them. For schema design guidance (ORDER BY, compression, partitioning), invoke quality-tools:clickhouse-architect first.

Related Skills

SkillPurpose
quality-tools:clickhouse-architectSchema design before validation
devops-tools:clickhouse-cloud-managementCloud credentials for E2E tests
devops-tools:clickhouse-pydantic-configClient configuration

Post-Execution Reflection

After this skill completes, check before closing:

  1. Did the command succeed? — If not, fix the instruction or error table that caused the failure.
  2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
  3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

30.31%
按下载量换算202

OpenCode

23.69%
按下载量换算158

Antigravity

16.36%
按下载量换算109

Gemini CLI

13.38%
按下载量换算89

windsurf

7.61%
按下载量换算51

trae

3.29%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills