很棒的维护者
- 作者仓库星标 105,145
- 作者仓库 awesome-mac
- 领域
- 文档
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @jaywcjlove · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Awesome Mac Maintainer
Use this skill for repository curation tasks that touch app listings, especially when the user wants to add, update, or reclassify an app across the English, Chinese, Japanese, and Korean READMEs.
## Use this skill for
- Add a new app entry to the right category in `README.md`.
- Sync the same app into `README-zh.md`, `README-ja.md`, and `README-ko.md`.
- Update or shorten an existing listing without drifting from repository style.
- Move an entry to a better category while preserving local document structure.
For supported repository files and scope boundaries, see [references/supported-files.md](references/supported-files.md).
## Core workflow
1. Identify the most appropriate category by searching the existing README files for similar apps or keywords.
2. Read the local context around the target section in each language before editing.
3. Add or update the entry in all required language files.
4. Keep the description to one sentence.
5. Verify placement, wording, and formatting with `rg` and `git diff`.
## Curation rules
- Match the local section used by each document instead of assuming all four files have identical structure.
- Preserve existing ordering within a section. In practice this is usually alphabetical by app name.
- Do not rewrite neighboring entries unless needed for the requested task.
- Keep edits narrowly scoped to the requested listing work.
## Description style
- Explain what the app is in one sentence.
- Keep it brief and concrete.
- Prefer product identity over feature lists.
- Do not emphasize that the app is a macOS app unless that detail is necessary.
- Avoid marketing phrasing unless the repository already uses it for that exact product.
Preferred patterns:
- "Open-source HTTP(S) debugging proxy for intercepting, inspecting, modifying, and replaying requests."
- "Open-source screen recorder and editor for polished demos, tutorials, and product videos."
- "Open-source tool for switching Git identities and managing SSH keys."
## Icons and links
- Use the product site or primary project URL for the main link when that matches surrounding entries.
- If the project is open source and the repository URL is known, add the OSS icon linking to the repository.
- If the project is presented as free/open source and nearby entries use the freeware marker, add `![Freeware][Freeware Icon]`.
- Follow the exact icon formatting already used in the target section.
## Category selection guidance
- Prefer the category that contains the closest comparable apps already in the repo.
- For developer tools, distinguish between:
- API clients / API development
- Network analysis / debugging proxies
- Version control
- For media apps, check whether the document uses a broad audio/video section or a dedicated streaming music subsection.
- If Chinese uses a more specific subsection than the other languages, follow that document's local structure rather than forcing uniform placement.
## Validation
- Search for the app name in all target files.
- Review `git diff` for only the intended changes.
- Confirm the entry appears once per intended file.
- Confirm the wording remains one sentence in each language.
## Scope boundary
- This skill is for repository curation, not for rewriting the repository structure or reformatting unrelated content.
- If the user asks for a broader taxonomy change, inspect the surrounding sections first and then make the smallest consistent change.
章节与文件索引
按说明文件中的顺序排列。
使用此技能
核心工作流程
策展规则
描述风格
图标和链接
文件/命令 -> README.md · README-zh.md · README-ja.md · README-ko.md · git diff · ![Freeware][Freeware Icon]
内容校验值 -> 47505bab53b0
当前原文的自动摘译,尚未人工审校。
使用此技能
将新的应用程序条目添加到
README.md中的正确类别。将同一应用程序同步到README-zh.md、README-ja.md和README-ko.md。更新或缩短现有列表,而不会偏离存储库风格。将条目移动到更好的类别,同时保留本地文档结构。有关支持的存储库文件和范围边界,请参阅references/supported-files.md。核心工作流程
通过在现有自述文件中搜索类似的应用程序或关键字来确定最合适的类别。在编辑之前,请阅读每种语言中目标部分的本地上下文。添加或更新所有必需语言文件中的条目。将描述保持在一句话内。使用
rg和git diff验证位置、措辞和格式。策展规则
匹配每个文档使用的本地部分,而不是假设所有四个文件具有相同的结构。保留部分内的现有顺序。实际上,这通常是按应用程序名称的字母顺序排列的。除非请求的任务需要,否则不要重写相邻条目。将编辑范围缩小到所请求的列表工作。
描述风格
用一句话解释一下该应用程序是什么。保持简短和具体。更喜欢产品标识而不是功能列表。除非需要详细说明,否则请勿强调该应用程序是 macOS 应用程序。避免使用营销措辞,除非存储库已将其用于该产品。
图标和链接
当产品站点或主要项目 URL 与周围条目匹配时,请使用主链接。如果项目是开源的并且已知存储库 URL,请添加链接到存储库的 OSS 图标。如果该项目以免费/开源形式呈现,并且附近的条目使用免费软件标记,请添加
![Freeware][Freeware Icon]。遵循目标部分中已使用的确切图标格式。