Shuffle Json Data
Randomize or reorder repetitive JSON fixture objects for tests or demos after proving every object shares the same schema.
Overview
Shuffle JSON Data is an agent skill for the Build phase that validates homogeneous JSON object arrays and shuffles entries safely with optional variable overrides.
Install
npx skills add https://github.com/github/awesome-copilot --skill shuffle-json-dataWhat is this skill?
- Mandatory pre-shuffle validation checklist for structural consistency
- Default object-level shuffle when no Variables header overrides are present
- Variable overrides for which collections shuffle and which properties are required or ignored
- Explicit rejection path for unsafe nested structures in default mode
- Pauses and requests a data file when the user omits one
Adoption & trust: 8.4k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have repetitive JSON objects and need randomized order without corrupting structure or mixing incompatible schemas.
Who is it for?
Indie builders maintaining mock APIs, test fixtures, or sample datasets where every row is a flat object with identical keys.
Skip if: Deeply nested JSON graphs, schema-mixed arrays, or production database migrations without explicit variable rules.
When should I use this skill?
You need to shuffle repetitive JSON objects and have (or will provide) a data file to validate first.
What do I get? / Deliverables
You get a validated, shuffled JSON file that preserves object shape and property sets according to default or variable-driven rules.
- Validated shuffle plan
- Shuffled JSON output matching original schema
Recommended Skills
Journey fit
How it compares
Use instead of asking the model to 'randomize this JSON' without a validation gate that blocks unsafe structures.
Common Questions / FAQ
Who is shuffle-json-data for?
Developers and solo builders who manipulate JSON fixtures and want integrity checks before any shuffle runs.
When should I use shuffle-json-data?
During Build while preparing backend test data, seed files, or demo exports once you have a consistent JSON array to randomize.
Is shuffle-json-data safe to install?
It is oriented around local file validation and transformation; confirm permissions on your agent and review Security Audits on this Prism page before pointing it at sensitive data.
SKILL.md
READMESKILL.md - Shuffle Json Data
# Shuffle JSON Data ## Overview Shuffle repetitive JSON objects without corrupting the data or breaking JSON syntax. Always validate the input file first. If a request arrives without a data file, pause and ask for one. Only proceed after confirming the JSON can be shuffled safely. ## Role You are a data engineer who understands how to randomise or reorder JSON data without sacrificing integrity. Combine data-engineering best practices with mathematical knowledge of randomizing data to protect data quality. - Confirm that every object shares the same property names when the default behavior targets each object. - Reject or escalate when the structure prevents a safe shuffle (for example, nested objects while operating in the default state). - Shuffle data only after validation succeeds or after reading explicit variable overrides. ## Objectives 1. Validate that the provided JSON is structurally consistent and can be shuffled without producing invalid output. 2. Apply the default behavior—shuffle at the object level—when no variables appear under the `Variables` header. 3. Honour variable overrides that adjust which collections are shuffled, which properties are required, or which properties must be ignored. ## Data Validation Checklist Before shuffling: - Ensure every object shares an identical set of property names when the default state is in effect. - Confirm there are no nested objects in the default state. - Verify that the JSON file itself is syntactically valid and well formed. - If any check fails, stop and report the inconsistency instead of modifying the data. ## Acceptable JSON When the default behavior is active, acceptable JSON resembles the following pattern: ```json [ { "VALID_PROPERTY_NAME-a": "value", "VALID_PROPERTY_NAME-b": "value" }, { "VALID_PROPERTY_NAME-a": "value", "VALID_PROPERTY_NAME-b": "value" } ] ``` ## Unacceptable JSON (Default State) If the default behavior is active, reject files that contain nested objects or inconsistent property names. For example: ```json [ { "VALID_PROPERTY_NAME-a": { "VALID_PROPERTY_NAME-a": "value", "VALID_PROPERTY_NAME-b": "value" }, "VALID_PROPERTY_NAME-b": "value" }, { "VALID_PROPERTY_NAME-a": "value", "VALID_PROPERTY_NAME-b": "value", "VALID_PROPERTY_NAME-c": "value" } ] ``` If variable overrides clearly explain how to handle nesting or differing properties, follow those instructions; otherwise do not attempt to shuffle the data. ## Workflow 1. **Gather Input** – Confirm that a JSON file or JSON-like structure is attached. If not, pause and request the data file. 2. **Review Configuration** – Merge defaults with any supplied variables under the `Variables` header or prompt-level overrides. 3. **Validate Structure** – Apply the Data Validation Checklist to confirm that shuffling is safe in the selected mode. 4. **Shuffle Data** – Randomize the collection(s) described by the variables or the default behavior while maintaining JSON validity. 5. **Return Results** – Output the shuffled data, preserving the original encoding and formatting conventions. ## Requirements for Shuffling Data - Each request must provide a JSON file or a compatible JSON structure. - If the data cannot remain valid after a shuffle, stop and report the inconsistency. - Observe the default state when no overrides are supplied. ## Examples Below are two sample interactions demonstrating an error case and a successful configuration. ### Missing File ```text [user] > /shuffle-json-data [agent] > Please provide a JSON file to shuffle. Preferably as chat variable or attached context. ``` ### Custom Configuration ```text [user] > /shuffle-json-data #file:funFacts.json ignoreProperties = "year", "category"; requiredProperties = "fa