docs: list paseo-skins as a community project

[huangguang1999]

Linked issue

Docs-only change; the PR template allows pure documentation changes without a linked issue.

Type of change

• Bug fix
• New feature (with prior issue + design alignment)
• Refactor / code improvement
• Docs

What does this PR do

Adds paseo-skins to the Community section in the English, Simplified Chinese, and Japanese READMEs.

The description identifies it as a community theme project with an Agent Skill and a zero-patch desktop theme loader, so it does not imply that theming is an official built-in Paseo feature.

How did you verify it

• Ran npm run build:server to generate workspace declarations in a clean clone.
• Ran npm run typecheck successfully.
• Ran npm run lint successfully with 0 warnings and 0 errors.
• Ran npm run format:check successfully.
• Confirmed the final diff contains exactly one new Community bullet in each of the three READMEs.
• Did not run the full test suite because this is a documentation-only change and the repository guidance advises against local full-suite runs.

Checklist

• One focused change. Unrelated cleanups split out.
• npm run typecheck passes
• npm run lint passes
• npm run format ran (targeted via npm run format:files)
• UI changes include screenshots or video for every affected platform (not applicable: docs-only)
• Tests added or updated where it made sense (not applicable: docs-only)

[greptile-apps]

Greptile Summary

This PR adds paseo-skins — a community desktop theme project with an Agent Skill integration — to the Community section of all three README files (English, Simplified Chinese, and Japanese).

• Each README receives exactly one new bullet, inserted in alphabetical order between paseo-relay and paseo-vscode, matching the existing formatting convention.
• All three localized descriptions are consistent with one another and accurately represent the project as a community contribution rather than an official Paseo feature.

Confidence Score: 5/5

This is a three-line documentation change — one bullet added per README — with no risk to application behavior.

All three READMEs receive identical, correctly formatted additions in the right alphabetical position. The linked repository exists on GitHub and matches the PR author. No code, config, or tests are touched.

No files require special attention.

Important Files Changed

Filename	Overview
README.md	Adds a single paseo-skins bullet to the Community section, alphabetically positioned between paseo-relay and paseo-vscode, with consistent formatting.
README.zh-CN.md	Adds the matching Simplified Chinese entry for paseo-skins in the 社区 section, correctly placed between paseo-relay and paseo-vscode.
README.ja.md	Adds the matching Japanese entry for paseo-skins in the コミュニティ section, correctly placed between paseo-relay and paseo-vscode.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Community Section] --> B[paseo-relay]
    A --> C[paseo-skins NEW]
    A --> D[paseo-vscode]
    C --> E[README.md - English]
    C --> F[README.zh-CN.md - Simplified Chinese]
    C --> G[README.ja.md - Japanese]

Loading

_{Reviews (1): Last reviewed commit: "docs: list paseo-skins as a community pr..." | Re-trigger Greptile}