agentsclimarketplace
Sign in

Coding style

Skill 26zl/universal-agent-skills/skills/coding-style

Keep code comments and docstrings concise, neutral, human-authored in tone, and written in English unless another language is required. Use when writing, refactoring, or reviewing code where comments, identifiers, or docstrings may be added or changed; do not use to shorten required public API documentation, safety notes, or legal notices.From its SKILL.md

Install
npx -y skills add 26zl/universal-agent-skills --skill coding-style

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.2 KB, as published. Nobody here has run it

Coding Style

Write code that explains itself through names, structure, and small functions. Treat comments as a last-mile explanation for information the code cannot express clearly.

Comment rules

  • Add a comment only for non-obvious intent, invariants, constraints, workarounds, security boundaries, or surprising tradeoffs.
  • Keep comments short, factual, and neutral. Prefer one sentence or a compact phrase.
  • Explain why a surprising choice is necessary. Do not narrate what an obvious line already does.
  • Avoid first-person or conversational phrasing such as “I added,” “we need,” “here we,” or “this is where.”
  • Avoid commentary about the editing process, the prompt, the agent, or who generated the code.
  • Do not narrate the change itself: no before/after wording, "previously," "now," "used to," or "fixed" — state the current invariant, not the diff that produced it.
  • Do not add tutorial paragraphs throughout implementation code.
  • Delete stale, redundant, speculative, or copied comments when touching nearby code.
  • Preserve required API documentation, public contracts, safety warnings, citations, and legal notices.
  • Match the repository's established documentation convention when it is stricter than this skill.

Language

  • Write code in English: identifiers, comments, docstrings, commit messages, and test names.
  • Keep English even when the conversation, issue, or specification is in another language.
  • Switch only when the user asks for another language, or when the repository already uses one consistently.
  • Never mix languages inside one identifier or one comment.
  • Keep user-facing strings, translations, and localized content in whatever language the product requires.

Examples

Prefer:

// Keep the old key for clients that cache signed URLs.
const cacheKey = previousKey ?? currentKey;

Avoid:

// Here we use the previous key because I want to make sure that clients that
// may have cached a signed URL do not suddenly stop working after this change.
const cacheKey = previousKey ?? currentKey;

Omit comments that only restate the code:

retryCount += 1;

State the current invariant, not the change that produced it:

# Built-in marketplaces (openai-*) are listed without a source.
if name not in managed:
    continue

Avoid narrating the fix history:

# Before the fix this raised "inventory malformed"; now the built-in is skipped.
if name not in managed:
    continue

Review

Before finishing, inspect new and edited comments. Shorten or remove any comment that sounds conversational, narrates the implementation, repeats the code, describes the change history, or reveals use of an AI assistant. Rewrite any identifier or comment left in the conversation's language instead of the repository's.

What ships with it: 1 file

172 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Write code that explains itself through names and structure
  • Add comments only for non-obvious intent or constraints
  • Explain why a surprising choice is necessary
  • Delete stale or redundant comments when editing code
  • Write identifiers and comments in English
  • Never mix languages within one identifier or comment

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.