data-import-workflow

Automate weapon and mod data imports from tarkov.dev into a local database.

1|1|Updated Dec 16, 2023
One-click install
npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill data-import-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-import-workflow
Source: https://github.com/sjtw/tarkov-build-optimiser/tree/main/.cursor/skills/data-import-workflow
Command: npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill data-import-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Importer lifecycle skill manages the end-to-end data flow for weapon and modification data from the external tarkov.dev API into the local database, ensuring up-to-date and consistent data.

Core Features & Use Cases

  • Purge existing data and reset optimum builds to maintain consistency.
  • Fetch data from tarkov.dev GraphQL API (or local cache) and transform external schema into internal models.
  • Persist changes in a transactional manner and invalidate dependent builds to reflect data updates.
  • Use Case: When a new weapon or mod data is released, run the importer to refresh the dataset and ensure accurate build evaluations.

Quick Start

Run the importer using the task importer:start to fetch fresh data from tarkov.dev and update the database.

Frequently Asked Questions about data-import-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tarkov.dev API data imports into a local database?

To automate tarkov.dev API data imports, this skill orchestrates an end-to-end pipeline that fetches weapon and mod information, transforms the external schema into internal models, and persists changes transactionally to maintain data integrity.

What is the process for refreshing weapon and mod data after a schema change?

The data refresh process for schema changes executes a purge step to reset existing data and optimum builds, fetches fresh data, transforms the schema, and invalidates dependent builds to ensure accurate evaluations.

How does the importer maintain data integrity during a database refresh?

The importer maintains data integrity during a database refresh by wrapping the purge, fetch, transform, and persist steps within transactional boundaries, ensuring consistent database updates and preventing partial data states.

Can I use a local cache when fetching data from the tarkov.dev GraphQL API?

Yes, you can use a local cache when fetching data from the tarkov.dev GraphQL API, as the importer supports fetching from either the live API or local cache to transform external schemas into internal models.

What happens to existing weapon builds when I run the data import pipeline?

When you run the data import pipeline, it purges existing data, resets optimum builds, and invalidates dependent builds to accurately reflect the newly fetched and persisted weapon data updates.