setup-lmfdb-pipeline
暂无简介
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
03 SKILL.md 正文
setup-lmfdb-pipeline
Meta-setup: create both project-local, gitignored confs that the mathcity-lmfdb server and database skills read. Private values (hostnames, users, SSH keys, schema names) live ONLY in the resulting files — never in pack content, the conversation transcript, or git history (POLICY.md P1.10).
Dependency check
ROOT="$(git rev-parse --show-toplevel 2>/dev/null)"
PIPELINE_CONF="$ROOT/lmfdb-pipeline.conf"
SERVER_CONF="$ROOT/lmfdb-server.conf"
if [ -f "$PIPELINE_CONF" ] && [ -f "$SERVER_CONF" ]; then
echo "I'm sorry, I can't do that — both lmfdb-pipeline.conf and lmfdb-server.conf already exist."
echo "Nothing to set up. To reconfigure, back up and remove the conf you want to recreate:"
echo " cp \"$PIPELINE_CONF\" \"${PIPELINE_CONF}.bak\" && rm \"$PIPELINE_CONF\""
echo " cp \"$SERVER_CONF\" \"${SERVER_CONF}.bak\" && rm \"$SERVER_CONF\""
exit 1
fi
If only one conf exists, the corresponding sub-skill (configure-database or configure-server) will report "I'm sorry, I can't do that — conf already exists" and stop. The other sub-skill runs normally.
Procedure
Run both sub-skills in sequence:
mathcity-lmfdb.configure-database— createslmfdb-pipeline.confat the project root (PGDATABASE, PGSCHEMA, DATA_DIR, SCHEMA_MD).mathcity-lmfdb.configure-server— createslmfdb-server.confat the project root (REMOTE_HOST, REMOTE_USER, REMOTE_REPO, SSH_JUMP, SSH_KEY, MAX_PARALLEL, ALERT_EMAILS).
Each sub-skill handles its own gitignore check and validation step. If either
reports blocked, stop and surface the exact failing step to the user before
continuing.
Output
ready (both confs created, gitignored, and validated) or blocked with the
sub-skill and step that failed. Never print conf contents.
See also
mathcity-lmfdb.configure-database— database/pipeline conf onlymathcity-lmfdb.configure-server— SSH/compute-server conf onlyassets/lmfdb-pipeline.conf.example— database conf templateassets/lmfdb-server.conf.example— server conf template- POLICY.md P1.10 (no private values) and P1.12 (this skill's reason to exist)
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code