[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2FPYRYRRBBM66QF8MHP3V":3,"skill-same:01M7B2FPYRYRRBBM66QF8MHP3V":50},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B2FPYRYRRBBM66QF8MHP3V","google-workspace-ops",null,"Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fgoogle-workspace-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: google-workspace-ops\ndescription: Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.\nmetadata:\n  origin: ECC\n---\n\n# Google Workspace Ops\n\nThis skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.\n\n## When to Use\n\n- User needs to find a doc, sheet, or deck and update it in place\n- Consolidating plans, trackers, notes, or customer lists stored in Google Drive\n- Cleaning or restructuring a shared spreadsheet\n- Importing, repairing, or reformatting a Google Slides deck\n- Producing summaries from Docs, Sheets, or Slides for decision-making\n\n## Preferred Tool Surface\n\nUse Google Drive as the entry point, then switch to the right specialist:\n\n- Google Docs for text-heavy docs\n- Google Sheets for tabular work, formulas, and charts\n- Google Slides for decks, imports, template migration, and cleanup\n\nDo not guess structure from filenames alone. Inspect first.\n\n## Workflow\n\n### 1. Find the asset\n\nStart with the Drive search surface to locate:\n\n- the exact file\n- sibling assets\n- likely duplicates\n- recently modified versions\n\nIf several documents look similar, confirm by title, owner, modified time, or folder.\n\n### 2. Inspect before editing\n\nBefore making changes:\n\n- summarize current structure\n- identify tabs, headings, or slide count\n- detect whether the task is local cleanup or structural surgery\n\nPick the smallest tool that can safely perform the work.\n\n### 3. Edit with precision\n\n- For Docs: use index-aware edits, not vague rewrites\n- For Sheets: operate on explicit tabs and ranges\n- For Slides: distinguish content edits from visual cleanup or template migration\n\nIf the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.\n\n### 4. Keep the working system clean\n\nWhen the file is part of a larger workflow, also surface:\n\n- duplicate trackers\n- outdated decks\n- stale docs vs canonical docs\n- whether the asset should be archived, merged, or renamed\n\n## Output Format\n\nUse:\n\n```text\nASSET\n- file name\n- type\n- why this is the right file\n\nCURRENT STATE\n- structure summary\n- key problems or blockers\n\nACTION\n- edits made or recommended\n\nFOLLOW-UPS\n- archive \u002F merge \u002F duplicate cleanup \u002F next file to update\n```\n\n## Good Use Cases\n\n- \"Find the active planning doc and condense it\"\n- \"Clean up this customer spreadsheet and show me the churn-risk rows\"\n- \"Import this deck into Slides and make it presentable\"\n- \"Find the current tracker, not the stale duplicate\"\n","# Google Workspace Ops\n\nThis skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.\n\n## When to Use\n\n- User needs to find a doc, sheet, or deck and update it in place\n- Consolidating plans, trackers, notes, or customer lists stored in Google Drive\n- Cleaning or restructuring a shared spreadsheet\n- Importing, repairing, or reformatting a Google Slides deck\n- Producing summaries from Docs, Sheets, or Slides for decision-making\n\n## Preferred Tool Surface\n\nUse Google Drive as the entry point, then switch to the right specialist:\n\n- Google Docs for text-heavy docs\n- Google Sheets for tabular work, formulas, and charts\n- Google Slides for decks, imports, template migration, and cleanup\n\nDo not guess structure from filenames alone. Inspect first.\n\n## Workflow\n\n### 1. Find the asset\n\nStart with the Drive search surface to locate:\n\n- the exact file\n- sibling assets\n- likely duplicates\n- recently modified versions\n\nIf several documents look similar, confirm by title, owner, modified time, or folder.\n\n### 2. Inspect before editing\n\nBefore making changes:\n\n- summarize current structure\n- identify tabs, headings, or slide count\n- detect whether the task is local cleanup or structural surgery\n\nPick the smallest tool that can safely perform the work.\n\n### 3. Edit with precision\n\n- For Docs: use index-aware edits, not vague rewrites\n- For Sheets: operate on explicit tabs and ranges\n- For Slides: distinguish content edits from visual cleanup or template migration\n\nIf the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.\n\n### 4. Keep the working system clean\n\nWhen the file is part of a larger workflow, also surface:\n\n- duplicate trackers\n- outdated decks\n- stale docs vs canonical docs\n- whether the asset should be archived, merged, or renamed\n\n## Output Format\n\nUse:\n\n```text\nASSET\n- file name\n- type\n- why this is the right file\n\nCURRENT STATE\n- structure summary\n- key problems or blockers\n\nACTION\n- edits made or recommended\n\nFOLLOW-UPS\n- archive \u002F merge \u002F duplicate cleanup \u002F next file to update\n```\n\n## Good Use Cases\n\n- \"Find the active planning doc and condense it\"\n- \"Clean up this customer spreadsheet and show me the churn-risk rows\"\n- \"Import this deck into Slides and make it presentable\"\n- \"Find the current tracker, not the stale duplicate\"\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fgoogle-workspace-ops",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill google-workspace-ops",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill google-workspace-ops",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill google-workspace-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fgoogle-workspace-ops\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"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},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"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":71,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]