Skip to content
cccskills
FreePublished on GitHubEnglish overview

awesome-mac-maintainer

Maintain app listings across English, Chinese, Japanese, and Korean README files. Choose suitable categories, write concise descriptions, and keep ordering, links, and icons consistent with each document’s existing structure and style.

OriginalShow the original description

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.

jaywcjlove/awesome-mac117,327 stars(GitHub 117,327 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Adding an app to four language editions
  • Shortening an existing app description
  • Moving an app to a more suitable category
  • Checking listing order, links, and icons

Overview

What it does

This skill adds, updates, and moves app entries across English, Chinese, Japanese, and Korean README files. It uses similar apps to identify a suitable category and follows each document’s heading structure. Descriptions are reduced to one sentence explaining what the product is for. It also keeps the existing order, links, and icon formatting consistent, including icons that indicate open-source or free software.

When it helps

Use it when maintaining multilingual app lists and checking for missing or duplicate entries. It also helps shorten existing descriptions or move apps whose current categories no longer fit. The work follows each document’s own category structure while making the requested entries consistent with their surroundings.

Example requests

  • “Add this app to an appropriate category and update the README files in all four languages.”
  • “Shorten the existing description to one sentence and match the surrounding format.”

Notes

The target files are README.md, README-zh.md, README-ja.md, and README-ko.md. After editing, it uses rg and git diff to check placement, duplicates, and the scope of changes. Formatting unrelated entries or restructuring the whole list is outside the basic scope.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt limits edits to requested entries, preserves neighboring content, and checks the change scope with git diff.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodIt names the target README files and validation tools rg and git diff, with no additional services specified.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (3)

  • SKILL.md3.7 KB
  • agents/openai.yaml295 B
  • references/supported-files.md1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Report a problem with this skill