Google Dev Docs

Community

surendranb

google-dev-docs

Use when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for developers using the Google developer documentation style guide.

Overview

Publisher	surendranb
Repository	`writing-skills`
Skill name	`google-dev-docs`
Stars	54
Forks	3
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by surendranb on GitHub. Read the source before you install it.

Installation

Install the Google Dev Docs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/surendranb/writing-skills/tree/main/skills/google-dev-docs
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/surendranb/writing-skills.git /tmp/writing-skills
mkdir -p .claude/skills
cp -r /tmp/writing-skills/skills/google-dev-docs .claude/skills/google-dev-docs

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Google Dev Docs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Google Dev Docs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Google Dev Docs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Google Developer Documentation Style

Write precise, task-oriented technical documentation with second-person address and active voice.

The core rule

Task-oriented headings, present tense, second person ("you"), active voice.

Workflow: state user goal in title → prerequisites first → numbered steps with concrete code examples → verification step.

Mechanics

Second person. Address the developer directly as "you"; avoid "we", "us", or third-person generalities.
Present tense. Describe current system behavior in present tense ("Returns a 200 OK status", not "Will return").
Task-oriented headings. Start headings with gerunds or action verbs ("Configuring authentication", not "Authentication overview").
Active voice. "The server processes the request" rather than "The request is processed by the server".
Code blocks with context. Every code snippet must include necessary imports, setup, and expected output.
Pronoun clarity. Ensure "this", "that", and "it" clearly point to a preceding noun.
Consistent terminology. Use identical terms across guides, API references, and UI labels.
Concise error messages. Explain what went wrong and how to fix it immediately.

Verify

Headings use gerunds or action verbs describing tasks
Sentences consistently use second person ("you")
Code snippets are complete, syntactically valid, and tested
Active voice used throughout instructions
Present tense used for API descriptions

Do not

Use future tense for deterministic software behavior ("The method will return...")
Leave code snippets without imports or setup context
Use vague filler phrases ("Simply run...", "Just configure...")
Mix second person and first person within the same tutorial

References

For exact mechanical rules (numbers, percentages, ordinals, ranges, abbreviations, units), read references/REFERENCE.md when a draft contains any of these — load on demand, not upfront.

Example transformations

Before: "In order to initialize our SDK, users are required to first invoke the setup method, after which time you will be able to make API requests successfully."

After: "To initialize the SDK, call setup(). Once initialized, you can make API requests."

Before: "Simply add the configuration dictionary to your project and you're good to go!"

After: "Add the configuration dictionary to your project configuration file."

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/REFERENCE.md2 KB

Frequently asked questions

What does the Google Dev Docs AI skill do?

Use when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for developers using the Google developer documentation style guide.

Why use Google Dev Docs on TypingMind?

Because you install it once and use it with any model. Google Dev Docs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Google Dev Docs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/surendranb/writing-skills/tree/main/skills/google-dev-docs. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Google Dev Docs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Google Dev Docs?

As many as you like. As long as a model supports skills, you can use Google Dev Docs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Google Dev Docs AI skill free?

Yes. It is published on GitHub by surendranb under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Discord Clawd

openclaw

OrganizationPopular

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Google Developer Documentation Style

The core rule

Mechanics

Verify

Do not

References

Example transformations

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now