data-schemas

Define standardized CSV data schemas for SmartSpender transactions, receipts, and payslips.

6|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/peerjakobsen/smartspender --skill data-schemas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-schemas
Source: https://github.com/peerjakobsen/smartspender/tree/main/skills/data-schemas
Command: npx skills add https://github.com/peerjakobsen/smartspender --skill data-schemas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Data structure definitions for all SmartSpender CSV files. Reference this when reading or writing to any data file.

Core Features & Use Cases

  • Standardizes the CSV schemas for all core artifacts: transactions, receipts, receipt items, payslips, subscriptions, and analytics.
  • Enables consistent validation, deduplication, and cross-file relationships across modules.
  • Serves as a single source of truth for file formats used by import, export, and reporting workflows.

Quick Start

Use these schemas to validate CSVs during import and to generate correctly structured output files.

Frequently Asked Questions about data-schemas

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

FAQPage Schema
How do I standardize CSV data structures for transactions and payslips?

Deduplication in CSV data schemas prevents redundant records by specifying cross-file relationships and validation rules. It maintains data integrity across modules like transactions and receipts, ensuring accurate analytics and reporting outputs.

What is the best way to validate CSV data during import?

Deduplication in CSV data schemas prevents redundant records by specifying cross-file relationships and validation rules. It maintains data integrity across modules like transactions and receipts, ensuring accurate analytics and reporting outputs.

How does deduplication work for CSV transaction data?

Deduplication in CSV data schemas prevents redundant records by specifying cross-file relationships and validation rules. It maintains data integrity across modules like transactions and receipts, ensuring accurate analytics and reporting outputs.

When do I need a standardized CSV schema for receipts and subscriptions?

Deduplication in CSV data schemas prevents redundant records by specifying cross-file relationships and validation rules. It maintains data integrity across modules like transactions and receipts, ensuring accurate analytics and reporting outputs.

Does this approach define file-naming and archiving rules for CSV data?

Deduplication in CSV data schemas prevents redundant records by specifying cross-file relationships and validation rules. It maintains data integrity across modules like transactions and receipts, ensuring accurate analytics and reporting outputs.