Skip to content
Skills Library
Programming · Testing

test-data

/test-data

Use when a new function or a new table needs tests, to write test data with the edge cases and the expected result written first, never from production data.

Licence
MIT
Last repository change
06.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a new function or a new table needs tests, to write test data with the edge cases and the expected result written first, never from production data.

Arguments

/test-data [function or table]
Original author description

Use when a new function or a new table needs tests, to write test data with the edge cases and the expected result written first, never from production data.

How it works

  1. Steps
  2. Output
  3. Reads
  4. Writes
  5. Never
Original SKILL.md headings · 34 lines, 198 words
SKILL.md preview
---
name: test-data
description: Use when a new function or a new table needs tests, to write test data with the edge cases and the expected result written first, never from production data.
argument-hint: "[function or table]"
---

# Test data

The job: small test files with the edge cases, and the expected result decided first.

Input: the function or the table under test.

## Steps

1. Name the function or the table under test, and what it must do with each edge case.
2. Synthetic rows from the metadata, in the source's own format. Never real data.
3. The expected result first: what the output must hold, written before the code.
4. Injected faults, each with its expected result: a broken line, a new column, broken bytes, a child row before its parent.
5. A second delivery with drift: a renamed column that the schema check must stop.
6. The fixtures beside the tests, never in the data folders.
7. Run the tests and report which passed.

## Output

The test files beside the tests: the input rows, the injected faults, the expected result written first, and the test that compares them.

## Reads

- the metadata of the table, the file parsers of the source's format

## Writes

- the fixtures of the test, and the test

## Never

- Never reads production data for a test.
- Never writes under the data folders.

Versions

RepositoryScoreLicence
This page · DataWithBaraa/claude-code-data-engineering-skills90MIT
MohamedRamadanSalah/claude-qa-toolkit100MIT
katalon-labs/true-skills100MIT
motlin/claude-code-plugins95Apache-2.0

Database snapshot: 13.11.2026 · package version 317c39d60f76 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100generating-test-data
    Generate realistic test data including edge cases and boundary conditions. Use when creating realistic fixtures or edge case test data. Trigger with phrases like "generate test data", "create fixtures", or "setup test database".
  • 100generating-test-data
    Generate realistic test data including edge cases and boundary conditions. Use when creating realistic fixtures or edge case test data. Trigger with phrases like "generate test data", "create fixtures", or "setup test database".
  • 90test-writer
    Write test code. 100% coverage, SSR tests, edge cases. Use when writing tests, adding test coverage.
  • 95memstack-development-test-writer
    Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
  • 100go-table-driven-tests
    Write Go table-driven tests following established patterns. Use when writing tests, creating test functions, adding test cases, or when the user mentions "test", "table-driven", "Go tests", or testing in Go codebases.
  • 95go-table-driven-tests
    Write Go table-driven tests following established patterns. Use when writing tests, creating test functions, adding test cases, or when the user mentions "test", "table-driven", "Go tests", or testing in Go codebases.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.