How do I install the Add Project skill?

Run npx skillmds@latest add tomevault-io/add-project-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Add Project safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Add Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Add Project?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Add Project by tomevault-io — Agent Skill

Name: Add Project
Author: tomevault-io

File contents

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

Follow these steps:

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.)
Read current list: Read data/LIST.json to determine the next available id (last entry's id + 1) and understand the existing format.
Read field definitions: Read website/shared/fields.ts to check valid categories (CATEGORIES) and website providers (WEBSITE_PROVIDERS).
Choose category and tags: Select the most appropriate category and tags based on the project's purpose. Refer to existing entries for tag conventions.
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
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
```
Report result: Show the added entry name, id, category, and whether all checks passed.

Source: palmcivet/awesome-arknights-endfield — distributed by TomeVault.

---name: add-project-2description: Add a new project to the awesome list from a GitHub repository URL Use when this capability is needed.---Add a new project entry to `data/LIST.json` from the given GitHub repository URL: $ARGUMENTSFollow 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 detected6. **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.---> Source: [palmcivet/awesome-arknights-endfield](https://github.com/palmcivet/awesome-arknights-endfield) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Add Project