← Products

Productivity
βš™ Needs: the `gws` binary on the PATH (see the repo README fo…

gws recipe: Block focus time

Recurring weekly deep-work blocks shown as busy via RRULE β€” protect the deep work, not a meeting

At a glance
What
Recurring weekly deep-work blocks shown as busy via RRULE β€” protect the deep work, not a meeting
Cost
Free
Needs
the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free); the `gws-shared` and `gws-calendar` prerequisite skills installed first
Install
Copy the installer prompt below into your Muse β€” your agent does the rest.

Version:

@
Created by: @googleworkspace
⌁

Install

Prerequisites: the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free); the `gws-shared` and `gws-calendar` prerequisite skills installed first Install "gws recipe: Block focus time" for me. Teach my agent to protect deep-work hours β€” create recurring weekly focus blocks with a RRULE and transparency opaque so they show as busy, then verify with +agenda Repository: https://github.com/googleworkspace/cli/blob/main/skills/recipe-block-focus-time/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-cli-recipe-block-focus-time skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "googleworkspace-cli-recipe-block-focus-time". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the gws binary, run `gws auth login`). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat β€” credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β€” no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the βœ“ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β€” always check a build before installing it.