[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADQTR9HGKR1J5TPNPSZDMF":3,"skill-same:01M6ADQTR9HGKR1J5TPNPSZDMF":108},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6ADQTR9HGKR1J5TPNPSZDMF","java-diagnostics",null,"Symptom-first runtime diagnostics for JVM applications using JDK tools: jcmd, jstack, jmap, jstat, JFR, GC logs, async-profiler, Native Memory Tracking, and Eclipse MAT. Use when a Java app has high CPU, memory leaks or OutOfMemoryError, slow startup, deadlocks or thread starvation, long GC pauses, native memory growth, or slow requests. Includes permission tiers for safe use.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41133,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"diagnostics","java","java diagnostics","gc","when","thread","for","high","requests","long","app","runtime","jvm","async","safe","use","growth","first","applications","startup","logs","memory","2026-11-10 10:12:30",false,"---\nname: java-diagnostics\ndescription: 'Symptom-first runtime diagnostics for JVM applications using JDK tools: jcmd, jstack, jmap, jstat, JFR, GC logs, async-profiler, Native Memory Tracking, and Eclipse MAT. Use when a Java app has high CPU, memory leaks or OutOfMemoryError, slow startup, deadlocks or thread starvation, long GC pauses, native memory growth, or slow requests. Includes permission tiers for safe use.'\n---\n\n# Java Diagnostics\n\nPick the lightest tool that answers the question, starting from the symptom.\n\n## Permission tiers (obey them)\n\n| Tier | Tools | Rule |\n|------|-------|------|\n| 1. Read-only | `jps -l`, `jcmd \u003Cpid> help\u002FVM.version\u002FVM.flags\u002FThread.print`, `jstat`, `jstack`, reading logs | May run after stating the exact command. Class histograms (`jcmd \u003Cpid> GC.class_histogram`, `jmap -histo`, `jmap -histo:live`) are NOT Tier 1: they run heap inspection at a safepoint and can pause application threads on a large heap, so treat them as Tier 2 (consent, stated overhead). The default forms and `-histo:live` additionally force a full GC; `-all=true` \u002F `jmap -histo` skip the full GC but still pause during the scan (and count unreachable objects). |\n| 2. Recording \u002F attach | JFR (`JFR.start`, `-XX:StartFlightRecording`), async-profiler, NMT (`-XX:NativeMemoryTracking`), enabling GC logs | Requires user consent. State duration and expected overhead (JFR default profile is about 1-2%; async-profiler depends on mode; NMT summary roughly 5-10%, detail more) before running. |\n| 3. Intrusive \u002F sensitive | Heap dumps (`GC.heap_dump`, `jmap -dump`), `jhsdb`, commands that print JVM arguments or system properties (`jps -v\u002F-lv\u002F-m`, bare `jcmd`, `VM.system_properties`, `VM.command_line`, `jinfo`, `ps aux` on a Java process; they can expose secrets, redact output), JDWP with suspend, anything on production | Requires explicit consent, a stated target path, free-disk check (a dump is about the size of the used heap), and a stated pause. Heap dumps contain secrets (passwords, tokens, personal data). Never share or upload them; redaction is NOT a reliable safeguard. Analyze locally and delete afterwards. |\n\nNever run Tier 2 or Tier 3 commands against production unless the user explicitly instructs it. Run diagnostic tools as the same OS user as the target JVM. Prefer reproducing on dev or staging.\n\n## Decision table\n\n| Symptom | First step | Then | Reference |\n|---------|-----------|------|-----------|\n| High CPU | Thread dumps x3 (Tier 1) + `top -H` to map hot native thread ids to `nid` | JFR or async-profiler CPU flame graph (Tier 2) | [threads](references\u002Fthread-dumps.md), [jfr](references\u002Fjfr.md), [async-profiler](references\u002Fasync-profiler.md) |\n| Memory leak \u002F OOM | `jstat -gcutil`, `GC.class_histogram -all=true` twice, minutes apart (Tier 2: safepoint pause even with `-all=true`; without it a full GC too; get consent on production) | Heap dump + Eclipse MAT (Tier 3) or JFR OldObjectSample (Tier 2) | [heap](references\u002Fheap.md), [gc](references\u002Fgc.md) |\n| Slow startup | `-Xlog:class+load`, framework startup\u002Fcondition reports, timestamped logs | JFR from start, async-profiler wall-clock | [jfr](references\u002Fjfr.md), [async-profiler](references\u002Fasync-profiler.md) |\n| Deadlock \u002F thread starvation | `jcmd \u003Cpid> Thread.print` (reports deadlocks), compare dumps over time | Virtual threads: `Thread.dump_to_file` | [threads](references\u002Fthread-dumps.md) |\n| GC pauses | GC log (`-Xlog:gc*`) and `jstat -gc` | JFR GC events; tune collector\u002Fheap | [gc](references\u002Fgc.md) |\n| Native memory growth (RSS grows, heap does not) | Compare RSS vs heap; enable NMT, `jcmd VM.native_memory baseline` \u002F `summary.diff` (Tier 2) | async-profiler `nativemem` or allocator tools | [nmt](references\u002Fnative-memory.md), [containers](references\u002Fcontainers.md) |\n| Slow requests | Tracing\u002Fmetrics and logs first; Actuator or Dev UI (see below) | JFR (socket\u002Ffile\u002Flock events), async-profiler wall-clock | [jfr](references\u002Fjfr.md), [async-profiler](references\u002Fasync-profiler.md) |\n| JVM crash \u002F hang, no tools respond | `hs_err_pid*.log`, core dump | `jhsdb` (Tier 3) | [basics](references\u002Fjcmd-basics.md) |\n\nStart with [jps\u002Fjcmd basics](references\u002Fjcmd-basics.md) to identify the target JVM and confirm which JDK version is running.\n\n## Workflow\n\n1. Capture the symptom precisely (when, how often, since which change, JDK version, container limits).\n2. Choose the tier needed; state the command, its overhead, and output location, and get consent for Tier 2\u002F3.\n3. Collect data to a dedicated directory, with timestamps. Prefer several samples over one.\n4. Form a hypothesis from the data, then confirm with a second source (for example a thread dump plus a flame graph).\n5. Fix, re-measure with the same method, and clean up artifacts (dumps, recordings).\n\n## Application-level insights (optional)\n\nJDK tools see the JVM; some questions (which endpoint, which SQL query, which bean) are easier at the application level. Optional options, in order of preference:\n\n- **Spring Boot Actuator** (`metrics`, `health`, `loggers`, `httpexchanges`) and **Quarkus Dev UI** \u002F Micrometer metrics are built in and need no extra tool. Expose Actuator endpoints minimally; For `heapdump` and `threaddump`, follow the policy in the `spring-observability` skill: never expose them over public HTTP; the only exception is a temporary, user-consented window with authentication, TLS and network restriction, removed afterwards.\n- **BootUI** (https:\u002F\u002Fgithub.com\u002Fjdubois\u002Fboot-ui , https:\u002F\u002Fwww.julien-dubois.com\u002Fboot-ui\u002F): a local-only developer console with an opt-in MCP server for Spring Boot and Quarkus. Optional. Its skill can be installed with `gh skill install jdubois\u002Fboot-ui skills\u002Fbootui`.\n\nIf considering BootUI:\n\n- Ask the user for consent before adding any dependency or installing the skill.\n- Use it in a local\u002Fdev profile only; never expose it on a network, and never enable its heap dump, thread dump endpoints or MCP server in production.\n- Check the capability and version first (read its README for the supported Spring Boot \u002F Quarkus versions) instead of assuming features.\n\nFollow the project's own documentation for usage; this skill does not reproduce it.\n\n## Containers\n\nSee [containers](references\u002Fcontainers.md) for attaching tools inside containers, `-XX:MaxRAMPercentage`, and cgroup memory limits.\n\n## References\n\n- [jps \u002F jcmd basics](references\u002Fjcmd-basics.md)\n- [Thread dumps and deadlocks](references\u002Fthread-dumps.md)\n- [Heap, histograms, Eclipse MAT](references\u002Fheap.md)\n- [GC logs and jstat](references\u002Fgc.md)\n- [JFR and JDK Mission Control](references\u002Fjfr.md)\n- [async-profiler](references\u002Fasync-profiler.md)\n- [Native Memory Tracking](references\u002Fnative-memory.md)\n- [Containers](references\u002Fcontainers.md)\n- Debugger-based investigation: the `java-debugging` skill.\n\nOfficial docs (prefer them over this skill for the JDK in use; change `21` to your version): `jcmd` \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Fdocs\u002Fspecs\u002Fman\u002Fjcmd.html>, `jfr` \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Fdocs\u002Fspecs\u002Fman\u002Fjfr.html>, JFR guide \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Fjfr\u002Fintroduction-jdk-flight-recorder.html>, troubleshooting guide \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Ftroubleshoot\u002F>, async-profiler releases \u003Chttps:\u002F\u002Fgithub.com\u002Fasync-profiler\u002Fasync-profiler\u002Freleases>.\n","# Java Diagnostics\n\nPick the lightest tool that answers the question, starting from the symptom.\n\n## Permission tiers (obey them)\n\n| Tier | Tools | Rule |\n|------|-------|------|\n| 1. Read-only | `jps -l`, `jcmd \u003Cpid> help\u002FVM.version\u002FVM.flags\u002FThread.print`, `jstat`, `jstack`, reading logs | May run after stating the exact command. Class histograms (`jcmd \u003Cpid> GC.class_histogram`, `jmap -histo`, `jmap -histo:live`) are NOT Tier 1: they run heap inspection at a safepoint and can pause application threads on a large heap, so treat them as Tier 2 (consent, stated overhead). The default forms and `-histo:live` additionally force a full GC; `-all=true` \u002F `jmap -histo` skip the full GC but still pause during the scan (and count unreachable objects). |\n| 2. Recording \u002F attach | JFR (`JFR.start`, `-XX:StartFlightRecording`), async-profiler, NMT (`-XX:NativeMemoryTracking`), enabling GC logs | Requires user consent. State duration and expected overhead (JFR default profile is about 1-2%; async-profiler depends on mode; NMT summary roughly 5-10%, detail more) before running. |\n| 3. Intrusive \u002F sensitive | Heap dumps (`GC.heap_dump`, `jmap -dump`), `jhsdb`, commands that print JVM arguments or system properties (`jps -v\u002F-lv\u002F-m`, bare `jcmd`, `VM.system_properties`, `VM.command_line`, `jinfo`, `ps aux` on a Java process; they can expose secrets, redact output), JDWP with suspend, anything on production | Requires explicit consent, a stated target path, free-disk check (a dump is about the size of the used heap), and a stated pause. Heap dumps contain secrets (passwords, tokens, personal data). Never share or upload them; redaction is NOT a reliable safeguard. Analyze locally and delete afterwards. |\n\nNever run Tier 2 or Tier 3 commands against production unless the user explicitly instructs it. Run diagnostic tools as the same OS user as the target JVM. Prefer reproducing on dev or staging.\n\n## Decision table\n\n| Symptom | First step | Then | Reference |\n|---------|-----------|------|-----------|\n| High CPU | Thread dumps x3 (Tier 1) + `top -H` to map hot native thread ids to `nid` | JFR or async-profiler CPU flame graph (Tier 2) | [threads](references\u002Fthread-dumps.md), [jfr](references\u002Fjfr.md), [async-profiler](references\u002Fasync-profiler.md) |\n| Memory leak \u002F OOM | `jstat -gcutil`, `GC.class_histogram -all=true` twice, minutes apart (Tier 2: safepoint pause even with `-all=true`; without it a full GC too; get consent on production) | Heap dump + Eclipse MAT (Tier 3) or JFR OldObjectSample (Tier 2) | [heap](references\u002Fheap.md), [gc](references\u002Fgc.md) |\n| Slow startup | `-Xlog:class+load`, framework startup\u002Fcondition reports, timestamped logs | JFR from start, async-profiler wall-clock | [jfr](references\u002Fjfr.md), [async-profiler](references\u002Fasync-profiler.md) |\n| Deadlock \u002F thread starvation | `jcmd \u003Cpid> Thread.print` (reports deadlocks), compare dumps over time | Virtual threads: `Thread.dump_to_file` | [threads](references\u002Fthread-dumps.md) |\n| GC pauses | GC log (`-Xlog:gc*`) and `jstat -gc` | JFR GC events; tune collector\u002Fheap | [gc](references\u002Fgc.md) |\n| Native memory growth (RSS grows, heap does not) | Compare RSS vs heap; enable NMT, `jcmd VM.native_memory baseline` \u002F `summary.diff` (Tier 2) | async-profiler `nativemem` or allocator tools | [nmt](references\u002Fnative-memory.md), [containers](references\u002Fcontainers.md) |\n| Slow requests | Tracing\u002Fmetrics and logs first; Actuator or Dev UI (see below) | JFR (socket\u002Ffile\u002Flock events), async-profiler wall-clock | [jfr](references\u002Fjfr.md), [async-profiler](references\u002Fasync-profiler.md) |\n| JVM crash \u002F hang, no tools respond | `hs_err_pid*.log`, core dump | `jhsdb` (Tier 3) | [basics](references\u002Fjcmd-basics.md) |\n\nStart with [jps\u002Fjcmd basics](references\u002Fjcmd-basics.md) to identify the target JVM and confirm which JDK version is running.\n\n## Workflow\n\n1. Capture the symptom precisely (when, how often, since which change, JDK version, container limits).\n2. Choose the tier needed; state the command, its overhead, and output location, and get consent for Tier 2\u002F3.\n3. Collect data to a dedicated directory, with timestamps. Prefer several samples over one.\n4. Form a hypothesis from the data, then confirm with a second source (for example a thread dump plus a flame graph).\n5. Fix, re-measure with the same method, and clean up artifacts (dumps, recordings).\n\n## Application-level insights (optional)\n\nJDK tools see the JVM; some questions (which endpoint, which SQL query, which bean) are easier at the application level. Optional options, in order of preference:\n\n- **Spring Boot Actuator** (`metrics`, `health`, `loggers`, `httpexchanges`) and **Quarkus Dev UI** \u002F Micrometer metrics are built in and need no extra tool. Expose Actuator endpoints minimally; For `heapdump` and `threaddump`, follow the policy in the `spring-observability` skill: never expose them over public HTTP; the only exception is a temporary, user-consented window with authentication, TLS and network restriction, removed afterwards.\n- **BootUI** (https:\u002F\u002Fgithub.com\u002Fjdubois\u002Fboot-ui , https:\u002F\u002Fwww.julien-dubois.com\u002Fboot-ui\u002F): a local-only developer console with an opt-in MCP server for Spring Boot and Quarkus. Optional. Its skill can be installed with `gh skill install jdubois\u002Fboot-ui skills\u002Fbootui`.\n\nIf considering BootUI:\n\n- Ask the user for consent before adding any dependency or installing the skill.\n- Use it in a local\u002Fdev profile only; never expose it on a network, and never enable its heap dump, thread dump endpoints or MCP server in production.\n- Check the capability and version first (read its README for the supported Spring Boot \u002F Quarkus versions) instead of assuming features.\n\nFollow the project's own documentation for usage; this skill does not reproduce it.\n\n## Containers\n\nSee [containers](references\u002Fcontainers.md) for attaching tools inside containers, `-XX:MaxRAMPercentage`, and cgroup memory limits.\n\n## References\n\n- [jps \u002F jcmd basics](references\u002Fjcmd-basics.md)\n- [Thread dumps and deadlocks](references\u002Fthread-dumps.md)\n- [Heap, histograms, Eclipse MAT](references\u002Fheap.md)\n- [GC logs and jstat](references\u002Fgc.md)\n- [JFR and JDK Mission Control](references\u002Fjfr.md)\n- [async-profiler](references\u002Fasync-profiler.md)\n- [Native Memory Tracking](references\u002Fnative-memory.md)\n- [Containers](references\u002Fcontainers.md)\n- Debugger-based investigation: the `java-debugging` skill.\n\nOfficial docs (prefer them over this skill for the JDK in use; change `21` to your version): `jcmd` \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Fdocs\u002Fspecs\u002Fman\u002Fjcmd.html>, `jfr` \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Fdocs\u002Fspecs\u002Fman\u002Fjfr.html>, JFR guide \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Fjfr\u002Fintroduction-jdk-flight-recorder.html>, troubleshooting guide \u003Chttps:\u002F\u002Fdocs.oracle.com\u002Fen\u002Fjava\u002Fjavase\u002F21\u002Ftroubleshoot\u002F>, async-profiler releases \u003Chttps:\u002F\u002Fgithub.com\u002Fasync-profiler\u002Fasync-profiler\u002Freleases>.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fjava-diagnostics",5354,"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-14 05:37:52",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add github\u002Fawesome-copilot --skill java-diagnostics",{"tool":62,"command":63},"bunx","bunx skills add github\u002Fawesome-copilot --skill java-diagnostics",{"tool":65,"command":66},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill java-diagnostics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002FSKILL.md",true,[70,76,80,84,88,92,96,100,104],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"package.json","REFERENCE","参考文档",832,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsandbox-packs\u002Fsandbox-diff\u002Fpackage.json",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fasync-profiler.md",3082,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fasync-profiler.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fcontainers.md",1695,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fcontainers.md",{"path":85,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fgc.md",1609,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fgc.md",{"path":89,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fheap.md",3083,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fheap.md",{"path":93,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fjcmd-basics.md",1939,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fjcmd-basics.md",{"path":97,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fjfr.md",2339,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fjfr.md",{"path":101,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fnative-memory.md",1567,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fnative-memory.md",{"path":105,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fthread-dumps.md",3377,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-diagnostics\u002Freferences\u002Fthread-dumps.md",[109,142,169,198,232,249],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":123,"publishedAt":41},"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",[115,120],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":121,"categoryName":122,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发",[124,125,126,127,128,23,129,130,131,132,133,134,135,136,137,138,34,139,140,141],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions","with",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":41},"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",[148],{"categoryNo":121,"categoryName":122,"taxonomyType":118,"taxonomyTypeDesc":119},[150,151,152,153,154,155,25,156,157,158,159,160,161,162,163,164,165,166,167,168],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":173,"sourceHtmlUrl":174,"categories":175,"keywords":181,"publishedAt":41},"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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[182,183,184,185,186,187,25,128,188,37,189,190,191,192,193,34,194,195,196,197],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":202,"sourceHtmlUrl":203,"categories":204,"keywords":209,"publishedAt":41},"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",[205,208],{"categoryNo":206,"categoryName":207,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},[210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,23,225,226,227,228,229,25,230,231],"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":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":236,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":245,"publishedAt":41},"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",[240,241,244],{"categoryNo":206,"categoryName":207,"taxonomyType":118,"taxonomyTypeDesc":119},{"categoryNo":242,"categoryName":243,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":121,"categoryName":122,"taxonomyType":118,"taxonomyTypeDesc":119},[246,153,219,247,248],"resemble detect","https","identity",{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":236,"licenseFileUrl":253,"sourceHtmlUrl":254,"categories":255,"keywords":260,"publishedAt":41},"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",[256,259],{"categoryNo":257,"categoryName":258,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":121,"categoryName":122,"taxonomyType":118,"taxonomyTypeDesc":119},[261,262,263,264,183,129,9,152,265,266,247,267,268,269,270,271,272,273,274,275,276,277,137,278,279,280,281],"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"]