New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Code Quality

by static-web-server in static-web-server/static-web-server

Ensure high-quality Rust code in the Static Web Server (SWS) project

Apache-2.0Auto-check passedDevelopment

Install Code Quality

skills CLI
$ npx skills add static-web-server/static-web-server --skill code-quality -a claude-code

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

GitHub CLI
$ gh skill install static-web-server/static-web-server code-quality --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/static-web-server/static-web-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-quality .claude/skills/code-quality && 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
code-quality
GitHub stars
2.4k
Token cost
~1.1k tokens
SKILL.md length
523 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Ensure high-quality Rust code in the Static Web Server (SWS) project

  • Tasks that involve Code quality
  • SKILL.md covers Core Engineering Principles, API Design, State & Concurrency and Maintainability, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Code Quality is an agent skill from static-web-server/static-web-server. Ensure high-quality Rust code in the Static Web Server (SWS) project

Its SKILL.md is about 1.1k 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 Development, covering Code quality. It works with Rust and Linux. The repository describes itself as: A cross-platform, high-performance and asynchronous web server for static files-serving. ⚡. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Code quality

Example prompts

  • “/code-quality”

What it can do on your machine

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

Code Quality loads about 1.1k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 523 words of instructions outside code blocks.

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

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 static-web-server/static-web-server at commit 32ec4aa, republished under its Apache-2.0 licence (© static-web-server). 523 words, ~1,081 tokens.

Download SKILL.mdSave it as .claude/skills/code-quality/SKILL.md (or your agent's skills folder).
name
code-quality
description
Ensure high-quality Rust code in the Static Web Server (SWS) project

Code Quality Guide

Load this skill when writing, reviewing, or refactoring Rust code in the SWS project.

When to load: editing any file under src/, adding a new module, changing error handling, touching async code, or reviewing a PR that modifies Rust source.

Core Engineering Principles

  • Correctness above all. Build production-grade software, not prototypes. Prioritize correctness, reliability, and maintainability over expedient shortcuts.

  • Every change requires a test. Every code change must be accompanied by a test that fails before the change and passes after it. No behavioral change is complete without objective verification.

  • Enforce invariants explicitly. Critical assumptions and invariants must be asserted, not silently ignored. Fail fast on invalid states rather than masking defects with defensive conditionals that obscure root causes.

  • Own regressions end-to-end. Any test failures introduced by your change are your responsibility to investigate and resolve. Do not defer by comparing against another branch or attempting to prove the failure is pre-existing. Diagnose the failure, identify the root cause, and either fix it or provide conclusive evidence that it is unrelated.

  • Evidence over assumptions. Every debugging hypothesis must be validated with reproducible evidence. Never speculate, infer causality without proof, or implement fixes based on unverified assumptions. Root-cause analysis must be grounded in observable facts.

  • Optimize only after measurement. Performance work must be driven by profiling, benchmarks, or measurable evidence. Do not trade correctness or maintainability for speculative micro-optimizations.

API Design

  • Design APIs that make invalid states impossible or difficult to represent.
  • Encode invariants in the type system whenever practical instead of relying on runtime validation.
  • Public APIs should have clear ownership semantics and minimal surprises.
  • Favor composability over specialization.

State & Concurrency

  • Minimize mutable state. Keep state transitions explicit and deterministic.
  • Prefer ownership and message passing over shared mutable state. Synchronize shared state explicitly.
  • Avoid holding locks across .await. Acquire locks for the shortest possible duration.
  • Keep async critical sections small. Never block asynchronous executors (see rust-backend skill: no block_on in async context).
  • Ensure task cancellation leaves the system in a valid state.
Show full SKILL.md (188 more words)Show less

Maintainability

  • Prefer straightforward code over clever code.
  • Eliminate duplication through sound abstractions, not indirection.
  • Keep functions focused on a single responsibility. Keep modules cohesive.
  • Refactor when complexity increases instead of layering additional special cases.
  • Code should be understandable without external explanation.

Explicitness & Predictability

  • Make control flow, ownership, and lifetimes obvious.
  • Prefer explicit conversions over implicit behavior.
  • Identical inputs must produce identical outputs unless randomness or external state is explicitly part of the contract.
  • Avoid hidden side effects and surprising defaults.

Resilience

  • Validate external input immediately. Never silently ignore malformed input.
  • Fail fast on impossible states. Recover gracefully from expected operational failures.
  • Preserve service availability whenever recovery is possible.

Code Review Checklist

Every contribution should leave the codebase:

  • More correct.
  • More explicit.
  • More maintainable.
  • Better tested.
  • At least as performant.
  • Easier to reason about than before.

Cross-References

The following concerns are governed by dedicated skills — defer to them for specifics:

ConcernSkill
Error handling (Result<T>, anyhow::Context, StatusCode), unsafe policy, async runtime, file system, patterns to avoidrust-backend/SKILL.md
Test organization, fixtures, handler/static-file test patternstesting/SKILL.md
Profiling, allocations, hot-path optimization, benchmarkingperformance/SKILL.md
Path traversal, TLS, security headers, CORS, input validationsecurity/SKILL.md

© static-web-server, Apache-2.0. 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/code-quality of static-web-server/static-web-server.

Open the folder on GitHubat commit 32ec4aa

Compare with similar skills

Code Quality 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.

Code Quality compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Quality this skillstatic-web-server/static-web-server2.4k—~1.1kAutomated safety check: PassApache-2.0
Cross-Language Coding Standardszereight/gitlab-mcp2k1 repos~1.4kAutomated safety check: PassMIT
Worktrunk CLI Output Rulesmax-sixty/worktrunk8.9k—~12kAutomated safety check: PassCustom licence
OpenLogi Device DiagnosisAprilNEA/OpenLogi23k—~1.6kAutomated safety check: PassApache-2.0
Gridbash Panesjasonsuhari/gridbash134—~1.5kAutomated safety check: PassMIT
Emskin Patternsemskin/emskin124—~1.6kAutomated safety check: PassGPL-3.0

Similar skills

  • Cross-Language Coding Standards

    zereight/gitlab-mcp

    Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.

    2k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Worktrunk CLI Output Rules

    max-sixty/worktrunk

    CLI output standards for worktrunk: message functions, ANSI color nesting and the shell integration that changes directory after the wt command exits.

    8.9k GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check passed

  • OpenLogi Device Diagnosis

    AprilNEA/OpenLogi

    Finds the first failing layer when an OpenLogi Logitech device is missing or misbehaving across enumeration, open, probe, IPC and UI.

    23k GitHub stars~1.6k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Gridbash Panes

    jasonsuhari/gridbash

    Coordinate with sibling agent panes from inside a GridBash grid — list panes and their roles, read what a pane is currently doing, prompt one pane or every other pane, and rename pane titles so the…

    134 GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Emskin Patterns

    emskin/emskin

    Coding and workflow patterns extracted from the emskin repo (nested Wayland compositor for Emacs).

    124 GitHub stars~1.6k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Marmite Development

    rochacbruno/marmite

    Guidelines and workflows for contributing to the marmite codebase - covers code quality, testing, architecture patterns, and contribution checklists

    880 GitHub stars~6.9k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from static-web-server/static-web-server

All 9 skills in this repo

  • Design

    static-web-server/static-web-server

    Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project

    2.4k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

  • Issue Tracking

    static-web-server/static-web-server

    Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention

    2.4k GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

  • Performance

    static-web-server/static-web-server

    Optimize or review performance for the Static Web Server (SWS) project — profiling, bottlenecks, resource usage, compression, and caching

    2.4k GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed

  • Prose

    static-web-server/static-web-server

    Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…

    2.4k GitHub stars~971 tokensUpdated 2 days ago
    Auto-check passed

  • Rust Backend

    static-web-server/static-web-server

    Write or review Rust backend code for the Static Web Server (SWS) project — crates, modules, functions, types, error handling, and async code

    2.4k GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

  • Static File Serving

    static-web-server/static-web-server

    Serve static files and web assets with optimal headers, MIME types, compression, and caching for the Static Web Server (SWS) project

    2.4k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Code Quality

What does Code Quality do?

Ensure high-quality Rust code in the Static Web Server (SWS) project. Code Quality is an agent skill from static-web-server/static-web-server.

When should I use Code Quality?

Code Quality fits situations like: tasks that involve Code quality.

How do I install Code Quality in Claude Code?

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

How do I install Code Quality in Codex?

Run `npx skills add static-web-server/static-web-server --skill code-quality -a codex`. Or copy the skill folder (.agents/skills/code-quality in static-web-server/static-web-server) into .agents/skills/code-quality in your project. Codex loads it when a task matches its description.

Can I use Code Quality 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 static-web-server/static-web-server --skill code-quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-quality, .gemini/skills/code-quality, .github/skills/code-quality and .opencode/skills/code-quality in your project.

What does Code Quality need to run?

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

Does Code Quality 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 Code Quality 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 Code Quality use?

Code Quality is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Quality use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Code Quality?

Skills that share tags, products or a category with Code Quality: Cross-Language Coding Standards (zereight/gitlab-mcp, 2k stars), Worktrunk CLI Output Rules (max-sixty/worktrunk, 8.9k stars), OpenLogi Device Diagnosis (AprilNEA/OpenLogi, 23k stars) and Gridbash Panes (jasonsuhari/gridbash, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Quality?

static-web-server (a GitHub organization) maintains it in static-web-server/static-web-server, which has 2,373 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 5, 2026.

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