Commit
LennartHennigs/Button2
Stage and commit current changes for Button2 — checks for needed CHANGELOG/README/CLAUDE.md updates, creates a branch if on master, writes a commit message, and commits
Apply the Google Developer Documentation Style Guide to user-facing docs, READMEs, AGENTS.md, and commit messages.
Install Google Developer Style
$ npx skills add OpenAgentsInc/openagents --skill google-developer-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenAgentsInc/openagents google-developer-style --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenAgentsInc/openagents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/google-developer-style .claude/skills/google-developer-style && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "google-developer-style" agent skill from https://github.com/OpenAgentsInc/openagents/tree/main/.agents/skills/google-developer-style into .claude/skills/google-developer-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-developer-style", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenAgentsInc/openagents/tree/main/.agents/skills/google-developer-styleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenAgentsInc/openagents --skill google-developer-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenAgentsInc/openagents google-developer-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenAgentsInc/openagents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/google-developer-style .agents/skills/google-developer-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-developer-style" agent skill from https://github.com/OpenAgentsInc/openagents/tree/main/.agents/skills/google-developer-style into .agents/skills/google-developer-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-developer-style", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenAgentsInc/openagents --skill google-developer-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenAgentsInc/openagents google-developer-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenAgentsInc/openagents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/google-developer-style .cursor/skills/google-developer-style && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-developer-style" agent skill from https://github.com/OpenAgentsInc/openagents/tree/main/.agents/skills/google-developer-style into .cursor/skills/google-developer-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-developer-style", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenAgentsInc/openagents.git --path .agents/skills/google-developer-style--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenAgentsInc/openagents --skill google-developer-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenAgentsInc/openagents google-developer-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenAgentsInc/openagents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/google-developer-style .gemini/skills/google-developer-style && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "google-developer-style" agent skill from https://github.com/OpenAgentsInc/openagents/tree/main/.agents/skills/google-developer-style into .gemini/skills/google-developer-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-developer-style", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenAgentsInc/openagents google-developer-styleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenAgentsInc/openagents --skill google-developer-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenAgentsInc/openagents.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/google-developer-style .github/skills/google-developer-style && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "google-developer-style" agent skill from https://github.com/OpenAgentsInc/openagents/tree/main/.agents/skills/google-developer-style into .github/skills/google-developer-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-developer-style", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenAgentsInc/openagents --skill google-developer-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenAgentsInc/openagents google-developer-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenAgentsInc/openagents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/google-developer-style .opencode/skills/google-developer-style && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-developer-style" agent skill from https://github.com/OpenAgentsInc/openagents/tree/main/.agents/skills/google-developer-style into .opencode/skills/google-developer-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-developer-style", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
google-developer-style- GitHub stars
- 455
- Token cost
- ~630 tokens
- SKILL.md length
- 328 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Apply the Google Developer Documentation Style Guide to user-facing docs, READMEs, AGENTS.md, and commit messages.
- Reviewing prose in this repo
- SKILL.md covers How to use this skill, Voice and tone, Language and grammar and Formatting, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Commit messages
What it does
Google Developer Style is an agent skill from OpenAgentsInc/openagents. Apply the Google Developer Documentation Style Guide to user-facing docs, READMEs, AGENTS.md, and commit messages. Use when writing or reviewing prose in this repo.
Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages, Technical documentation and Agent instruction files. The licence is Apache-2.0.
When your agent uses it
- Reviewing prose in this repo
- Tasks that involve Commit messages
- Tasks that involve Technical documentation
Example prompts
- “/google-developer-style”
What it can do on your machine
Read from SKILL.md and the folder at commit ad9f02f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developers.google.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Google Developer Style loads about 630 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 328 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from OpenAgentsInc/openagents at commit ad9f02f, republished under its Apache-2.0 licence (© OpenAgentsInc). 328 words, ~630 tokens.
Download SKILL.mdSave it as
.claude/skills/google-developer-style/SKILL.md (or your agent's skills folder).- name
- google-developer-style
- description
- Apply the Google Developer Documentation Style Guide to user-facing docs, READMEs, AGENTS.md, and commit messages. Use when writing or reviewing prose in this repo.
Google Developer Documentation Style
Use this skill when you write or review user-facing documentation, READMEs, AGENTS.md, and commit messages for OpenAgents.
How to use this skill
Apply these rules to the text you produce or edit. When a rule would make something less clear, break the rule and stay consistent.
Voice and tone
- Be conversational and friendly, but not frivolous or overly casual.
- Write as a knowledgeable friend who understands what the developer wants to do.
- Avoid jargon, buzzwords, clichés, metaphors, ableist language, and pop-culture references.
- Avoid exclamation marks and over-polite phrases such as "please" or "please note."
- Avoid filler words like "simply," "just," "it's easy," or "quickly" in procedures.
- Avoid phrasing like "let's do something" or "we" for the reader; speak to the reader with "you."
Language and grammar
- Use active voice. Make clear who performs the action.
- Use second person ("you") for the reader.
- Use present tense.
- Use standard American spelling and punctuation.
- Put conditions before instructions, not after.
- Use serial commas.
- Do not use ampersands (&) as conjunctions in body text or headings.
Formatting
- Use sentence case for all headings, titles, and navigation.
- Use code font for code, filenames, class names, method names, HTTP status codes, placeholders, and user input.
- Use bold for UI elements and run-in headings.
- Use italics sparingly, mainly when introducing or defining terms.
- Underline only for link text.
- Do not override global font styles.
Lists
- Use numbered lists for sequences and procedures.
- Use bulleted lists for related but unordered items.
- Use description lists for related pairs of data.
- Keep list items parallel in structure.
Code and links
- Put code in text in code font.
- Use descriptive link text. Avoid "click here" or "this page."
- Use unambiguous date and time formatting.
- Provide alt text for images.
Banned patterns
- "Dude!" / "This is awesome!"
- "It's that simple" / "It's easy" / "simply"
- "Please" in instructions
- "At this time" / "please note"
- "Let's" as an imperative to the reader
- All-caps or title-case headings
Source
© OpenAgentsInc, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/google-developer-style of OpenAgentsInc/openagents.
Open the folder on GitHubat commit ad9f02f
Compare with similar skills
Google Developer Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Developer Style this skillOpenAgentsInc/openagents | 455 | — | ~630 | Automated safety check: Pass | Apache-2.0 | |
| CommitLennartHennigs/Button2 | 565 | — | ~562 | Automated safety check: Pass | MIT | |
| CommitLennartHennigs/ESPRotary | 188 | — | ~590 | Automated safety check: Pass | MIT | |
| Swig Conventionsswig/swig | 6.3k | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| Create Skill Samplepnp/copilot-prompts | 891 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Release Docs SyncUfoMiao/zcf | 6.1k | — | ~4k | Automated safety check: Pass | MIT |
Similar skills
Commit
LennartHennigs/ESPRotary
Stage and commit current changes for ESPRotary — checks for needed CHANGELOG/README/CLAUDE.md updates, creates a branch if on master, writes a commit message, and commits
Swig Conventions
swig/swig
SWIG source and contribution conventions: clang-format / code formatting, C/C++ comment style (quotes, widths, function header blocks), parser.y new-code rules, alphabetical ordering of makefile…
Create Skill Sample
pnp/copilot-prompts
This skill should be used when the user asks to "create a new skill sample", "add a skill", "scaffold a new skill", "contribute a skill", "create a GitHub Copilot skill", "build a custom skill", or…
Release Docs Sync
UfoMiao/zcf
Compares code changes since the last Git tag with the multilingual docs and CLAUDE.md, then updates them or only reports mismatches with --check-only.
Plain Writing
docwriter-org/plain-writing-skill
Writes and edits prose in a plain and boring style: simple everyday words, complete sentences, no dashes, no jargon, and no analogies.
More from OpenAgentsInc/openagents
Typesafe AI
OpenAgentsInc/openagents
Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.
Decision API
OpenAgentsInc/openagents
Call the OpenAgents decision API: authenticate with an oak bearer key, post state + typed questions to POST /v1/systemone, read Noul, Choice, and Score answers with their probabilities, and handle…
Openagents Decision API
OpenAgentsInc/openagents
Authenticate to and call the OpenAgents decision API — typed decisions, batch classification, durable jobs, and the bundled documentation — through the oak CLI, the oak-mcp server, or raw HTTP.
Nostr
OpenAgentsInc/openagents
How Nostr works in this repository: the three NIP lanes under nips/, the wire protocol (NIP-01), relay authentication (NIP-42), payload encryption (NIP-44), the Block agent NIPs the relay serves…
Related
Categories
Questions about Google Developer Style
What does Google Developer Style do?
Apply the Google Developer Documentation Style Guide to user-facing docs, READMEs, AGENTS.md, and commit messages. Google Developer Style is an agent skill from OpenAgentsInc/openagents.md, and commit messages.
When should I use Google Developer Style?
Google Developer Style fits situations like: reviewing prose in this repo; tasks that involve Commit messages; tasks that involve Technical documentation.
How do I install Google Developer Style in Claude Code?
Run `npx skills add OpenAgentsInc/openagents --skill google-developer-style -a claude-code`. Or copy the skill folder (.agents/skills/google-developer-style in OpenAgentsInc/openagents) into .claude/skills/google-developer-style in your project. Claude Code loads it when a task matches its description.
How do I install Google Developer Style in Codex?
Run `npx skills add OpenAgentsInc/openagents --skill google-developer-style -a codex`. Or copy the skill folder (.agents/skills/google-developer-style in OpenAgentsInc/openagents) into .agents/skills/google-developer-style in your project. Codex loads it when a task matches its description.
Can I use Google Developer Style in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenAgentsInc/openagents --skill google-developer-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-developer-style, .gemini/skills/google-developer-style, .github/skills/google-developer-style and .opencode/skills/google-developer-style in your project.
What does Google Developer Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Google Developer Style is instructions for the agent only.
Does Google Developer Style access the network?
SKILL.md names 1 domain. As links in the text: developers.google.com. This is read from the text; nothing was executed.
Is Google Developer Style safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Google Developer Style use?
Google Developer Style is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Google Developer Style use?
About 630 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Google Developer Style?
Skills that share tags, products or a category with Google Developer Style: Commit (LennartHennigs/Button2, 565 stars), Commit (LennartHennigs/ESPRotary, 188 stars), Swig Conventions (swig/swig, 6.3k stars) and Create Skill Sample (pnp/copilot-prompts, 891 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Developer Style?
OpenAgentsInc (a GitHub organization) maintains it in OpenAgentsInc/openagents, which has 455 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.
Source: OpenAgentsInc/openagents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.