[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJC6RVZYQQ9W6WVMDR2MXF":3,"skill-same:01M7BJC6RVZYQQ9W6WVMDR2MXF":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":13,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7BJC6RVZYQQ9W6WVMDR2MXF","google-workspace-setup",null,"Guidance and commands for setting up Google Workspace integration.","darkmatter\u002Fhermes","darkmatter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17834193?v=4","01M7BHSAW99WRAMTSSHNHX73V0","01M7BHSAXDR4PY4NA2DY5PN6W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fdevbox\u002Fprofiles\u002Fworker\u002Fskills\u002Fproductivity\u002Fgoogle-workspace-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: google-workspace-setup\ndescription: \"Guidance and commands for setting up Google Workspace integration.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Google, Workspace, Setup, OAuth, Configuration, Email, Calendar, Drive, Docs, Sheets]\n---\n\n# Google Workspace Setup\n\nThis skill provides the step-by-step process for setting up the Google Workspace skill, including OAuth authorization and credential management.\n\n## Prerequisites\n\n1.  **Google Cloud Project**: You need a Google Cloud project with the necessary APIs enabled (Gmail, Calendar, Drive, Sheets, Docs, People API).\n2.  **OAuth 2.0 Client ID**: Create an \"OAuth 2.0 Client ID\" of type \"Desktop app\" within your Google Cloud project. Download the JSON secret file.\n3.  **Advanced Protection (Optional)**: If your Google account uses Advanced Protection, your Workspace administrator must allowlist the OAuth client ID.\n\n## Setup Steps\n\nFollow these steps to authorize Hermes Agent to access your Google Workspace data.\n\n### Step 1: Provide Client Secret File\n\nYou will need to provide the path to the `client_secret.json` file you downloaded from the Google Cloud Console.\n\n**Action**: Please provide the **absolute path** to your `client_secret.json` file. For example: `~\u002FDownloads\u002Fclient_secret_....json`\n\n### Step 2: Specify Services\n\nTell me which Google services you need access to. This determines the required scopes for authorization.\n\n**Action**: Choose the services you need:\n- `email`\n- `calendar`\n- `drive`\n- `docs`\n- `sheets`\n- `contacts`\n- `all` (for full access)\n\nExample input: `email,calendar,drive`\n\n### Step 3: Authorization URL Generation\n\nOnce I have the client secret path and service list, I will generate an authorization URL. You will need to open this URL in your browser, log in to your Google account, and grant permission.\n\n### Step 4: Redirect URL Handling\n\nAfter you grant permission, your browser will redirect to a local URL (likely `http:\u002F\u002Flocalhost:1`). This redirect will fail, but it will contain an authorization `code` or a full OAuth URL.\n\n**Action**: **Copy the *entire* redirected URL** from your browser's address bar and provide it back to me.\n\n### Step 5: Complete Authorization\n\nI will use the provided URL\u002Fcode to complete the authorization process and save the necessary credentials.\n\n### Troubleshooting\n\n-   **`ACCESS_DENIED` Error**: If you receive an `access_denied` error during authorization, it most likely means your Google account is not listed as a test user in the Google Cloud Console's OAuth consent screen or that your Workspace admin has not allowed the client ID. Go to [Google Cloud Console](https:\u002F\u002Fconsole.cloud.google.com\u002Fapis\u002Fcredentials) to manage test users or have your admin whitelist the client ID.\n-   **Expired\u002FUsed Code**: If the authorization code expires or has been used, a new authorization URL will be provided. Repeat Step 4 with the new URL.\n-   **Insufficient Permission**: If commands fail with insufficient permission errors after setup, it might mean the initial scopes were too narrow. You may need to re-run the setup process (`$GSETUP --revoke` and then restart the flow) with a broader set of services.\n-   **Missing Dependencies**: Ensure you have `google-auth` and `google-api-python-client` installed. If not, you can install them using `python -m pip install google-auth google-api-python-client --upgrade`. Or, install the `gws` CLI tool from its GitHub repository and run `$GSETUP --install-deps`.\n\n## Usage\n\n**Environment Variable**: Set `GAPI` as a shorthand for the Google API script:\n\\`\\`\\`bash\nGAPI=\"python \\${HERMES_HOME:-$HOME\u002F.hermes}\u002Fskills\u002Fproductivity\u002Fgoogle-workspace\u002Fscripts\u002Fgoogle_api.py\"\n\\`\\`\\`\n\nRefer to the `google-workspace` skill's main documentation for detailed API usage examples.\n","# Google Workspace Setup\n\nThis skill provides the step-by-step process for setting up the Google Workspace skill, including OAuth authorization and credential management.\n\n## Prerequisites\n\n1.  **Google Cloud Project**: You need a Google Cloud project with the necessary APIs enabled (Gmail, Calendar, Drive, Sheets, Docs, People API).\n2.  **OAuth 2.0 Client ID**: Create an \"OAuth 2.0 Client ID\" of type \"Desktop app\" within your Google Cloud project. Download the JSON secret file.\n3.  **Advanced Protection (Optional)**: If your Google account uses Advanced Protection, your Workspace administrator must allowlist the OAuth client ID.\n\n## Setup Steps\n\nFollow these steps to authorize Hermes Agent to access your Google Workspace data.\n\n### Step 1: Provide Client Secret File\n\nYou will need to provide the path to the `client_secret.json` file you downloaded from the Google Cloud Console.\n\n**Action**: Please provide the **absolute path** to your `client_secret.json` file. For example: `~\u002FDownloads\u002Fclient_secret_....json`\n\n### Step 2: Specify Services\n\nTell me which Google services you need access to. This determines the required scopes for authorization.\n\n**Action**: Choose the services you need:\n- `email`\n- `calendar`\n- `drive`\n- `docs`\n- `sheets`\n- `contacts`\n- `all` (for full access)\n\nExample input: `email,calendar,drive`\n\n### Step 3: Authorization URL Generation\n\nOnce I have the client secret path and service list, I will generate an authorization URL. You will need to open this URL in your browser, log in to your Google account, and grant permission.\n\n### Step 4: Redirect URL Handling\n\nAfter you grant permission, your browser will redirect to a local URL (likely `http:\u002F\u002Flocalhost:1`). This redirect will fail, but it will contain an authorization `code` or a full OAuth URL.\n\n**Action**: **Copy the *entire* redirected URL** from your browser's address bar and provide it back to me.\n\n### Step 5: Complete Authorization\n\nI will use the provided URL\u002Fcode to complete the authorization process and save the necessary credentials.\n\n### Troubleshooting\n\n-   **`ACCESS_DENIED` Error**: If you receive an `access_denied` error during authorization, it most likely means your Google account is not listed as a test user in the Google Cloud Console's OAuth consent screen or that your Workspace admin has not allowed the client ID. Go to [Google Cloud Console](https:\u002F\u002Fconsole.cloud.google.com\u002Fapis\u002Fcredentials) to manage test users or have your admin whitelist the client ID.\n-   **Expired\u002FUsed Code**: If the authorization code expires or has been used, a new authorization URL will be provided. Repeat Step 4 with the new URL.\n-   **Insufficient Permission**: If commands fail with insufficient permission errors after setup, it might mean the initial scopes were too narrow. You may need to re-run the setup process (`$GSETUP --revoke` and then restart the flow) with a broader set of services.\n-   **Missing Dependencies**: Ensure you have `google-auth` and `google-api-python-client` installed. If not, you can install them using `python -m pip install google-auth google-api-python-client --upgrade`. Or, install the `gws` CLI tool from its GitHub repository and run `$GSETUP --install-deps`.\n\n## Usage\n\n**Environment Variable**: Set `GAPI` as a shorthand for the Google API script:\n\\`\\`\\`bash\nGAPI=\"python \\${HERMES_HOME:-$HOME\u002F.hermes}\u002Fskills\u002Fproductivity\u002Fgoogle-workspace\u002Fscripts\u002Fgoogle_api.py\"\n\\`\\`\\`\n\nRefer to the `google-workspace` skill's main documentation for detailed API usage examples.\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":38,"description":7},"Hermes Agent","1.0.0",{"hermes":26},{"tags":27},[28,29,30,31,32,33,34,35,36,37],"Google","Workspace","Setup","OAuth","Configuration","Email","Calendar","Drive","Docs","Sheets",[39,40,41],"linux","macos","windows","main","81189f70e1089f9b3a944ffc480e6887efd831b9","devbox\u002Fprofiles\u002Fworker\u002Fskills\u002Fproductivity\u002Fgoogle-workspace-setup","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes","https:\u002F\u002Fgithub.com\u002Fdarkmatter","dm.sh","2026-09-14 08:11:52",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add darkmatter\u002Fhermes --skill google-workspace-setup",{"tool":55,"command":56},"bunx","bunx skills add darkmatter\u002Fhermes --skill google-workspace-setup",{"tool":58,"command":59},"pnpm","pnpm dlx skills add darkmatter\u002Fhermes --skill google-workspace-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fdevbox\u002Fprofiles\u002Fworker\u002Fskills\u002Fproductivity\u002Fgoogle-workspace-setup\u002FSKILL.md",true,[],[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7BMC2PYBVXM6FQEZMBQZB4G","plan","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7BMBSEKDVQ09Z666RCWT7BR","monorepo-fleet-sync","Sync docs and configs when a Flue monorepo fleet changes.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fmonorepo-fleet-sync\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7BMBNWFJT2TJZ2AKA64GEV9","inspecting-hermes-desktop-dom","Read the live Hermes desktop DOM\u002FCSS over CDP.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Finspecting-hermes-desktop-dom\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7BMAZM4VJ97K7JD0FDN58M8","grounded-citations","Ground answers and documents in cited, verifiable sources.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7BMATPEDZ4BPP67Y4ZS0BMM","competitor-news-monitor","Watch named companies for material news; cited digests.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fcompetitor-news-monitor\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7BMAQZV7YFA2SFPT7HCVCTX","blocked-page-recovery","Recover blocked\u002Fpaywalled\u002FWAF'd pages via fallbacks.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fblocked-page-recovery\u002FSKILL.md",[],[]]