Claude-skill-registry data-import-workflow
Managing the lifecycle of weapon and mod data from external sources to the local database
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/data-import-workflow" ~/.claude/skills/majiayu000-claude-skill-registry-data-import-workflow && rm -rf "$T"
manifest:
skills/data/data-import-workflow/SKILL.mdsource content
Data Import Workflow Skill
Use this skill when working on or running the data import pipeline.
Scope
- Running the importer to populate or refresh data
- Extending the importer to handle new fields or types
- Debugging import failures
Running the Importer
| Command | Use Case |
|---|---|
| Fetch fresh data from tarkov.dev API and update the database. |
| Use locally cached JSON files (faster, avoids API rate limits). |
| Fetch from API and update local cache, but skip database writes. |
Import Behavior
- Purge: Existing weapons, mods, trader offers, and optimum builds are deleted.
- Fetch: Data is retrieved from tarkov.dev GraphQL API (or local cache).
- Transform: External schema is mapped to internal
structs.models - Persist: Data is written to the database within a transaction.
- Invalidate:
are purged since they depend on the imported data.optimum_builds
Extending the Importer
When adding new fields or types:
- Update GraphQL Query: Modify
.internal/tarkovdev/schemas/queries.graphql - Regenerate Client: Run
.task tarkovdev:regenerate - Update Models: Add new fields to structs in
.internal/models/ - Update Mapping: Adjust conversion logic in
.internal/importers/ - Update SQL: Modify
functions inUpsert
to include new columns.internal/models/
Troubleshooting
- Rate Limiting: Use
for repeated runs during development.--use-cache - Schema Mismatch: Run
thentask tarkovdev:get-schema
.task tarkovdev:regenerate - Connection Issues: Verify
inPOSTGRES_HOST
and ensure the database is running..env