Gws workflow weekly digest
Skill S3YED/appie-kit/skills/openclaw-imports/gws-workflow-weekly-digest
Google Workflow: Weekly summary: this week's meetings + unread email count.From its SKILL.md
npx -y skills add S3YED/appie-kit --skill gws-workflow-weekly-digestAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 226 tokens by cl100k_base, as published. Nobody here has run it
workflow +weekly-digest
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Weekly summary: this week's meetings + unread email count
Usage
gws workflow +weekly-digest
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--format | — | — | Output format: json (default), table, yaml, csv |
Examples
gws workflow +weekly-digest
gws workflow +weekly-digest --format table
Tips
- Read-only — never modifies data.
- Combines calendar agenda (week) with gmail triage summary.
See Also
- gws-shared — Global flags and auth
- gws-workflow — All cross-service productivity workflows commands
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most automation workflows skills give in 226 tokens
Counted across 813 of the 1,214 authors here whose files we hold, read 2026-09-06
- Use conventional commit message formatin 38 of 813, across 34 files
- Write tests before implementing codein 26 of 813, across 12 files
- Achieve at least 80 percent test coveragein 24 of 813, across 11 files
- Mock external dependencies for unit testsin 22 of 813, across 10 files
- Read product marketing context before asking questionsin 21 of 813, across 6 files
- Implement rollback plans for every deploymentin 21 of 813, across 9 files
- Follow the arrange-act-assert patternin 20 of 813, across 9 files
- Delete branches after mergingin 20 of 813, across 18 files
- Test all edge cases and error scenariosin 20 of 813, across 8 files
- Use semantic selectors for UI testsin 19 of 813, across 7 files
- Define sequence type and audience contextin 18 of 813, across 5 files
- Monitor feature drift and prediction distribution driftin 18 of 813, across 5 files
Said here and by no other author read
- Read shared skill for auth and security rules
- Run generate-skills if shared skill is missing
- Execute weekly digest workflow command
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.