[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADFRTYSDW71V9B1FZ5SFQV":3,"skill-same:01M6ADFRTYSDW71V9B1FZ5SFQV":64},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6ADFRTYSDW71V9B1FZ5SFQV","desk-journal",null,"Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries. A good entry has: what was done, current state, next step.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fdesk-journal\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"desk journal","journal","state","memory","current state","session","entries","good","done","next","read","entry","write","persistent memory","append","next step","2026-11-10 10:12:30",false,"---\nname: desk-journal\ndescription: 'Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries. A good entry has: what was done, current state, next step.'\n---\n\n# Desk Journal\n\nManage a desk's journal — the persistent memory that survives\nsession boundaries.\n\n## When to use\n\n- **End of session:** Write what was done, current state, next step\n- **Start of session:** Read the journal to pick up where you left off\n- **Mid-session checkpoint:** Note significant progress or decisions\n- **Desk wind-down:** Write a final summary when a desk is being closed\n\n## How to write a journal entry\n\nAppend to `desks\u002F\u003Cdesk-name>\u002Fjournal.md` (for a desk in a group folder,\n`\u003Cgroup>-desks\u002F\u003Cdesk-name>\u002Fjournal.md` — look in `desks\u002F` first, then in\neach `*-desks\u002F` folder). Each entry is a section:\n\n```markdown\n## \u003Cdate> — \u003Cshort summary>\n- **Worked on:** \u003Cwhat was done this session>\n- **Current state:** \u003Cwhere things stand right now>\n- **Next step:** \u003Cwhat the next session should pick up>\n```\n\n### Guidelines\n\n- **Be specific.** \"Worked on security scanning\" is useless to the\n  next session. \"Scanned repos A, B, C for CWE-502; found 3\n  findings in A, 0 in B and C; findings triaged to bench\" — that's\n  a trail.\n- **Include what didn't work.** Dead ends are valuable — they prevent\n  the next session from walking the same path.\n- **Keep it short.** The journal is a trail marker, not a diary.\n  3-5 lines per entry. If you need more, the important context\n  should go on the bench as a separate artifact.\n- **Always include next step.** The next session starts from zero.\n  Without a next step, it has to re-derive everything.\n\n## End-of-desk entry\n\nWhen a desk is being wound down (not just a session ending, but\nthe desk itself closing):\n\n```markdown\n## \u003Cdate> — Desk closed\n- **Summary:** \u003Cwhat this desk accomplished overall>\n- **Artifacts:** \u003Cwhat's on the bench from this desk>\n- **Handoff:** \u003Canything another desk or the operator needs to know>\n```\n\n## Reading the journal\n\nAt session start, read the desk's journal to pick up context.\nThe most recent entry is the most important — it has the current\nstate and next step. Earlier entries provide history if needed.\n\n## Principles\n\n- The journal is a cairn — stones left so the next traveler finds\n  the way. Every entry is a stone.\n- Honesty over completeness. \"I got stuck on X and don't know why\"\n  is more useful than silence.\n- The journal is for the next session, not for the current one.\n  Write for someone who knows nothing about what you just did.\n","# Desk Journal\n\nManage a desk's journal — the persistent memory that survives\nsession boundaries.\n\n## When to use\n\n- **End of session:** Write what was done, current state, next step\n- **Start of session:** Read the journal to pick up where you left off\n- **Mid-session checkpoint:** Note significant progress or decisions\n- **Desk wind-down:** Write a final summary when a desk is being closed\n\n## How to write a journal entry\n\nAppend to `desks\u002F\u003Cdesk-name>\u002Fjournal.md` (for a desk in a group folder,\n`\u003Cgroup>-desks\u002F\u003Cdesk-name>\u002Fjournal.md` — look in `desks\u002F` first, then in\neach `*-desks\u002F` folder). Each entry is a section:\n\n```markdown\n## \u003Cdate> — \u003Cshort summary>\n- **Worked on:** \u003Cwhat was done this session>\n- **Current state:** \u003Cwhere things stand right now>\n- **Next step:** \u003Cwhat the next session should pick up>\n```\n\n### Guidelines\n\n- **Be specific.** \"Worked on security scanning\" is useless to the\n  next session. \"Scanned repos A, B, C for CWE-502; found 3\n  findings in A, 0 in B and C; findings triaged to bench\" — that's\n  a trail.\n- **Include what didn't work.** Dead ends are valuable — they prevent\n  the next session from walking the same path.\n- **Keep it short.** The journal is a trail marker, not a diary.\n  3-5 lines per entry. If you need more, the important context\n  should go on the bench as a separate artifact.\n- **Always include next step.** The next session starts from zero.\n  Without a next step, it has to re-derive everything.\n\n## End-of-desk entry\n\nWhen a desk is being wound down (not just a session ending, but\nthe desk itself closing):\n\n```markdown\n## \u003Cdate> — Desk closed\n- **Summary:** \u003Cwhat this desk accomplished overall>\n- **Artifacts:** \u003Cwhat's on the bench from this desk>\n- **Handoff:** \u003Canything another desk or the operator needs to know>\n```\n\n## Reading the journal\n\nAt session start, read the desk's journal to pick up context.\nThe most recent entry is the most important — it has the current\nstate and next step. Earlier entries provide history if needed.\n\n## Principles\n\n- The journal is a cairn — stones left so the next traveler finds\n  the way. Every entry is a stone.\n- Honesty over completeness. \"I got stuck on X and don't know why\"\n  is more useful than silence.\n- The journal is for the next session, not for the current one.\n  Write for someone who knows nothing about what you just did.\n",{"name":5,"description":7},"main","227949a7542a55d2155c00e7cdb998d9a0fee4f3","skills\u002Fdesk-journal",5340,"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 13:41:32",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add github\u002Fawesome-copilot --skill desk-journal",{"tool":56,"command":57},"bunx","bunx skills add github\u002Fawesome-copilot --skill desk-journal",{"tool":59,"command":60},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill desk-journal","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fdesk-journal\u002FSKILL.md",true,[],[65,98,126,156,190,207],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":79,"publishedAt":35},"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",[71,76],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发",[80,81,82,83,84,85,86,87,29,31,88,89,90,91,92,93,94,95,96,97],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":35},"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",[104],{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},[106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":138,"publishedAt":35},"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",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[139,140,141,142,143,144,112,84,145,146,147,148,149,150,151,94,152,153,154,155],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":167,"publishedAt":35},"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",[163,166],{"categoryNo":164,"categoryName":165,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},[168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,85,183,184,185,186,187,112,188,189],"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":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":194,"licenseFileUrl":195,"sourceHtmlUrl":196,"categories":197,"keywords":203,"publishedAt":35},"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",[198,199,202],{"categoryNo":164,"categoryName":165,"taxonomyType":74,"taxonomyTypeDesc":75},{"categoryNo":200,"categoryName":201,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},[204,109,177,205,206],"resemble detect","https","identity",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":194,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":218,"publishedAt":35},"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",[214,217],{"categoryNo":215,"categoryName":216,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},[219,220,221,222,140,86,9,108,223,224,205,225,226,227,228,229,230,231,232,233,234,235,92,236,237,238,239],"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"]