agentleFS
palmcivetpalmcivet/awesome-arknights-endfield/.claude/skills/add-project/SKILL.md

add-project

Skill111 starsChanged 6 months agoMITView on GitHub

Add a new project to the awesome list from a GitHub repository URL

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. dmzoneill/skills★ 2same name
    2. blueOctopusAI/intel-hub★ 0same name
    3. leomancini/claude-skills★ 0same name
    4. NickMoignard/agent-workspace-template★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add a new project entry to data/LIST.json from the given GitHub repository URL: $ARGUMENTS

    line 7
  2. Distinctive:

    Fetch project info: Use WebFetch to visit the GitHub repository URL and extract:

    line 11
  3. Very specific:

    Read current list: Read data/LIST.json to determine the next available id (last entry's id + 1) and understand the existing format.

    line 17
  4. Very specific:

    Read field definitions: Read website/shared/fields.ts to check valid categories (CATEGORIES) and website providers (WEBSITE_PROVIDERS).

    line 19

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a new project entry to data/LIST.json from the given GitHub repository URL: $ARGUMENTS

Follow these steps:

  1. Fetch project info: Use WebFetch to visit the GitHub repository URL and extract:
    • Project description (write concise en-US and zh-CN descriptions)
    • Author/owner info: Determine whether the repository owner (the first part of owner/repo in the URL) is a GitHub organization or a personal account. If it is an organization, use the organization name and URL as the author. Only use an individual's name if the owner is a personal account.
    • License (if any)
    • Any website links (homepage, demo, etc.)
  2. Read current list: Read data/LIST.json to determine the next available id (last entry's id + 1) and understand the existing format.
  3. Read field definitions: Read website/shared/fields.ts to check valid categories (CATEGORIES) and website providers (WEBSITE_PROVIDERS).
  4. Choose category and tags: Select the most appropriate category and tags based on the project's purpose. Refer to existing entries for tag conventions.
  5. Add entry: Append the new project entry to data/LIST.json before the closing ]. Follow the ProjectProps & ProjectMeta interface from website/shared/project.ts:
    • name: Use author/repo format
    • description: Object with en-US and zh-CN keys
    • repository: The GitHub URL
    • website: Array of { provider, url } objects (only if applicable)
    • author: Object with name and url. Use the repository owner (organization or user) from the GitHub URL, not an individual contributor mentioned in the README
    • category: One of the valid categories
    • tags: Array of relevant tags
    • id: Next sequential id
    • addedAt: Today's date in YYYY-MM-DD format
    • openSource: true if repository field is present
    • license: Include only if a license is detected
  6. Run validation and generation: Execute the following commands sequentially in the website directory using bun:
    bun run check:list && bun run format:list && bun run generate:list
  7. Report result: Show the added entry name, id, category, and whether all checks passed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.