tracker-scenario-import-export

Synchronize test scenarios between XLSX files and the PICASso SQLite tracker database.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/VBaranouski/PIC_Automation --skill tracker-scenario-import-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracker-scenario-import-export
Source: https://github.com/VBaranouski/PIC_Automation/tree/main/.agents/skills/tracker-scenario-import-export
Command: npx skills add https://github.com/VBaranouski/PIC_Automation --skill tracker-scenario-import-export

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Tracker Scenario Import/Export skill streamlines keeping the PICASso tracker database in sync with XLSX files, reducing manual data entry and ensuring consistency between the DB and scenario spreadsheets.

Core Features & Use Cases

  • Export: generate area-specific scenario sheets from the DB to XLSX for review and editing.
  • Import: load updated scenarios from XLSX back into the DB with a safe dry-run to preview changes before writing.
  • Workflows: supports area-based validation, dry-runs, and user confirmation steps to guard data integrity across auth, landing, products, releases, doc, reports, backoffice, integrations, and other areas.

Quick Start

Export or import tracker scenarios by area via XLSX files and validate changes before applying them to the DB.

Frequently Asked Questions about tracker-scenario-import-export

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

FAQPage Schema
How do I export test scenarios from a SQLite tracker database to an Excel file?

Exporting test scenarios from a SQLite tracker database to an Excel file involves generating area-specific scenario sheets from the database to XLSX for review and editing using dedicated scripts.

Can I import updated test scenarios from an Excel spreadsheet back into the tracker database safely?

Yes, you can import updated scenarios from an Excel spreadsheet back into the tracker database safely by using a dry-run option to preview changes and a safe write phase with user confirmation to guard data integrity.

What is the best way to prevent data loss when synchronizing test scenarios between an Excel file and a database?

Preventing data loss when synchronizing test scenarios between an Excel file and a database requires validating changes and previewing updates with a dry-run option before applying them to the database.

Does the scenario import and export workflow support all feature areas like auth, products, and reports?

Yes, the scenario import and export workflow supports area-based validation across all feature areas including auth, landing, products, releases, doc, reports, backoffice, integrations, and other.

How do I validate changes before applying imported XLSX tracker data to the database?

Validating changes before applying imported XLSX tracker data to the database involves running a dry-run to preview changes and executing user confirmation steps to ensure data integrity prior to the write phase.