awesome-mac-maintainer
- Repo stars 105,145
- Author updated Live
- Author repo awesome-mac
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @jaywcjlove · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: awesome-mac-maintainer
description: Maintain the Awesome Mac repository when adding, updating, or relocating app entries across READ…
category: documentation
runtime: no special runtime
---
# awesome-mac-maintainer output preview
## PART A: Task fit
- Use case: Maintain the Awesome Mac repository when adding, updating, or relocating app entries across README.md, README-zh.md, README-ja.md, and README-ko.md. Use this when the task requires category selection, multilingual sync, concise listing copy, ordering consistency, or repository-specific curation rules..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Use this skill for / Core workflow / Curation rules” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Maintain the Awesome Mac repository when adding, updating, or relocating app entries across README.md, README-zh.md, README-ja.md, and README-ko.md. Use this when the task requires category selection, multilingual sync, concise listing copy, ordering consistency, or repository-specific curation rules.”.
- **02** When the source has headings, the agent prioritizes “Use this skill for / Core workflow / Curation rules” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Use this skill for / Core workflow / Curation rules”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: awesome-mac-maintainer
description: Maintain the Awesome Mac repository when adding, updating, or relocating app entries across READ…
category: documentation
source: jaywcjlove/awesome-mac
---
# awesome-mac-maintainer
## When to use
- Maintain the Awesome Mac repository when adding, updating, or relocating app entries across README.md, README-zh.md, R…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Use this skill for / Core workflow / Curation rules” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "awesome-mac-maintainer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Use this skill for / Core workflow / Curation rules
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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, andREADME-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.
Core workflow
- Identify the most appropriate category by searching the existing README files for similar apps or keywords.
- Read the local context around the target section in each language before editing.
- Add or update the entry in all required language files.
- Keep the description to one sentence.
- Verify placement, wording, and formatting with
rgandgit 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 difffor 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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review