Review & quality
19,169 rows, by stacks then stars
1,766 of these skill files have been read, by 1,273 distinct authors, and what they tell an agent counted. What Review & quality authors agree on, and what they forbid
u9401066/template-is-all-you-need/.claude/skills/security-reviewer Skill
3★ repoSecurity audit following OWASP Top 10 and best practices for web applications. Triggers: SEC, security, 安全, OWASP, 漏洞, vulnerability, audit, 稽核, 安全檢查, security check, CVE, 資安, penetration, pentest, 滲透, injection, XSS, CSRF, 認證, authentication, 授權, authorization, secrets, 敏感資料.
u9401066/template-is-all-you-need/.claude/skills/skill-health-check Skill
3★ repoCheck health, freshness, and consistency of all Skills, copilot-instructions.md, chatmodes, and bylaws. Triggers: SHC, health, 健康檢查, skill check, freshness, 翻新, 過期, stale, 檢查 skill, instruction check, audit skills, 技能檢查.
u9401066/template-is-all-you-need/.claude/skills/test-generator Skill
3★ repoGenerate comprehensive test suites including static analysis (vulture dead code), unit tests, integration tests, E2E tests, and coverage reports. Triggers: TG, test, 測試, 寫測試, coverage, 覆蓋率, pytest, unittest, 驗證, check, 檢查, quality, 品質, dead code, 死碼, vulture, static analysis, 靜態分析, lint, type check.
thoreinstein/obsidian-rag/skills/vault-lint Skill
3★ repoUse when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps. Triggers on "lint vault", "vault health", "check vault", "stale notes", "vault audit", "vault quality", or "check conventions".
AlexShchuka/neuro-matrix/skills/storozh Skill
3★ repoAdvisory semantic guard over a changeset manifest before it lands in shared state. Use after a multi-repo session produces a changeset-manifest (mirabilis C1) and before the co-sign push gate — classify each unit's routing against the darwin routing-policy (C3) and NLI-check each unit against the shield corpus (claims + invariants + lessons + memory) for contradiction or duplication. Flags, never blocks — the owner and Claude co-review the flags and decide.
EdytaKucharska/keel/skills/estimate-check Skill
3★ repoInvoke PROACTIVELY (do NOT judge the number directly, and NEVER produce a counter-estimate) whenever the user reports an engineering estimate, quote, or timeline someone gave them — "my engineer says 6 weeks, is that real?", "the agency/freelancer quoted 3 months", "is N weeks reasonable for [feature]?", "my dev says we can't ship without rebuilding X first" — or is deciding whether to approve, push back on, or defer quoted work. Fires on ANY reported estimate from an employee, agency, contractor, or co-founder, including when the user wants ammunition against it. The move is never re-estimating (Keel hasn't seen the code the estimator has): it arms the user with the three questions that make the estimate auditable, translates the number into money and opportunity cost, and coaches how to ask without burning trust. Especially for non-technical PMs and founders, whose failure mode is deference. Asking Keel to estimate new work from scratch routes to feature-decision.
EdytaKucharska/keel/skills/investor-dd-prep Skill
3★ repoPrepares a founder for investor technical due diligence — the moment a term sheet or serious interest turns into "our technical advisor wants to look at the codebase / meet your team / see the architecture." Use this skill PROACTIVELY when the user mentions upcoming technical due diligence, an investor asking technical questions, "we're raising and they want to review our tech", "a VC's engineer wants a call about our architecture", "what will investors look at in the codebase", "preparing a data room" (technical section), or a fundraise timeline with a diligence window. Produces: what a DD reviewer actually examines at each round stage (pre-seed to A — the bar moves), a candid pre-mortem of what THIS codebase/team will get flagged for, what's genuinely fixable in the time available vs. what to disclose-and-frame instead, and how to present AI-assisted development honestly (increasingly the #1 topic for this segment). The stance is preparation, not concealment — DD reviewers find what's there, and a founder who names their own debt with a plan reads as senior; one who hides it reads as either naive or dishonest, both of which cost more than the debt.
The-Artificer-of-Ciphers-LLC/skills-from-the-artificer/trust-but-verify Skill
3★ repoUse when you receive findings, a report, or any factual claims back from a subagent/Task before you act on them — re-validate every claim against a primary source (the code itself, the memory directory, CONTEXT.md, docs/ and docs/adr/, context7 library docs, package/API references, or a language spec) instead of trusting the agent's summary. Trigger automatically after any Task/subagent returns a result you're about to rely on, and whenever the user says "trust but verify", "verify these claims", "double-check what the agent found", "did it actually confirm that", or "where's the source for X". A subagent's report is a lead, not a fact. Nothing is verified until a source was opened and quoted; guessing, inferring, and "that looks right" are not verification.
iwritec0de/app-dev/skills/quality-gate Skill
3★ repoThis skill should be used when the user asks to "run a quality gate", "check code quality", "run lint checks", "run pre-push security scan", "check for dead code", or mentions "quality gate", "quality check", "lint check", "run checks", "code quality", "pre-push scan", "security scan". Provides automated JavaScript/TypeScript code quality enforcement including type checking, linting, formatting, dead code detection, type coverage, circular dependency detection, tests, and security scanning before git push.
iwritec0de/app-dev/skills/verification Skill
3★ repoThis skill should be used before claiming any work is complete, before committing, before creating PRs, or before reporting task status. Enforces fresh verification evidence for all completion claims. Provides the verification gate methodology: run commands, read output, then report.
rashidee/co2-skills/skills/util-usanalyzer Skill
3★ repoAnalyze PRD.md files for quality issues: incomplete sentences, non-existent references, cross-module inconsistencies, contradictory requirements, duplicate roles, design system validation, architecture principle violations, and process flow coverage gaps. Validates bi-directional coverage between User Stories/NFRs and High Level Process Flows — detects modules not covered by any process flow and process flow steps not covered by any User Story or NFR. Adds inline [TODO] annotations directly into the PRD.md file for each issue found. Trigger on keywords: "analyze user story", "analyze user stories", "check user story quality", "validate user stories", "find user story issues", "audit user stories", "review user stories", "check requirements quality", "find inconsistencies", "find contradictions". Accepts an application name as input (e.g., `/util-usanalyzer mainapp`, `/util-usanalyzer "Main App"`).
rashidee/co2-skills/skills/util-ustagger Skill
3★ repoTag new items in PRD.md files with unique ID codes and validate no duplicate tags exist. Applies to PRD.md documents structured with module sections containing User Stories, Non Functional Requirements, Constraints, References, and Test instructions. Each top-level bullet item gets a unique 9-character code with category prefix, application initials, and running number (interval of 3). Trigger on keywords: "tag user story", "tag user stories", "fix user story tag", "fix user story tags", "add IDs to requirements", "tag items in PRD.md", "number the requirements", "add requirement codes", "validate tags", "check duplicate tags", "verify tagging completeness". Accepts an application name and version as input (e.g., `/util-ustagger hub_middleware v1.0.3`, `/util-ustagger "Hub Middleware" v1.0.3`).
shwetank/bettersense/plugin/skills/team-check-in Skill
no license3★ repoUse when a team needs to regularly revisit their Goals/Roles/Norms foundation to surface drift and realign. Trigger phrases include "team check-in", "are we still aligned", "team retro on our operating model", "review our team charter", "3X3 check-in". Facilitates a structured conversation (30–90 min) that answers: Are we still committed to our stated goals/roles/norms? If not, what's the gap and how do we close it? The second step of Moussa's 3X3 framework. Works from an existing team charter (from team-charter) or surfaces foundations de novo if none exist.
shwetank/bettersense/plugin/skills/team-workspace Skill
no license3★ repoUse to set up or work with a SHARED, git-backed team workspace for artifacts a team co-owns — team charters, strategy docs, decision records — kept strictly separate from your private reflections, which never leave your machine. Trigger phrases include "share our team charter with the team", "set up a shared bettersense workspace", "put our strategy doc in the team repo", "how do teams use bettersense together". Establishes `$BETTERSENSE_TEAM_HOME` (a separate git repo), enforces a hard wall that personal files (reflections, wins, retros, commitments) are NEVER shared, and drafts the branch/commit/PR — but never pushes or opens a PR for you. The multiplayer layer with the privacy wall built in.
FutureJJ/claude-skills/skills/code-reviewer Skill
3★ repoCode review practices including review checklists, refactoring patterns, PR best practices, and team conventions. Trigger for code review guidance, refactoring advice, or PR process design.
The same file is in 1 other repository
FutureJJ/claude-skills/skills/git-workflow Skill
3★ repoGit version control including branching strategies, interactive rebase, bisect, hooks, conflict resolution, and monorepo workflows. Trigger for git branching questions, merge conflicts, rebase strategies, or git workflow design.
The same file is in 1 other repository
Biraj2004/huashu-skills-english/huashu-video-check-en Skill
3★ repoCheck video titles, thumbnails, and opening hooks based on MrBeast's strategies. Use when the user mentions "video title", "thumbnail", "click-through rate", "CTR", or "watch time".
janewu77/jw-skills/jw-agenda/skills/jw-agenda-weekly-review Skill
no license3★ repoWeekly review: aggregate daily logs, compute completion rate and time allocation, generate summary, list carry-over items; archive daily files older than 2 weeks into YYYYMM subdirs. Triggers: '周总结', '本周回顾', 'weekly review', '运行 weekly-review'.
Howie126313/obsidian-vault-kit/skills/review-scheduler Skill
3★ repo(macOS only) Spaced repetition review scheduler for Obsidian. Based on the Ebbinghaus forgetting curve, auto-reminds you to review articles at optimal intervals via macOS launchd + screen unlock detection. Triggers: "/review-scheduler", "set up review reminders", "start review scheduler", "stop review scheduler"
Howie126313/obsidian-vault-kit/skills/vault-lint Skill
3★ repoObsidian vault health checker. Detects broken links, orphan pages, index.md inconsistencies, cross-reference gaps, and frontmatter validation. Inspired by Karpathy's LLM Wiki lint pattern. Triggers: "/vault-lint", "check vault", "vault health", "lint notes"
endorphin-ai/claude-code-teams/mean-team/.claude/skills/code-review-mean Skill
no license3★ repoCode review for MEAN stack apps. Use when reviewing backend (Express + MongoDB) and frontend (React) code for quality, security, architecture compliance, performance, and best practices.
Shivam990q/better-than-claude-skills/caveman/cavecrew Skill
3★ repoDecision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
The same file is in 7 other repositories
Shivam990q/better-than-claude-skills/caveman/caveman-commit Skill
3★ repoUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
The same file is in 8 other repositories
Shivam990q/better-than-claude-skills/caveman/caveman-review Skill
3★ repoUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
The same file is in 11 other repositories
raven-sourav/pmm-content-engine/skills/critique Skill
no license3★ repoPMM Content Distribution Engine — Newsletter scraper, Obsidian knowledge brain, multi-format content generation powered by Claude Code
hussainweb/skills/skills/drupal/drupal-review Skill
no license3★ repoReview Drupal code against team standards for Drupal 11, PHP 8.4/8.5, and modern best practices. Use this skill whenever someone asks to review a Drupal module, check a PR, audit Drupal architecture, or validate that code follows standards.
hussainweb/skills/skills/drupal/drupal-theme-review Skill
no license3★ repoReview Drupal theme code - Twig templates, libraries, preprocess functions, JavaScript behaviors, Single Directory Components (SDC), accessibility, and responsive images - against Drupal 11 best practices. Use this skill whenever someone asks to review a Drupal theme, check a .theme file, audit Twig templates, look at a libraries.yml, or validate SDC components.
hussainweb/skills/skills/git/conventional-commits Skill
no license3★ repoWrite commit messages following the Conventional Commits v1.0.0 specification. ALWAYS use this skill for any workflow that produces or edits a git commit — `git commit`, `git commit --amend`, interactive rebase message editing, or a step that implies a commit such as opening a pull request, squashing, or staging work to push. Triggers on "commit", "git commit", "commit message", "amend", "squash", "create a PR", "open a pull request", "gh pr create", or any action that produces or edits a git commit message.
shakeebshaan/claude-code-quant-skills/skills/strategy-critique Skill
3★ repoAdversarial review of a trading strategy. Claude acts as a skeptical prop-desk risk manager and tries to find why the strategy will blow up. Use when evaluating a new strategy idea, before scaling up capital, or when a backtest looks "too good."
TitusKirch/skills/skills/meta/validate-skills Skill
3★ repoValidates agent skills against the Agent Skills specification — one named skill, or every skill in a repo — and reports what fails and where. Drives skills-ref, the standard's reference validator, rather than reimplementing the checks; where skills-ref cannot be obtained it reports the spec tier as unverified rather than passing a weaker hand-check off as green. Reports spec violations (portability-breaking) separately from house-style deviations (a repo's own conventions) — distinct findings, never conflated. Names Anthropic's skill-creator as the adjacent quality tool it is, not a conformance validator. Use when the user wants to validate, check, lint or conformance-test a skill or SKILL.md, verify frontmatter against the spec, find skills that break the standard, or says things like "validate the skills", "check this skill against the spec", "is my SKILL.md valid", "Skills prüfen", "Skill validieren".
TitusKirch/skills/skills/repo/atomic-commit Skill
3★ repoCommits the current session's working-tree changes as a series of atomic Conventional Commits in the repo's own detected conventions (scopes, types, commitlint rules, message language). Always presents the full plan first and commits only after confirmation; switches to plan-only when asked. Use when the user wants to commit session or feature work, mentions conventional or atomic commits, splitting changes into multiple commits, or says things like "how would you commit this", "just show me the plan", "don't commit yet", "nicht committen".
TitusKirch/skills/skills/repo/merge-deps Skill
3★ repoTriages and merges a repo's open Dependabot pull requests, selected strictly by author (app/dependabot) so no human's and no other bot's PR is ever touched. Verifies each update on its own branch first, because a Dependabot PR into an integration branch often runs no meaningful CI at all. Merging is opt-in per repo via mergeDeps.merge; once opted in, mergeDeps.confirm (default major) lets the low-risk tier merge on that standing opt-in while major bumps still wait for a human. Forge chosen per-repo by config (root forge key); v1 is GitHub via the gh CLI. Invoke manually only — this skill never fires proactively and never opens a pull request. Use when the user asks to triage, review or merge Dependabot PRs or dependency updates, mentions the Dependabot queue, dependency bumps or Dependabot alerts, or says things like "merge the dependabot PRs", "check the dependency updates", "Dependabot PRs mergen".
TitusKirch/skills/skills/repo/prune-branches Skill
3★ repoReports a repo's stale branches grouped by why they are stale — merged into the integration branch (squash and rebase merges included), upstream gone, a closed PR that never merged, and no commits for 90 days — then deletes only what a human confirms. Local and remote branches list separately; a scope argument restricts a run to one side. Merged and upstream-gone form the default set; a closed PR and plain age are listed, never preselected. Protected branches are never offered. Forge chosen per-repo by config (root forge key); v1 is GitHub via the gh CLI. Invoke manually only — never fires proactively and never deletes without an explicit yes. Use when the user wants to prune, clean up or list stale, merged or dead branches, asks which branches are safe to delete, or says things like "clean up the branches", "delete the merged branches", "Branches aufräumen", "alte Branches löschen".
TitusKirch/skills/skills/repo/pull-request Skill
3★ repoCreates a pull request from the current branch in the repo's own conventions — an umbrella Conventional-Commits title and a body filled from the repo's PR template. Forge chosen per-repo by config (root `forge`); v1 is GitHub via the gh CLI. Presents the full plan first and creates only after confirmation; plan-only when asked. Updates your own existing PR instead of duplicating, and never touches PRs opened by others or automation. Use when the user wants to open, create, or raise a pull request or merge request, mentions a PR/MR or a conventional PR, or says things like "open a PR", "create a pull request", "PR for this branch", "PR erstellen", "mach einen PR".
TitusKirch/skills/skills/repo/release Skill
3★ repoDrives a repo's release-please flow to a shipped release — promotes the integration branch onto the release branch (config-gated), waits for the release PR release-please opens, validates it, and merges it. Forge chosen per-repo by config (root `forge` key); v1 is GitHub via the gh CLI. Invoke manually only — this skill never fires proactively, never merges without confirmation, and opens at most one pull request (the promotion PR, and only where configured to create it). Use when the user explicitly asks to cut, ship or publish a release, to merge the release-please PR, to promote dev onto main for a release, or says things like "ship the release", "cut a release", "merge the release PR", "Release machen", "Release veröffentlichen".
TitusKirch/skills/skills/work/work-review-queue Skill
3★ repoDrains a repo's queue of issues awaiting AI review across GitHub (gh) or Linear (MCP) — selects every issue in review, then reviews each with a fresh, independent agent by delegating to work-review, routing each to done, changes-requested (back to the implement loop), needs-human, or blocked. Starts by reconciling issues whose PR a human merged or closed out-of-band. Honours a per-run cap, single-flight-locked with a lock separate from the implement loop's, so review and implement drains run concurrently. Use when the user wants to review, drain, or auto-review the pushed AI work, run the review loop, says things like "review the queue", "reviewe die Issues", "drain the review queue", or runs it under /loop.
TitusKirch/skills/skills/work/work-review Skill
3★ repoReviews a single tracked issue's pushed implementation across GitHub (gh) or Linear (MCP) as a fresh, independent agent — reads the issue's requirements and the pushed diff, adversarially checks whether the work is correct and complete, and writes a verdict that routes the issue to done (accepted), changes-requested (feedback, back to the implement loop), needs-human (escalation), or blocked. It never implements or fixes anything — review only. It also applies a human's verdict on a needs-human issue. Tracker, labels and the round cap come from the committed config (.tituskirch-skills.json). Use when the user wants to review, check, or sign off one specific issue's AI work, mentions an issue awaiting review, or says things like "review issue 42", "check the work on issue 42", "reviewe Issue 42", or gives a verdict on an escalated issue.
ronaknnathani/relay/skills/commit Skill
3★ repoCreate a single well-formed git commit from the working changes, following the repo's AGENTS.md and recent commit-message conventions. Use when the caller wants only to commit — not push and not open a PR (for that, use `open-pr`).
ronaknnathani/relay/skills/open-pr Skill
3★ repoStage, commit, push, and open a pull request following the author's repository and AGENTS.md conventions — repo-style commit messages, a prose PR summary, and a Testing Done command list. Use when work is finished and the caller wants it committed and a PR opened. Supports --draft and an optional local review before push.
ronaknnathani/relay/skills/rebase Skill
3★ repoUse when you need to rebase the current branch onto main, resolve merge conflicts, and force-push
ronaknnathani/relay/skills/review Skill
3★ repoReview a change for correctness, quality, and guideline compliance using a library of specialized reviewer roles. Use before opening a PR, after finishing a chunk of work, or to review an existing PR. Two output modes — a local severity-ranked report for a fix loop (default), or inline GitHub comments (--comment). Scores every finding for confidence, filters the noise, and delegates each role adversarially.
ronaknnathani/relay/skills/validate Skill
3★ repoVerify a change is ready to ship by checking it against its acceptance criteria and running the repo's own quality gates in order, then report a pass/fail verdict with the exact failures. Use to decide go/no-go right before shipping — when you want a pass/fail verdict against acceptance criteria and the repo's quality gates (lint/build/test), not a code critique (use `review` for that). It reports — it does not fix (route failures to `pr-fix`/`implement`) and does not ship.
mrzhangguoguo/oh-my-workbuddy/skills/autoresearch Skill
3★ repoStateful validator-gated research loop that keeps nudging until explicit validation evidence exists. Use when a research output is a bounded deliverable that must pass a script or professor-critic validator, not for ordinary pre-planning docs lookup.
mrzhangguoguo/oh-my-workbuddy/skills/code-review Skill
3★ repoRun a comprehensive, severity-rated code review for quality, security, and maintainability, with a deterministic merge-readiness verdict
mrzhangguoguo/oh-my-workbuddy/skills/git-master Skill
3★ repoGit expert for atomic commits, interactive rebasing, branch management, and history cleanup. Trigger "git rebase", "atomic commits", "clean git history", "squash commits", "branch strategy".
mrzhangguoguo/oh-my-workbuddy/skills/review Skill
3★ repoDeprecated. Do not invoke. Use code-review directly for implementation review, or plan --review only when reviewing an existing planning artifact.
mrzhangguoguo/oh-my-workbuddy/skills/security-review Skill
3★ repoDeprecated standalone security review skill. Use `code-review` when security concerns are in scope.
mrzhangguoguo/oh-my-workbuddy/skills/ultraqa Skill
3★ repoAdversarial dynamic end-to-end QA - generate hostile scenarios, test, verify, fix, report, and clean up. Use for robust behavior verification.
tony-adamson/groundwork/skills/ops-review Skill
no license3★ repoReviews an implemented change for silent operational failures: missing timeouts, unbounded resources, connection leaks, non-idempotent retries, slow-dependency degradation. Read-only, findings only, no fixes. Use only when the user explicitly asks to run ops-review.
protosphinx/sphinxstack/skills/design-critique Skill
3★ repoCritique something the person designed, then fix it with them. Names what works and what fails, and applies the top three fixes. Use when they say "is this good", "review my site", "why does this look off", or want feedback before sharing.
protosphinx/sphinxstack/skills/resume-review Skill
3★ repoReview an existing resume line by line. What a screener sees in six seconds, what to cut, what needs evidence. Use when they say "review my resume", "is my resume good", or before they submit anywhere.
Bmad check implementation readiness
mannnrachman/pi-bmad/skills/bmad-check-implementation-readiness Skill
no license3★ repoValidate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
mannnrachman/pi-bmad/skills/bmad-code-review Skill
no license3★ repoReview code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
mannnrachman/pi-bmad/skills/bmad-editorial-review-prose Skill
no license3★ repoClinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose
The same file is in 1 other repository
Bmad editorial review structure
mannnrachman/pi-bmad/skills/bmad-editorial-review-structure Skill
no license3★ repoStructural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure
The same file is in 1 other repository
Bmad review adversarial general
mannnrachman/pi-bmad/skills/bmad-review-adversarial-general Skill
no license3★ repoPerform a Cynical Review and produce a findings report. Use when the user requests a critical review of something
mannnrachman/pi-bmad/skills/bmad-review-edge-case-hunter Skill
no license3★ repoWalk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.
Syncfusion winforms spell checker
syncfusion/winforms-ui-components-skills/skills/syncfusion-winforms-spell-checker Skill
no license3★ repoImplement spell checking capabilities in Windows Forms applications using Syncfusion SpellCheckerAdv. Use this skill whenever the user needs to add spell checking to text controls, configure dictionaries, set up context menu suggestions, customize ignore options, or retrieve spelling suggestions. This skill covers attaching the control to RichTextBox/TextBox, managing multiple language dictionaries, enabling real-time context menus, and handling misspelled word suggestions.
wchen02/cursor-agent-learning/.cursor/skills/bugfix-and-verify Skill
no license3★ repoFixes bugs or test failures using debugger → fix → verify. Use when the user reports an error, test failure, or unexpected behavior and wants a fix confirmed.
wchen02/cursor-agent-learning/.cursor/skills/code-review Skill
no license3★ repoReview code for correctness, style, and maintainability. Use when the user asks for a code review, PR review, or feedback on changes.