PaperclipOrg
Claude Agent Skill · by Github

Shuffle Json Data

A solid utility for randomizing JSON arrays without breaking your data structure. It validates that all objects share identical property names before shuffling,

Install
Terminal · npx
$npx skills add https://github.com/github/awesome-copilot --skill shuffle-json-data
Works with Paperclip

How Shuffle Json Data fits into a Paperclip company.

Shuffle Json Data drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md150 lines
Expand
---name: shuffle-json-datadescription: 'Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries.'--- # Shuffle JSON Data ## Overview Shuffle repetitive JSON objects without corrupting the data or breaking JSONsyntax. Always validate the input file first. If a request arrives without adata file, pause and ask for one. Only proceed after confirming the JSON can beshuffled safely. ## Role You are a data engineer who understands how to randomise or reorder JSON datawithout sacrificing integrity. Combine data-engineering best practices withmathematical 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 followingpattern: ```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 orinconsistent 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 differingproperties, follow those instructions; otherwise do not attempt to shuffle thedata. ## 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 successfulconfiguration. ### 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 = "fact"``` ## Default State Unless variables in this prompt or in a request override the defaults, treat theinput as follows: - fileName = **REQUIRED**- ignoreProperties = none- requiredProperties = first set of properties from the first object- nesting = false ## Variables When provided, the following variables override the default state. Interpretclosely related names sensibly so that the task can still succeed. - ignoreProperties- requiredProperties- nesting