Repository navigation
Description
Two suggestions for the agent skills under .agents/skills/, which the README installs with npx skills for any agent.
1. Descriptions don't say when to use each skill. scripts/gen-agent-skills.mjs:71 generates description: "${title} operations through gog.", which produces, for example:
gog-contacts: "Google Contacts operations through gog."gog-people: "Google People operations through gog."
Agents choose a skill from its description alone, and several skills overlap with nothing in their descriptions to tell them apart:
- contacts and people (both have search, and people's search covers the Workspace directory)
- groups and
admin groups - gmail, inbox-triage and save-attachments
- calendar, meeting-prep and weekly-digest
- drive and drive-audit
The core skill's clearest routing rule ("use gog when built-in Google connectors are missing a feature") is in the body of gog/SKILL.md, which an agent doesn't see when it chooses a skill. A short "use for X; for Y use gog-Z" clause per skill would help, generated where possible.
2. gog/SKILL.md line 146 says "see $browser-use". That skill isn't in this repo. In an agent that has no browser-use skill, or that doesn't use $ references, the pointer leads nowhere. A plain sentence that names what's needed (a browser automation tool that can open the consent URL) would work in any agent.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon Nov 13, 2026
Codex review: this still needs some work.
Summary
This issue identifies two documentation gaps still present on current main; a focused generator and skill-docs fix remains useful.
Reproducibility: Static inspection confirms both reported text defects at the current main SHA; no agent misrouting or live authentication failure was reproduced.
Next step
Update generator-owned routing descriptions, clarify the core skill's trigger, replace the browser reference, and verify regenerated skills remain fresh.
Review details
Best possible solution:
Ship concise, accurate routing descriptions generated from maintained service metadata and describe browser automation requirements without assuming an external skill.
Do we have a high-confidence way to reproduce the issue?
Static inspection confirms both reported text defects at the current main SHA; no agent misrouting or live authentication failure was reproduced.
Is this the best way to solve the issue?
The proposed documentation approach fits the existing design in #864; service descriptions belong in the generator, and cross-references should reflect overlapping capabilities rather than invent exclusive boundaries.
AGENTS.md: found and applied where relevant.
Codex review notes: model internal, reasoning medium; reviewed against 6f910fffac0a.
Label changes
Label changes:
P3: This is bounded skill-documentation polish with no demonstrated failure of a Google operation or authentication flow.impact:ux-friction: Overlapping descriptions and an unavailable skill reference make agent discovery and reauth guidance less clear.issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.clawsweeper:source-repro: Current issue advisory state selects this label.clawsweeper:queueable-fix: Current issue advisory state selects this label.clawsweeper:fix-shape-clear: Current issue advisory state selects this label.Label justifications:
P3: This is bounded skill-documentation polish with no demonstrated failure of a Google operation or authentication flow.impact:ux-friction: Overlapping descriptions and an unavailable skill reference make agent discovery and reauth guidance less clear.Evidence reviewed
Acceptance criteria:
What I checked:
scripts/gen-agent-skills.mjs:71, 6f910fffac0a).agents/skills/gog/SKILL.md:146, 6f910fffac0a)internal/cmd/contacts_directory.go:19, 6f910fffac0a)scripts/gen-agent-skills.mjs:71, 4ddec67538e6).agents/skills/gog/SKILL.md:146, bd733de86dbe)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.Reviewed November 13, 2026, 12:11 AM ET / 05:11 UTC.
fix: preserve workspace request and output contracts
steipete commentedon Nov 14, 2026
Fixed in #1336. Generated service skills now describe when to use them and distinguish overlapping workflows. Core instructions explain browser consent without requiring an unshipped browser skill.
The regression failed against the previous main and passes with the fix. Full
make ci, independent P0–P2 review, and exact-head GitHub CI passed. The generated-skill consistency check passed.