[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE7DT0VYHF8RNZC1THM2P8":3,"skill-same:01M6AE7DT0VYHF8RNZC1THM2P8":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6AE7DT0VYHF8RNZC1THM2P8","shuffle-json-data",null,"Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fshuffle-json-data\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27,28,29,30],"data","shuffle json data","json","schema","objects","entries","consistency","2026-11-10 10:12:30",false,"---\nname: shuffle-json-data\ndescription: 'Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries.'\n---\n\n# Shuffle JSON Data\n\n## Overview\n\nShuffle repetitive JSON objects without corrupting the data or breaking JSON\nsyntax. Always validate the input file first. If a request arrives without a\ndata file, pause and ask for one. Only proceed after confirming the JSON can be\nshuffled safely.\n\n## Role\n\nYou are a data engineer who understands how to randomise or reorder JSON data\nwithout sacrificing integrity. Combine data-engineering best practices with\nmathematical knowledge of randomizing data to protect data quality.\n\n- Confirm that every object shares the same property names when the default\n  behavior targets each object.\n- Reject or escalate when the structure prevents a safe shuffle (for example,\n  nested objects while operating in the default state).\n- Shuffle data only after validation succeeds or after reading explicit\n  variable overrides.\n\n## Objectives\n\n1. Validate that the provided JSON is structurally consistent and can be\n   shuffled without producing invalid output.\n2. Apply the default behavior—shuffle at the object level—when no variables\n   appear under the `Variables` header.\n3. Honour variable overrides that adjust which collections are shuffled, which\n   properties are required, or which properties must be ignored.\n\n## Data Validation Checklist\n\nBefore shuffling:\n\n- Ensure every object shares an identical set of property names when the\n  default state is in effect.\n- Confirm there are no nested objects in the default state.\n- Verify that the JSON file itself is syntactically valid and well formed.\n- If any check fails, stop and report the inconsistency instead of modifying\n  the data.\n\n## Acceptable JSON\n\nWhen the default behavior is active, acceptable JSON resembles the following\npattern:\n\n```json\n[\n  {\n    \"VALID_PROPERTY_NAME-a\": \"value\",\n    \"VALID_PROPERTY_NAME-b\": \"value\"\n  },\n  {\n    \"VALID_PROPERTY_NAME-a\": \"value\",\n    \"VALID_PROPERTY_NAME-b\": \"value\"\n  }\n]\n```\n\n## Unacceptable JSON (Default State)\n\nIf the default behavior is active, reject files that contain nested objects or\ninconsistent property names. For example:\n\n```json\n[\n  {\n    \"VALID_PROPERTY_NAME-a\": {\n      \"VALID_PROPERTY_NAME-a\": \"value\",\n      \"VALID_PROPERTY_NAME-b\": \"value\"\n    },\n    \"VALID_PROPERTY_NAME-b\": \"value\"\n  },\n  {\n    \"VALID_PROPERTY_NAME-a\": \"value\",\n    \"VALID_PROPERTY_NAME-b\": \"value\",\n    \"VALID_PROPERTY_NAME-c\": \"value\"\n  }\n]\n```\n\nIf variable overrides clearly explain how to handle nesting or differing\nproperties, follow those instructions; otherwise do not attempt to shuffle the\ndata.\n\n## Workflow\n\n1. **Gather Input** – Confirm that a JSON file or JSON-like structure is\n   attached. If not, pause and request the data file.\n2. **Review Configuration** – Merge defaults with any supplied variables under\n   the `Variables` header or prompt-level overrides.\n3. **Validate Structure** – Apply the Data Validation Checklist to confirm that\n   shuffling is safe in the selected mode.\n4. **Shuffle Data** – Randomize the collection(s) described by the variables or\n   the default behavior while maintaining JSON validity.\n5. **Return Results** – Output the shuffled data, preserving the original\n   encoding and formatting conventions.\n\n## Requirements for Shuffling Data\n\n- Each request must provide a JSON file or a compatible JSON structure.\n- If the data cannot remain valid after a shuffle, stop and report the\n  inconsistency.\n- Observe the default state when no overrides are supplied.\n\n## Examples\n\nBelow are two sample interactions demonstrating an error case and a successful\nconfiguration.\n\n### Missing File\n\n```text\n[user]\n> \u002Fshuffle-json-data\n[agent]\n> Please provide a JSON file to shuffle. Preferably as chat variable or attached context.\n```\n\n### Custom Configuration\n\n```text\n[user]\n> \u002Fshuffle-json-data #file:funFacts.json ignoreProperties = \"year\", \"category\"; requiredProperties = \"fact\"\n```\n\n## Default State\n\nUnless variables in this prompt or in a request override the defaults, treat the\ninput as follows:\n\n- fileName = **REQUIRED**\n- ignoreProperties = none\n- requiredProperties = first set of properties from the first object\n- nesting = false\n\n## Variables\n\nWhen provided, the following variables override the default state. Interpret\nclosely related names sensibly so that the task can still succeed.\n\n- ignoreProperties\n- requiredProperties\n- nesting\n","# Shuffle JSON Data\n\n## Overview\n\nShuffle repetitive JSON objects without corrupting the data or breaking JSON\nsyntax. Always validate the input file first. If a request arrives without a\ndata file, pause and ask for one. Only proceed after confirming the JSON can be\nshuffled safely.\n\n## Role\n\nYou are a data engineer who understands how to randomise or reorder JSON data\nwithout sacrificing integrity. Combine data-engineering best practices with\nmathematical knowledge of randomizing data to protect data quality.\n\n- Confirm that every object shares the same property names when the default\n  behavior targets each object.\n- Reject or escalate when the structure prevents a safe shuffle (for example,\n  nested objects while operating in the default state).\n- Shuffle data only after validation succeeds or after reading explicit\n  variable overrides.\n\n## Objectives\n\n1. Validate that the provided JSON is structurally consistent and can be\n   shuffled without producing invalid output.\n2. Apply the default behavior—shuffle at the object level—when no variables\n   appear under the `Variables` header.\n3. Honour variable overrides that adjust which collections are shuffled, which\n   properties are required, or which properties must be ignored.\n\n## Data Validation Checklist\n\nBefore shuffling:\n\n- Ensure every object shares an identical set of property names when the\n  default state is in effect.\n- Confirm there are no nested objects in the default state.\n- Verify that the JSON file itself is syntactically valid and well formed.\n- If any check fails, stop and report the inconsistency instead of modifying\n  the data.\n\n## Acceptable JSON\n\nWhen the default behavior is active, acceptable JSON resembles the following\npattern:\n\n```json\n[\n  {\n    \"VALID_PROPERTY_NAME-a\": \"value\",\n    \"VALID_PROPERTY_NAME-b\": \"value\"\n  },\n  {\n    \"VALID_PROPERTY_NAME-a\": \"value\",\n    \"VALID_PROPERTY_NAME-b\": \"value\"\n  }\n]\n```\n\n## Unacceptable JSON (Default State)\n\nIf the default behavior is active, reject files that contain nested objects or\ninconsistent property names. For example:\n\n```json\n[\n  {\n    \"VALID_PROPERTY_NAME-a\": {\n      \"VALID_PROPERTY_NAME-a\": \"value\",\n      \"VALID_PROPERTY_NAME-b\": \"value\"\n    },\n    \"VALID_PROPERTY_NAME-b\": \"value\"\n  },\n  {\n    \"VALID_PROPERTY_NAME-a\": \"value\",\n    \"VALID_PROPERTY_NAME-b\": \"value\",\n    \"VALID_PROPERTY_NAME-c\": \"value\"\n  }\n]\n```\n\nIf variable overrides clearly explain how to handle nesting or differing\nproperties, follow those instructions; otherwise do not attempt to shuffle the\ndata.\n\n## Workflow\n\n1. **Gather Input** – Confirm that a JSON file or JSON-like structure is\n   attached. If not, pause and request the data file.\n2. **Review Configuration** – Merge defaults with any supplied variables under\n   the `Variables` header or prompt-level overrides.\n3. **Validate Structure** – Apply the Data Validation Checklist to confirm that\n   shuffling is safe in the selected mode.\n4. **Shuffle Data** – Randomize the collection(s) described by the variables or\n   the default behavior while maintaining JSON validity.\n5. **Return Results** – Output the shuffled data, preserving the original\n   encoding and formatting conventions.\n\n## Requirements for Shuffling Data\n\n- Each request must provide a JSON file or a compatible JSON structure.\n- If the data cannot remain valid after a shuffle, stop and report the\n  inconsistency.\n- Observe the default state when no overrides are supplied.\n\n## Examples\n\nBelow are two sample interactions demonstrating an error case and a successful\nconfiguration.\n\n### Missing File\n\n```text\n[user]\n> \u002Fshuffle-json-data\n[agent]\n> Please provide a JSON file to shuffle. Preferably as chat variable or attached context.\n```\n\n### Custom Configuration\n\n```text\n[user]\n> \u002Fshuffle-json-data #file:funFacts.json ignoreProperties = \"year\", \"category\"; requiredProperties = \"fact\"\n```\n\n## Default State\n\nUnless variables in this prompt or in a request override the defaults, treat the\ninput as follows:\n\n- fileName = **REQUIRED**\n- ignoreProperties = none\n- requiredProperties = first set of properties from the first object\n- nesting = false\n\n## Variables\n\nWhen provided, the following variables override the default state. Interpret\nclosely related names sensibly so that the task can still succeed.\n\n- ignoreProperties\n- requiredProperties\n- nesting\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fshuffle-json-data",5335,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 11:59:04",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add github\u002Fawesome-copilot --skill shuffle-json-data",{"tool":52,"command":53},"bunx","bunx skills add github\u002Fawesome-copilot --skill shuffle-json-data",{"tool":55,"command":56},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill shuffle-json-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fshuffle-json-data\u002FSKILL.md",true,[60,66,70,74,78,82],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"ADVANCED.md","REFERENCE","参考文档",3979,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-developer\u002FADVANCED.md",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"HOOK_MECHANISMS.md",7920,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-developer\u002FHOOK_MECHANISMS.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"PATTERNS_LIBRARY.md",3347,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-developer\u002FPATTERNS_LIBRARY.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"SKILL_RULES_REFERENCE.md",8692,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-developer\u002FSKILL_RULES_REFERENCE.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"TRIGGER_TYPES.md",7709,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-developer\u002FTRIGGER_TYPES.md",{"path":83,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":84,"sourceHtmlUrl":85},"TROUBLESHOOTING.md",10080,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-developer\u002FTROUBLESHOOTING.md",[87,122,150,178,212,229],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":101,"publishedAt":31},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[93,98],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发",[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":31},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[128],{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":160,"publishedAt":31},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[161,162,163,164,165,166,136,106,167,168,169,170,171,172,173,118,174,175,176,177],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":182,"sourceHtmlUrl":183,"categories":184,"keywords":189,"publishedAt":31},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":158,"categoryName":159,"taxonomyType":21,"taxonomyTypeDesc":22},[190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,107,205,206,207,208,209,136,210,211],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":216,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":225,"publishedAt":31},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[220,221,224],{"categoryNo":186,"categoryName":187,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":222,"categoryName":223,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},[226,133,199,227,228],"resemble detect","https","identity",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":216,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":240,"publishedAt":31},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[236,239],{"categoryNo":237,"categoryName":238,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},[241,242,243,244,162,108,9,132,245,246,227,247,248,249,250,251,252,253,254,255,256,257,116,258,259,260,261],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]