Agent skill

Comments

by tola-rs in tola-rs/tola-ssg

Write comments that carry an invariant. An agent skill from tola-rs/tola-ssg.

MITAuto-check passedFrontend & Design

Install Comments

skills CLI
$ npx skills add tola-rs/tola-ssg --skill comments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tola-rs/tola-ssg comments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tola-rs/tola-ssg.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/comments .claude/skills/comments && rm -rf skills-src

Use ~/.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/

Facts

Skill name
comments
GitHub stars
178
Token cost
~606 tokens
SKILL.md length
339 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Write comments that carry an invariant. An agent skill from tola-rs/tola-ssg.

  • Frontend & Design work in your project
  • SKILL.md covers Earns a line, Delete, One fact, one place and How it reads, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Comments is an agent skill from tola-rs/tola-ssg. Write comments that carry an invariant. Use before adding, editing, merging, or deleting any comment, doc comment, or module doc — in source or in tests — and whenever a comment restates the code or the name it sits on, one fact is explained in more than one place, or a rename leaves a name inside a comment stale.

Its SKILL.md is about 610 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 Frontend & Design. The repository describes itself as: SSG for typst-based websites - keep your focus on the content. The licence is MIT.

When your agent uses it

  • Frontend & Design work in your project

Example prompts

  • “/comments”

What it can do on your machine

Read from SKILL.md and the folder at commit fbb0506. 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

    No URLs in SKILL.md.

    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

Comments loads about 606 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 339 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~606

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 tola-rs/tola-ssg at commit fbb0506, republished under its MIT licence (© tola-rs). 339 words, ~606 tokens.

Download SKILL.mdSave it as .claude/skills/comments/SKILL.md (or your agent's skills folder).
name
comments
description
Write comments that carry an invariant. Use before adding, editing, merging, or deleting any comment, doc comment, or module doc — in source or in tests — and whenever a comment restates the code or the name it sits on, one fact is explained in more than one place, or a rename leaves a name inside a comment stale.

Comments

A comment earns its line when it says something the code cannot. Everything else competes with the code for the reader's attention and goes stale unnoticed.

Earns a line

  • Invariant: what must stay true, what enforces it.
  • Reason behind an ordering, an asymmetry, or an arbitrary-looking workaround.
  • Removal condition of a workaround or known defect left in place: what still depends on it, what removes it.
  • External constraint: protocol, platform rule, library behaviour the code cannot change.

Delete

  • Restatement of the code, the name, or the test above/below.
  • Narration of the steps, or a label naming the block it sits on.
  • Banners, separators, section markers.
  • Story about the implementation that used to be here.
  • Note about work nobody asked for.
  • Doc comment repeating the signature it documents.

One fact, one place

Explain an invariant where it is enforced; delete the copies. A caller depending on it need not say it again. Narrowest owner wins: the field or function that keeps the promise.

How it reads

State the fact in the vocabulary the code already uses. Name the exact thing — the path, the key, the value — not "this" or "it". As long as the fact, no longer. A comment needing its own explanation signals rename (skill://naming) or extract, not further explanation.

Four standards, all of them: concise — the fact and no longer; clear — the reader's vocabulary, one reading; rigorous — no hedge, no claim the code does not support; correct — verified against the code, fixed or deleted the moment it drifts.

Renames and doc comments

A name inside a comment is part of a rename: update it with the code; when that name was all the comment carried, delete it.

/// tells a caller what an item is or does, in the caller's terms, not how it works inside. //! states the module's responsibility, not a list of what it contains.

In tests

Same rules. A step needs no label; a comment earns its line by naming the boundary under test, or why the input has to look the way it does.

© tola-rs, MIT. 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/comments of tola-rs/tola-ssg.

Open the folder on GitHubat commit fbb0506

Compare with similar skills

Comments 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.

Comments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Comments this skilltola-rs/tola-ssg178—~606Automated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k40 repos~769Automated safety check: PassApache-2.0
React Doctormakeplane/plane61k12 repos~657Automated safety check: PassAGPL-3.0
Impeccablebestofjs/bestofjs3.1k26 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone

Similar skills

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 40 repos~769 tokens
    Frontend & DesignAuto-check passed
  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    61k GitHub starsUsed in 12 repos~657 tokens
    Frontend & DesignAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed

More from tola-rs/tola-ssg

All 10 skills in this repo
  • Trim

    tola-rs/tola-ssg

    Shrink code, tests, comments, and docs to what carries meaning — delete dead paths, redundant states, and refactor-dragging tests outright, then hold the survivors to the four bars.

    178 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Tola

    tola-rs/tola-ssg

    Build and maintain Tola websites and documentation. An agent skill from tola-rs/tola-ssg.

    178 GitHub stars~6k tokensUpdated yesterday
    Auto-check passed
  • Concurrency And Failure

    tola-rs/tola-ssg

    Design and review work that runs concurrently, waits, retries, or owns resources.

    178 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Friendly Report

    tola-rs/tola-ssg

    Report progress to the human. An agent skill from tola-rs/tola-ssg.

    178 GitHub stars~634 tokensUpdated yesterday
    Auto-check passed
  • Refactoring

    tola-rs/tola-ssg

    Restructure code while keeping observable behavior identical, and prove it with difference testing.

    178 GitHub stars~659 tokensUpdated yesterday
    Auto-check passed
  • Subagent Delegation

    tola-rs/tola-ssg

    Run work through subagents instead of the main thread. An agent skill from tola-rs/tola-ssg.

    178 GitHub stars~924 tokensUpdated yesterday
    Auto-check passed

Questions about Comments

What does Comments do?

Write comments that carry an invariant. An agent skill from tola-rs/tola-ssg. Comments is an agent skill from tola-rs/tola-ssg. Write comments that carry an invariant.

When should I use Comments?

Comments fits situations like: frontend & Design work in your project.

How do I install Comments in Claude Code?

Run `npx skills add tola-rs/tola-ssg --skill comments -a claude-code`. Or copy the skill folder (.agents/skills/comments in tola-rs/tola-ssg) into .claude/skills/comments in your project. Claude Code loads it when a task matches its description.

How do I install Comments in Codex?

Run `npx skills add tola-rs/tola-ssg --skill comments -a codex`. Or copy the skill folder (.agents/skills/comments in tola-rs/tola-ssg) into .agents/skills/comments in your project. Codex loads it when a task matches its description.

Can I use Comments 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 tola-rs/tola-ssg --skill comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/comments, .gemini/skills/comments, .github/skills/comments and .opencode/skills/comments in your project.

What does Comments need to run?

SKILL.md names no scripts, command-line tools or credentials: Comments is instructions for the agent only.

Does Comments access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Comments 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 Comments use?

Comments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Comments use?

About 606 tokens (SKILL.md is roughly 2.4k 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 Comments?

Skills that share tags, products or a category with Comments: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Comments?

tola-rs (a GitHub organization) maintains it in tola-rs/tola-ssg, which has 178 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.

Source: tola-rs/tola-ssg on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.