Skip to content
TrustedSkillsbeta
Back to all skills

Adev Writing Guide

Checked
angular·vlatest·writing·MIT

Provides clear, concise writing guidance tailored to Angular documentation and style conventions.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add angular/angular --skill adev-writing-guide --full-depth -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

angular

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned angular/angular at 516170741d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
516170741d
Manifest
.agent/skills/adev-writing-guide/SKILL.md
Scanned
1 file, 174 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance on writing content specifically for Angular documentation, adhering to both Google's technical writing standards and Angular-specific markdown conventions. It ensures consistency in tone, style, and formatting across all Angular documentation. The goal is to create clear, accessible, and helpful resources for developers using Angular.

When to use it

  • When drafting new Angular developer documentation.
  • When revising existing Angular documentation to ensure adherence to style guidelines.
  • To maintain consistency in terminology and writing style within the Angular documentation set.

Key capabilities

  • Provides guidance on tone and content, emphasizing a conversational yet professional approach.
  • Offers advice on accessible language for a global audience.
  • Covers formatting rules including sentence casing for headings, list types (numbered, bulleted, description), serial commas, code formatting, UI element styling, and date formatting.
  • Details best practices for images, captions, and code samples within documentation.
  • References the hierarchy of style guides to follow: project-specific guidelines, Google Developer Documentation Style Guide, Merriam-Webster, Chicago Manual of Style, and Microsoft Writing Style Guide.

Example prompts

  • "Review this paragraph for adherence to Angular documentation style."
  • "Suggest improvements to make this section more accessible to non-native English speakers."
  • "Check the formatting of this code sample according to Angular documentation guidelines."

Tips & gotchas

  • The skill prioritizes Google's technical writing standards and Angular-specific conventions. Project-specific style guides, if they exist, should be consulted first.
  • Focus on explaining why code exists rather than simply describing what it does in comments.
  • Always use standard American English spelling and punctuation.