[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79PB510DTTD3TPR71HCXKJF":3,"skill-same:01M79PB510DTTD3TPR71HCXKJF":51},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79PB510DTTD3TPR71HCXKJF","level-design",null,"Design and build playable levels — the blockout\u002Fwhitebox-to-playable workflow, player metrics and grid layout, pacing and flow (tension\u002Frest curve), gating and the critical path, and encounter design. Engine-neutral practice. Use when the user mentions level design, blockout\u002Fwhitebox\u002Fgreybox, level layout, level pacing, encounter design, or the critical path through a level.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Flevel-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: level-design\ndescription: >\n  Design and build playable levels — the blockout\u002Fwhitebox-to-playable workflow,\n  player metrics and grid layout, pacing and flow (tension\u002Frest curve), gating\n  and the critical path, and encounter design. Engine-neutral practice. Use when\n  the user mentions level design, blockout\u002Fwhitebox\u002Fgreybox, level layout, level\n  pacing, encounter design, or the critical path through a level.\n---\n\n# Level design\n\nA level is a **sequence of intentional experiences** delivered through space.\nGood level design is a *process*: define the metrics movement is built on, block\nout geometry with primitives, play it, then dress it — never the reverse. This\nskill is the engine-neutral practice; use `godot-tilemap`\u002F`unity-tilemap-2d` to\nlay out 2D grids and gridmaps for 3D.\n\n## When to use\n\n- Use to plan a level's structure: critical path, pacing, gating, encounters,\n  and where the player learns vs is tested.\n- Use the **blockout → test → iterate → dress** workflow to build a level that\n  plays well before any art exists.\n- Use to derive level **metrics** from the character's movement so geometry is\n  reachable and fair.\n\n**When *not* to use:** to *generate* levels algorithmically, use `procedural-gen`\n(authored and procedural design are complementary). For the engine's tile\u002Fgrid\npainting tools, use `godot-tilemap` \u002F `unity-tilemap-2d`. For the movement\nabilities the metrics come from, that's the engine movement skill + `input-systems`.\n\n## Core workflow\n\n1. **Derive metrics first.** Measure the character: max jump height and distance,\n   run speed, reach, camera range. Every gap, ledge, and corridor is sized in\n   these units. Lock them before building geometry.\n2. **Blockout (whitebox\u002Fgreybox).** Build the whole level from untextured\n   primitives at correct scale. Validate flow, sightlines, and reachability while\n   changes are cheap. No art yet. Tools: Godot `CSGBox3D` and friends with\n   `use_collision` on (prototype only: the docs flag their CPU cost, so bake to\n   static meshes later), Unity's ProBuilder package (`com.unity.probuilder`),\n   Unreal's Modeling Mode (Cube Grid), and a plain grey tileset for 2D.\n3. **Define the critical path** (start → goal) and the **golden path** you expect\n   most players to take. Layer optional\u002Fsecret paths off it.\n4. **Pace the experience.** Alternate tension and rest in a deliberate curve;\n   don't run combat-combat-combat. Give the player room to breathe and to\n   anticipate.\n5. **Teach, then test.** Introduce each mechanic in a safe space, let the player\n   practice, then test it under pressure. Difficulty rises in a sawtooth, not a\n   straight line.\n6. **Gate with intent.** Use locks\u002Fkeys, abilities, and one-way drops to control\n   order and pacing; guide with light, lines, and landmarks rather than walls.\n7. **Playtest and iterate.** Watch real players: where do they get lost, stuck,\n   bored, or killed unfairly? Fix the blockout; only dress when it plays well.\n\n## Patterns\n\n### 1. Player metrics drive every dimension\n\n```gdscript\n# Derive the metrics from the SAME constants the character controller uses, then\n# size geometry in these units. If the jump changes, the numbers follow.\nconst RUN_SPEED      := 240.0   # px\u002Fs (or m\u002Fs in 3D)\nconst JUMP_VELOCITY  := 420.0   # initial upward speed of a full jump\nconst GRAVITY        := 980.0   # px\u002Fs², the value the controller applies\nconst MAX_JUMP_H     := JUMP_VELOCITY * JUMP_VELOCITY \u002F (2.0 * GRAVITY)  # 90: peak height\nconst AIR_TIME       := 2.0 * JUMP_VELOCITY \u002F GRAVITY   # ~0.86 s, take-off to same height\nconst MAX_JUMP_DIST  := RUN_SPEED * AIR_TIME            # ~206: running jump, level ground\nconst SAFE_GAP       := MAX_JUMP_DIST * 0.7   # comfortable, not pixel-perfect\nconst HARD_GAP       := MAX_JUMP_DIST * 0.95  # a deliberate skill check\n# Build platforms so required jumps use SAFE_GAP; reserve HARD_GAP for optional reward.\n```\n\nThe formulas are the ideal arc. Variable jump height, a separate fall gravity,\nair acceleration, the fixed physics step and the collider's width all move the\nreal numbers, and landing higher shortens the reach. Confirm them once in a\ntest room with a measured gap ladder, then treat the measured values as the\ntruth. A platform placed `MAX_JUMP_DIST + 1` away is impossible; one at\n`SAFE_GAP` is fair. Keep these constants beside the level data so designers and\ncode agree.\n\n### 2. Encounter \u002F pacing as data (a tension timeline)\n\n```gdscript\n# Author the level as a sequence of beats with an intended intensity (0..1).\n# This makes the pacing curve explicit and reviewable before you build rooms.\nconst BEATS := [\n    { \"room\": \"entry\",      \"type\": \"teach\",   \"intensity\": 0.1 },\n    { \"room\": \"hall_1\",     \"type\": \"combat\",  \"intensity\": 0.5 },\n    { \"room\": \"vista\",      \"type\": \"rest\",    \"intensity\": 0.1 },  # breather + reward\n    { \"room\": \"gauntlet\",   \"type\": \"combat\",  \"intensity\": 0.8 },\n    { \"room\": \"save_room\",  \"type\": \"rest\",    \"intensity\": 0.2 },  # before the boss\n    { \"room\": \"boss\",       \"type\": \"climax\",  \"intensity\": 1.0 },\n]\n# Read the intensity column top-to-bottom: it should rise overall but dip for rests\n# (a sawtooth), never flatline high. Drive spawns\u002Fmusic intensity from this.\n```\n\n### 3. Gating and the critical path (a small graph)\n\n```gdscript\n# Model the level as rooms + gated connections. Validate that the goal is\n# reachable with the keys\u002Fabilities the player can actually obtain in order.\nconst ROOMS := {\n    \"entry\":   { \"exits\": [ { \"to\": \"hall_1\" } ] },\n    \"hall_1\":  { \"exits\": [ { \"to\": \"vista\", \"needs\": \"double_jump\" },\n                            { \"to\": \"side_room\" } ] },           # optional branch\n    \"side_room\": { \"exits\": [ { \"to\": \"hall_1\" } ], \"grants\": \"double_jump\" },\n    \"vista\":   { \"exits\": [ { \"to\": \"boss\", \"needs\": \"red_key\" } ] },\n}\n\n# Grow the reachable set until nothing new opens: collect what each reached room\n# grants, then follow every exit whose `needs` is already held. Assumes keys are\n# never used up and doors never re-lock; model consumable keys as counts.\nfunc goal_reachable(rooms: Dictionary, start: String, goal: String) -> bool:\n    var have := {}                                 # keys\u002Fabilities collected\n    var reached := {start: true}\n    var changed := true\n    while changed:\n        changed = false\n        for room in reached.keys():\n            var info: Dictionary = rooms.get(room, {})\n            var grant = info.get(\"grants\")\n            if grant != null and not have.has(grant):\n                have[grant] = true\n                changed = true\n            for exit in info.get(\"exits\", []):\n                var open: bool = not exit.has(\"needs\") or have.has(exit[\"needs\"])\n                if open and not reached.has(exit[\"to\"]):\n                    reached[exit[\"to\"]] = true\n                    changed = true\n    return reached.has(goal)\n# goal_reachable(ROOMS, \"entry\", \"boss\") is FALSE for the table above: no room\n# grants \"red_key\". That is exactly the soft-lock this check exists to catch.\n# Run it in a test or editor tool whenever the room graph changes.\n```\n\n## Pitfalls\n\n- **Dressing before it plays.** Detailing a blockout you haven't validated wastes\n  the most expensive work on a layout you'll change. Greybox and test first.\n- **Geometry that ignores metrics**: gaps the jump can't clear, ledges below\n  reach, corridors narrower than the camera needs. Size everything in player units.\n- **Flat pacing.** Wall-to-wall combat (or wall-to-wall calm) numbs the player.\n  Alternate tension and rest; place a breather and a save before the climax.\n- **Testing a mechanic before teaching it.** Players meet a hazard for the first\n  time in a lethal spot. Introduce safely, let them practice, then test.\n- **Soft-locks and dead ends.** A gate needs an ability\u002Fkey obtainable only past\n  the gate. Validate the critical path's key\u002Fability order, not just connectivity.\n- **No readability \u002F guidance.** Players get lost when nothing draws the eye. Use\n  light, leading lines, color, and landmarks to point toward the path.\n- **One-way drops with no signposting** strand or surprise players. Telegraph\n  irreversible moves.\n- **Confusing procedural with authored.** Generation gives variety, not\n  authored pacing. Use `procedural-gen` for variety; hand-author for intent.\n\n## References\n\n- `references\u002Fpacing-and-flow.md` — the difficulty\u002Ftension curve in depth,\n  teaching-loop design (introduce→develop→twist→test), readability and guidance\n  techniques, 2D vs 3D layout considerations, and a blockout review checklist.\n\n## Related skills\n\n- `godot-tilemap`, `unity-tilemap-2d` — paint 2D level grids; gridmaps for 3D.\n- `procedural-gen` — generate variety to complement authored structure.\n- `game-ai` — encounter enemies that navigate the space you build.\n- `platformer`, `puzzle`, `roguelike` — genres that compose this skill.\n","# Level design\n\nA level is a **sequence of intentional experiences** delivered through space.\nGood level design is a *process*: define the metrics movement is built on, block\nout geometry with primitives, play it, then dress it — never the reverse. This\nskill is the engine-neutral practice; use `godot-tilemap`\u002F`unity-tilemap-2d` to\nlay out 2D grids and gridmaps for 3D.\n\n## When to use\n\n- Use to plan a level's structure: critical path, pacing, gating, encounters,\n  and where the player learns vs is tested.\n- Use the **blockout → test → iterate → dress** workflow to build a level that\n  plays well before any art exists.\n- Use to derive level **metrics** from the character's movement so geometry is\n  reachable and fair.\n\n**When *not* to use:** to *generate* levels algorithmically, use `procedural-gen`\n(authored and procedural design are complementary). For the engine's tile\u002Fgrid\npainting tools, use `godot-tilemap` \u002F `unity-tilemap-2d`. For the movement\nabilities the metrics come from, that's the engine movement skill + `input-systems`.\n\n## Core workflow\n\n1. **Derive metrics first.** Measure the character: max jump height and distance,\n   run speed, reach, camera range. Every gap, ledge, and corridor is sized in\n   these units. Lock them before building geometry.\n2. **Blockout (whitebox\u002Fgreybox).** Build the whole level from untextured\n   primitives at correct scale. Validate flow, sightlines, and reachability while\n   changes are cheap. No art yet. Tools: Godot `CSGBox3D` and friends with\n   `use_collision` on (prototype only: the docs flag their CPU cost, so bake to\n   static meshes later), Unity's ProBuilder package (`com.unity.probuilder`),\n   Unreal's Modeling Mode (Cube Grid), and a plain grey tileset for 2D.\n3. **Define the critical path** (start → goal) and the **golden path** you expect\n   most players to take. Layer optional\u002Fsecret paths off it.\n4. **Pace the experience.** Alternate tension and rest in a deliberate curve;\n   don't run combat-combat-combat. Give the player room to breathe and to\n   anticipate.\n5. **Teach, then test.** Introduce each mechanic in a safe space, let the player\n   practice, then test it under pressure. Difficulty rises in a sawtooth, not a\n   straight line.\n6. **Gate with intent.** Use locks\u002Fkeys, abilities, and one-way drops to control\n   order and pacing; guide with light, lines, and landmarks rather than walls.\n7. **Playtest and iterate.** Watch real players: where do they get lost, stuck,\n   bored, or killed unfairly? Fix the blockout; only dress when it plays well.\n\n## Patterns\n\n### 1. Player metrics drive every dimension\n\n```gdscript\n# Derive the metrics from the SAME constants the character controller uses, then\n# size geometry in these units. If the jump changes, the numbers follow.\nconst RUN_SPEED      := 240.0   # px\u002Fs (or m\u002Fs in 3D)\nconst JUMP_VELOCITY  := 420.0   # initial upward speed of a full jump\nconst GRAVITY        := 980.0   # px\u002Fs², the value the controller applies\nconst MAX_JUMP_H     := JUMP_VELOCITY * JUMP_VELOCITY \u002F (2.0 * GRAVITY)  # 90: peak height\nconst AIR_TIME       := 2.0 * JUMP_VELOCITY \u002F GRAVITY   # ~0.86 s, take-off to same height\nconst MAX_JUMP_DIST  := RUN_SPEED * AIR_TIME            # ~206: running jump, level ground\nconst SAFE_GAP       := MAX_JUMP_DIST * 0.7   # comfortable, not pixel-perfect\nconst HARD_GAP       := MAX_JUMP_DIST * 0.95  # a deliberate skill check\n# Build platforms so required jumps use SAFE_GAP; reserve HARD_GAP for optional reward.\n```\n\nThe formulas are the ideal arc. Variable jump height, a separate fall gravity,\nair acceleration, the fixed physics step and the collider's width all move the\nreal numbers, and landing higher shortens the reach. Confirm them once in a\ntest room with a measured gap ladder, then treat the measured values as the\ntruth. A platform placed `MAX_JUMP_DIST + 1` away is impossible; one at\n`SAFE_GAP` is fair. Keep these constants beside the level data so designers and\ncode agree.\n\n### 2. Encounter \u002F pacing as data (a tension timeline)\n\n```gdscript\n# Author the level as a sequence of beats with an intended intensity (0..1).\n# This makes the pacing curve explicit and reviewable before you build rooms.\nconst BEATS := [\n    { \"room\": \"entry\",      \"type\": \"teach\",   \"intensity\": 0.1 },\n    { \"room\": \"hall_1\",     \"type\": \"combat\",  \"intensity\": 0.5 },\n    { \"room\": \"vista\",      \"type\": \"rest\",    \"intensity\": 0.1 },  # breather + reward\n    { \"room\": \"gauntlet\",   \"type\": \"combat\",  \"intensity\": 0.8 },\n    { \"room\": \"save_room\",  \"type\": \"rest\",    \"intensity\": 0.2 },  # before the boss\n    { \"room\": \"boss\",       \"type\": \"climax\",  \"intensity\": 1.0 },\n]\n# Read the intensity column top-to-bottom: it should rise overall but dip for rests\n# (a sawtooth), never flatline high. Drive spawns\u002Fmusic intensity from this.\n```\n\n### 3. Gating and the critical path (a small graph)\n\n```gdscript\n# Model the level as rooms + gated connections. Validate that the goal is\n# reachable with the keys\u002Fabilities the player can actually obtain in order.\nconst ROOMS := {\n    \"entry\":   { \"exits\": [ { \"to\": \"hall_1\" } ] },\n    \"hall_1\":  { \"exits\": [ { \"to\": \"vista\", \"needs\": \"double_jump\" },\n                            { \"to\": \"side_room\" } ] },           # optional branch\n    \"side_room\": { \"exits\": [ { \"to\": \"hall_1\" } ], \"grants\": \"double_jump\" },\n    \"vista\":   { \"exits\": [ { \"to\": \"boss\", \"needs\": \"red_key\" } ] },\n}\n\n# Grow the reachable set until nothing new opens: collect what each reached room\n# grants, then follow every exit whose `needs` is already held. Assumes keys are\n# never used up and doors never re-lock; model consumable keys as counts.\nfunc goal_reachable(rooms: Dictionary, start: String, goal: String) -> bool:\n    var have := {}                                 # keys\u002Fabilities collected\n    var reached := {start: true}\n    var changed := true\n    while changed:\n        changed = false\n        for room in reached.keys():\n            var info: Dictionary = rooms.get(room, {})\n            var grant = info.get(\"grants\")\n            if grant != null and not have.has(grant):\n                have[grant] = true\n                changed = true\n            for exit in info.get(\"exits\", []):\n                var open: bool = not exit.has(\"needs\") or have.has(exit[\"needs\"])\n                if open and not reached.has(exit[\"to\"]):\n                    reached[exit[\"to\"]] = true\n                    changed = true\n    return reached.has(goal)\n# goal_reachable(ROOMS, \"entry\", \"boss\") is FALSE for the table above: no room\n# grants \"red_key\". That is exactly the soft-lock this check exists to catch.\n# Run it in a test or editor tool whenever the room graph changes.\n```\n\n## Pitfalls\n\n- **Dressing before it plays.** Detailing a blockout you haven't validated wastes\n  the most expensive work on a layout you'll change. Greybox and test first.\n- **Geometry that ignores metrics**: gaps the jump can't clear, ledges below\n  reach, corridors narrower than the camera needs. Size everything in player units.\n- **Flat pacing.** Wall-to-wall combat (or wall-to-wall calm) numbs the player.\n  Alternate tension and rest; place a breather and a save before the climax.\n- **Testing a mechanic before teaching it.** Players meet a hazard for the first\n  time in a lethal spot. Introduce safely, let them practice, then test.\n- **Soft-locks and dead ends.** A gate needs an ability\u002Fkey obtainable only past\n  the gate. Validate the critical path's key\u002Fability order, not just connectivity.\n- **No readability \u002F guidance.** Players get lost when nothing draws the eye. Use\n  light, leading lines, color, and landmarks to point toward the path.\n- **One-way drops with no signposting** strand or surprise players. Telegraph\n  irreversible moves.\n- **Confusing procedural with authored.** Generation gives variety, not\n  authored pacing. Use `procedural-gen` for variety; hand-author for intent.\n\n## References\n\n- `references\u002Fpacing-and-flow.md` — the difficulty\u002Ftension curve in depth,\n  teaching-loop design (introduce→develop→twist→test), readability and guidance\n  techniques, 2D vs 3D layout considerations, and a blockout review checklist.\n\n## Related skills\n\n- `godot-tilemap`, `unity-tilemap-2d` — paint 2D level grids; gridmaps for 3D.\n- `procedural-gen` — generate variety to complement authored structure.\n- `game-ai` — encounter enemies that navigate the space you build.\n- `platformer`, `puzzle`, `roguelike` — genres that compose this skill.\n",{"name":5,"description":7},"main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Flevel-design","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill level-design",{"tool":37,"command":38},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill level-design",{"tool":40,"command":41},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill level-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Flevel-design\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fpacing-and-flow.md","REFERENCE","参考文档",4500,"https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Flevel-design\u002Freferences\u002Fpacing-and-flow.md",[52,58,64,70,76,82],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]