菜单
Follow the project workflow when adding or modifying shell or Python scripts. Use when the user asks to add a script, create a new script, modify a script, or write a script for a task. Ensures POSIX bash, common.sh, documentation in SCRIPTS.md, and tests are created or updated and run.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Workflow for generating and sending DPLA monthly pre-ingest emails to hub partners via AWS SES. Use this skill whenever someone asks to: send the monthly ingest email, prepare the DPLA pre-ingest notice, generate the hub email for a given month, preview the pre-ingest email, or do anything involving the pre-ingest email pipeline. Trigger even if the user just says something like "time to send the ingest email" or "it's email day" — context from the project makes the intent clear.
Run Community Webs ingest. Use when the user says harvest community-webs, run community-webs ingest, export community webs, or process community webs DB.
Remove DPLA items from the live site and search index in response to takedown requests. Use when the user says take down, delete, remove item(s) from dp.la, or action a takedown request. Accepts DPLA IDs directly or criteria (hub, institution, collection) to generate an ID list. Includes mandatory pre-flight verification, search-before-delete on Elasticsearch, and post-deletion confirmation with count delta verification.
Show key i3.conf config for a hub (provider, harvest.type, harvest.endpoint, schedule, email, setlist). Use when user asks for hub config, harvest type/endpoint, who gets emails, schedule months, or OAI setlist details.
Debug and fix DPLA hub ingestion failures (harvest/mapping/enrichment/jsonl/s3-sync/anomaly). Use when user asks why a hub failed, to debug an ingest failure, check an escalation report, or retry a failed hub/stage.
Show all active and completed ingests in one consolidated view. Use when user asks status of the ingests, ingest status, which hubs are running, show active ingests, or ingest progress.
| name | dpla-script-workflow |
| description | Follow the project workflow when adding or modifying shell or Python scripts. Use when the user asks to add a script, create a new script, modify a script, or write a script for a task. Ensures POSIX bash, common.sh, documentation in SCRIPTS.md, and tests are created or updated and run. |
When adding or modifying scripts in this repo, follow the project's conventions so scripts are documented, portable, and tested.
Environment: When running the test suite or any script that depends on project env, run source .env from repo root first.
./venv/ (e.g. ./venv/bin/python or source ./venv/bin/activate). Never assume system Python.--profile dpla for any AWS commands.sed -i, readlink -f). Use helpers from scripts/common.sh: sed_i, get_script_dir, get_common_dir, log_info, die, etc.scripts/common.sh if bash (source it, use its helpers).scripts/tests/test-scripts.sh (or under scripts/tests/ as appropriate)../scripts/tests/test-scripts.sh (or --quick for syntax) before committing../scripts/tests/test-scripts.sh before committing.| Resource | Path |
|---|---|
| Script docs | scripts/SCRIPTS.md |
| Updating docs | SCRIPTS.md section "Updating This Documentation" |
| Shared helpers | scripts/common.sh |
| Test suite | scripts/tests/test-scripts.sh |
# Run full script test suite
./scripts/tests/test-scripts.sh
# Quick syntax / lightweight checks
./scripts/tests/test-scripts.sh --quick
# Verbose test output
./scripts/tests/test-scripts.sh --verbose
scripts/ with shebang #!/usr/bin/env bash, set -euo pipefail, and source "$(get_script_dir)/common.sh" (or equivalent via get_common_dir).sed_i, get_script_dir, log_info, die instead of raw sed -i or readlink -f.scripts/tests/test-scripts.sh (e.g. syntax check, help output, or sourcing common.sh)../scripts/tests/test-scripts.sh and fix any failures.