Skip to content
TrustedSkillsbeta
Back to all skills

Coding Standards

Checked
helloggx·vlatest·backend·MIT

This skill enforces consistent coding standards across your project, improving readability and maintainability for collaborative development.

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 helloggx/skill --skill coding-standards --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

helloggx

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 helloggx/skill at f1214d33f0.

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

Commit
f1214d33f0
Manifest
skill/coding-standards/SKILL.md
Scanned
1 file, 276 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 enforces consistent coding standards and best practices across projects, improving code readability and maintainability for collaborative development. It provides guidelines on variable naming, function naming, immutability patterns, error handling, and async/await usage. The goal is to ensure a high level of code quality through established conventions.

When to use it

  • Starting a new project or module
  • Reviewing existing code for quality and maintainability
  • Refactoring code to adhere to coding standards
  • Onboarding new contributors to the team's coding conventions
  • Setting up linting, formatting, or type-checking rules

Key capabilities

  • Readability Focus: Prioritizes clear variable and function names over excessive commenting.
  • KISS (Keep It Simple, Stupid): Encourages simple solutions and avoids premature optimization.
  • DRY (Don't Repeat Yourself): Promotes extracting common logic into reusable functions and components.
  • YAGNI (You Aren't Gonna Need It): Advocates for building features only when required.
  • TypeScript/JavaScript Standards: Provides specific examples of good and bad practices for variable and function naming, immutability patterns, error handling, and async/await usage.

Example prompts

  • "Review this code snippet for adherence to coding standards."
  • "Suggest improvements to make this function more readable."
  • "Check if this code follows the immutability pattern."

Tips & gotchas

  • This skill provides guidelines and examples; it doesn't automatically enforce them. It’s intended as a reference for developers.
  • The provided standards are specifically tailored to TypeScript/JavaScript projects.